⚙️

DevOps & Release Engineering Topics

CI/CD pipeline design, build automation, deployment strategies, release management, artifact repositories, version control integration, and continuous delivery practices. Covers infrastructure automation for delivery workflows, release gates and approvals, multi-service orchestration, rollback strategies, and GitOps approaches. Distinct from Cloud & Infrastructure by focusing specifically on delivery automation and release processes rather than infrastructure platforms.

Automation Scripting for Operations

Writing scripts and tooling to automate operational and delivery tasks: shell and Python scripting, glue automation, toil reduction, and operational efficiency. Covers automating repetitive infrastructure and deployment work and building internal tooling that raises operational leverage. The concern is task-level automation and scripting, distinct from full pipeline or infrastructure-as-code frameworks.

0 questions

Pipeline Testing and Quality Gates

Automated testing wired into the delivery pipeline: test orchestration and execution in CI, quality gates and gating criteria, test environments and test-data management for pipelines, and scaling test infrastructure. Covers deciding what must pass before a change advances and keeping pipeline test stages fast and reliable. Scoped to testing as a delivery-gating concern; test strategy and craft belong to Testing, Quality & Reliability.

1 questions

Safe Deployment and Rollback Strategies

Releasing changes to production safely and incrementally, and recovering when they fail: blue-green, canary, and rolling deployments, feature flags, dark launches, traffic shifting, and progressive rollout, together with rollback strategies, safe-deploy practices, blast-radius containment, automated recovery, and safe forward/backward migration. Covers deployment orchestration across cloud platforms, staged exposure of new behavior to users, assessing deployment risk, designing reversible releases, and restoring a known-good state quickly. Focuses on how a release reaches production and how it is unwound on failure, distinct from broader incident command, which lives in Enterprise Operations & Incident Management.

16 questions

Pipeline Security and Compliance

Securing the software delivery pipeline and enforcing compliance within it: supply-chain security, secrets management in CI/CD, security and compliance gates, and automated patch and vulnerability management in the delivery flow. Covers shifting security left into pipelines and preventing insecure or non-compliant changes from shipping. Concerned with securing the delivery path itself, not general application or infrastructure security.

0 questions

Build Automation and Artifact Management

Automating the build step and managing its outputs: compilation, dependency resolution, build reproducibility, artifact repositories, and container image creation and registries. Covers versioning schemes, semantic versioning, and backward/forward compatibility of published artifacts. The concern is producing, storing, and versioning deployable units rather than orchestrating their release.

0 questions

Deployment Observability and Release Health

Instrumenting and monitoring the delivery process and its outcomes: deployment metrics (including DORA-style measures), pipeline monitoring and troubleshooting, and observability wired into continuous delivery to verify release health. Covers confirming a deployment succeeded, detecting regressions post-release, and diagnosing pipeline failures. Focuses on delivery-time signals, not broad production monitoring or incident response.

0 questions