DOP-C02 study plan

Your step-by-step plan

1. Map the blueprint and book a date

   Day 1

   Read the official AWS exam guide and the six domains with their weights, and be honest about your AWS experience against the recommended two-plus years. Book a provisional date now: a fixed date turns open-ended study into a plan and is the strongest predictor of actually sitting. Note that SDLC Automation is the single largest domain and that Configuration Management and Infrastructure as Code and Security and Compliance are the next heaviest, so plan the deepest study where the marks are.

2. Build the delivery and IaC decision maps

   Week 1

   Before drilling any domain, build the decision trees the whole exam rests on: the CodePipeline native-gating rule and the CodeDeploy lifecycle-hook order, the canary-versus-linear and blue/green-versus-in-place splits, and the CloudFormation feature split (stack policy, change set, StackSets, conformance pack, drift detection). Use the recall prompts in this guide: cover the answer, choose the approach from the constraint, then reveal. If you cannot pick from the requirement alone, you do not own it yet.

3. Go deep on SDLC Automation and IaC (Domains 1 and 2)

   Weeks 1 to 3

   These two carry the most marks, so they get the most time. Drill cross-account pipelines and the three grants a target role needs with a customer managed KMS key, the deployment strategies matched to a stated downtime and rollback need, and the in-stack guardrails and change-set previews that keep infrastructure changes safe and auditable. Practise on scenario questions and read the worked explanation on every one, including the ones you got right, watching for the named constraint that picks the answer.

4. Lock resilience and observability (Domains 3 and 4)

   Weeks 3 to 4

   Drill the disaster-recovery ladder against a named RTO and RPO, RDS Multi-AZ for zonal failover, scheduled provisioned concurrency, per-method throttling, and the cross-account backup copy that escapes the production blast radius. For observability, fix the CloudWatch agent for in-guest signals, X-Ray sampling rules with a reservoir and error condition, CloudTrail log file integrity validation, and Container Insights. Do each easy-to-confuse pair by hand until the constraint alone decides it.

5. Cover incident response and security (Domains 5 and 6)

   Week 4

   Drill event-driven and serverless remediation: EventBridge patterns for a specific API call, CloudWatch Logs subscription filters for log-driven fixes, AWS Chatbot over SNS, and CloudTrail versus VPC Flow Logs for root cause. On security, lock the SCP preventive ceiling, OIDC with STS for keyless pipelines, ACM managed renewal, the detection-service map, and AWS Audit Manager for continuous control-mapped evidence. Tie every choice back to the constraint named.

6. Drill weak domains, then space the review

   Week 5

   Use your per-domain accuracy to attack the two domains dragging you down, not to re-read what you already know. Then space it: revisit each domain's recall prompts after a few days and again a week later. Spacing roughly doubles what sticks compared with cramming, and it is the cheapest gain available before a professional-level exam where the scenarios are long and the trade-offs are sharp.

7. Sit a timed mock and calibrate

   Weeks 5 to 6

   Take at least one full timed mock under exam conditions to rehearse pacing across the long professional scenarios and the flag-and-return habit in the time allowed. Treat the score as a per-domain readiness signal, not a single number, and review every missed question, naming the constraint you misread, before you book or sit.

Frequently asked questions