Home / devops-containers / AWS Certified DevOps Engineer - Professional (DOP-C02) / Cheat Sheet
AWS Certified DevOps Engineer - Professional (DOP-C02)

DOP-C02 Cheat Sheet

DOP-C02 Tests Automated, Multi-Account Operations at Scale — Not Single-Pipeline Setups

A professional exam for engineers who run delivery and operations across many accounts and Regions. Choose the answer that scales automatically to new accounts and leaves no manual step or long-lived credential behind.

Check Your Readiness →
Among the harder certs
Avg: Not published by Amazon Web Services
Pass: 750 / 1000
Most candidates understand AWS Certified DevOps Engineer - Professional (DOP-C02) concepts — and still fail. This exam tests how you apply knowledge under pressure.

DOP-C02 Domain Map

Long scenarios with numeric RTO, RPO or downtime limits and several workable answers; the winner meets the numbers with the least effort and no manual steps. The guide still lists AWS OpsWorks, which reached end of life in May 2024; treat Systems Manager as its replacement.

  1. 01
    SDLC Automation (22%) — CodePipeline stages, CodeBuild, CodeDeploy strategies, artifact stores, secrets in builds
  2. 02
    Configuration Management and IaC (17%) — CloudFormation, StackSets, Organizations, Control Tower, Systems Manager, AppConfig
  3. 03
    Resilient Cloud Solutions (15%) — RTO/RPO-driven DR strategies, Aurora Global Database, Auto Scaling policies
  4. 04
    Monitoring and Logging (15%) — CloudWatch agent, metric vs. subscription filters, Logs Insights, X-Ray, Data Firehose
  5. 05
    Incident and Event Response (14%) — EventBridge routing, SNS vs. SQS, Config remediation, stack failure diagnosis
  6. 06
    Security and Compliance (17%) — permissions boundaries, SCPs, KMS key policies, GuardDuty, Security Hub, organization trails

Wrong instinct vs correct approach

A remediation workflow that patches hundreds of instances runs for several hours
✕ Wrong instinct

Run the whole workflow in one Lambda function

✓ Correct approach

Lambda stops at 15 minutes. Use Systems Manager Automation or Run Command with rate controls, or Step Functions to sequence steps with retries, so each step finishes within its own limits.

Developers need S3 access, so the team attaches an SCP allowing s3:* to their OU
✕ Wrong instinct

The SCP allow grants developers access to the buckets

✓ Correct approach

SCPs only filter the maximum permissions available in member accounts; they never grant. Developers still need identity-based IAM permissions, and a permissions boundary can cap what delegated admins create.

Instances in an Auto Scaling group are terminated and replaced repeatedly right after launch
✕ Wrong instinct

Rebuild the AMI because the image is broken

✓ Correct approach

A health check grace period shorter than application start-up makes ELB health checks fail before the app is ready. Lengthen the grace period or use lifecycle hooks, then confirm with the target group health reason.

A CloudFormation stack update fails and the event list ends with ROLLBACK_IN_PROGRESS
✕ Wrong instinct

Troubleshoot the last error message in the event list

✓ Correct approach

Later failures are usually cascades. Find the first CREATE_FAILED or UPDATE_FAILED event and its status reason, fix that resource, then rerun. Drift detection only reports differences and never restores settings.

Operations wants automatic action when AWS Health reports an issue affecting their resources
✕ Wrong instinct

Poll the AWS Health API every minute from Lambda

✓ Correct approach

AWS Health publishes events to EventBridge. Create a rule matching the event pattern and route it to SNS, Lambda or a Systems Manager Automation runbook, with no polling code to maintain.

Know these cold

  • ▸ Canary shifts traffic in two steps; linear shifts in equal increments; all-at-once is immediate
  • ▸ ECS and Lambda deployments need no CodeDeploy agent; EC2 and on-premises hosts do
  • ▸ Build once, then promote the same artifact through test and production; never rebuild per stage
  • ▸ Secrets Manager rotates natively; Parameter Store SecureString is cheaper but has no native rotation
  • ▸ DR cost and RTO order — ackup and restore, pilot light, warm standby, multi-site active/active
  • ▸ Memory and disk metrics need the CloudWatch agent; SSM Agent handles Run Command and patching
  • ▸ SNS fans out without storage; SQS buffers and retries; EventBridge routes on event content
  • ▸ Reserved concurrency caps a Lambda function; provisioned concurrency removes cold starts
  • ▸ Route 53 failover records do nothing useful without a health check on the primary
  • ▸ An organization trail stops member accounts from disabling or deleting their own CloudTrail logging

Can you answer these without checking your notes?

In this scenario: "A remediation workflow that patches hundreds of instances runs for several hours" — what should you do first?
Lambda stops at 15 minutes. Use Systems Manager Automation or Run Command with rate controls, or Step Functions to sequence steps with retries, so each step finishes within its own limits.
In this scenario: "Developers need S3 access, so the team attaches an SCP allowing s3:* to their OU" — what should you do first?
SCPs only filter the maximum permissions available in member accounts; they never grant. Developers still need identity-based IAM permissions, and a permissions boundary can cap what delegated admins create.
In this scenario: "Instances in an Auto Scaling group are terminated and replaced repeatedly right after launch" — what should you do first?
A health check grace period shorter than application start-up makes ELB health checks fail before the app is ready. Lengthen the grace period or use lifecycle hooks, then confirm with the target group health reason.

Common Exam Mistakes — What candidates get wrong

Treating a rolling in-place deployment as a zero-downtime release

Rolling in-place batches reduce capacity and roll back by redeploying the previous revision. Blue/green on EC2 keeps the old fleet for fast rollback, while Lambda and ECS use canary or linear traffic shifting with CloudWatch alarms triggering automatic rollback.

Using RDS Multi-AZ to meet a cross-Region disaster recovery target

Multi-AZ protects against an Availability Zone failure in one Region only. Cross-Region read replicas need manual or scripted promotion. Aurora Global Database replicates across Regions with typically sub-second lag and managed failover for tight RPO and RTO.

Expecting a CloudWatch metric filter to report on past log data

Metric filters only evaluate events ingested after creation and produce numbers, not events. For history use Logs Insights; to stream raw events to Data Firehose, Lambda or another account use a subscription filter. Athena reads S3 exports, not log groups.

Choosing self-managed StackSets for an organization that keeps adding accounts

Service-managed StackSets with automatic deployment roll baselines out to every new account that joins a target OU, with no execution roles to create. Self-managed permissions need roles in each account and suit setups without AWS Organizations.

Granting cross-account KMS access through the IAM policy alone

A role in another account needs kms:Decrypt in its IAM policy and an allow in the key policy. Pipelines deploying to other accounts need a customer managed key on the artifact bucket, because the AWS managed S3 key cannot be shared.

Resources to help you pass AWS DevOps Engineer - Professional on your first attempt

DOP-C02 rewards automation that scales across accounts. Find out where your answers still rely on manual steps.