Browse AWS Certification Guides

DOP-C02 SDLC Automation Guide

Study DOP-C02 SDLC automation for pipelines, testing gates, artifacts, and release strategies.

This domain tests whether delivery is repeatable, auditable, and safe under pressure. Strong DOP-C02 answers prefer pipelines, artifacts, promotion controls, and rollback-ready release strategies over manual heroics.

What AWS is explicitly testing

As of May 11, 2026, the current AWS DOP-C02 domain page breaks SDLC Automation into four task areas:

  • Task 1.1: implement CI/CD pipelines
  • Task 1.2: integrate automated testing into CI/CD pipelines
  • Task 1.3: build and manage artifacts
  • Task 1.4: implement deployment strategies for instance, container, and serverless environments

That split matters because DOP-C02 often hides the real issue behind familiar AWS service names. A question that mentions CodePipeline might still be a testing-gate problem, an artifact-integrity problem, or a deployment-strategy problem.

Current weight in the exam guide

AWS currently weights this domain at 22% of scored content, making SDLC automation the largest DOP-C02 area.

Work this domain in order

Start with 1.1 CI/CD Pipelines so the pipeline shape is clear before you optimize anything else.

Then move through:

  1. 1.2 Automated Testing in Pipelines
  2. 1.3 Artifact Build and Management
  3. 1.4 Deployment Strategies Across Runtimes

Fast routing inside this chapter

If the scenario is really about… Go first to…
source stages, build stages, cross-account promotion, secrets in the pipeline, or release flow structure 1.1 CI/CD Pipelines
unit tests, integration tests, security scans, approval gates, or where testing belongs in the release path 1.2 Automated Testing in Pipelines
package integrity, ECR or CodeArtifact, image generation, artifact retention, or what gets promoted between stages 1.3 Artifact Build and Management
blue/green, canary, immutable rollout, Lambda alias shifting, ECS/EKS release risk, or rollback behavior 1.4 Deployment Strategies Across Runtimes

What strong DOP-C02 answers usually do

  • treat the pipeline as the release control plane, not just a convenience wrapper
  • keep artifacts immutable between test and production promotion
  • put the right tests at the right stage instead of delaying everything until the end
  • design release strategies around rollback, blast radius, and runtime fit
  • use secrets, approvals, and permissions in ways that preserve auditability

Common DOP-C02 traps

  • rebuilding a different artifact for production after testing already passed
  • putting expensive or low-signal tests too early or too late in the pipeline
  • choosing a deployment strategy without considering rollback speed
  • confusing infrastructure provisioning with application release orchestration
  • treating CodePipeline, CodeBuild, CodeDeploy, ECR, and CodeArtifact as interchangeable because they all sit “in CI/CD”

In this section

Revised on Monday, June 15, 2026
2. Configuration Management and IaC