AWS Certified DevOps Engineer – Professional DOP-C02: Current Exam Guide
AWS Certified DevOps Engineer – Professional (DOP-C02) validates the ability to automate delivery, operate distributed workloads and respond to events on AWS. It is a professional-level assessment for practitioners with substantial AWS and software delivery experience, not a generic software-engineering or advanced-networking exam.
On this page
- Use the exact official exam-domain weights
- Automate a verifiable software delivery lifecycle
- Use infrastructure as code with controlled change
- Engineer resilient cloud services
- Make telemetry explain failures
- Respond to incidents and operational events safely
- Automate security without creating blind spots
- Choose a realistic study strategy
The current AWS exam guide specifies six content domains. A preparation plan must use their published weights rather than a rearranged list that labels security as a minor ten-percent area or makes monitoring and incident response larger than the official blueprint.
Use the exact official exam-domain weights
AWS currently identifies SDLC Automation at 22%, Configuration Management and Infrastructure as Code at 17%, Resilient Cloud Solutions at 15%, Monitoring and Logging at 15%, Incident and Event Response at 14%, and Security and Compliance at 17% of scored content. These percentages help allocate preparation effort but do not guarantee that every question looks like one narrow product feature.
Review the AWS DOP-C02 exam objectives for the latest domain definitions, included services, response types and policy changes. Exam providers can revise an outline; third-party summaries should never overrule the current issuer guide.
Automate a verifiable software delivery lifecycle
Design CI/CD so a source change creates a traceable artifact, tests run at the appropriate stages, and production changes require the correct permissions and evidence. Understand AWS CodePipeline, CodeBuild, CodeDeploy and related services without assuming each organization must use all of them.
Compare rolling, blue-green, canary and immutable deployment patterns. For each, explain how traffic changes, what metrics would trigger a stop, how the previous version remains recoverable and what happens to data during an application rollback.
Use infrastructure as code with controlled change
AWS CloudFormation and the AWS CDK can define infrastructure repeatably, while Systems Manager can coordinate supported fleet operations and configuration tasks. A professional engineer should know how to review change sets, detect drift, protect stateful resources and split stacks or modules around ownership.
Treat security and environment configuration as code subject to review and test. A deployment that succeeds syntactically can still introduce an overly broad IAM role or remove a required dependency, so quality gates need to inspect effective behavior.
Engineer resilient cloud services
Resilience begins with failure domains, service objectives and recovery constraints. Use supported multi-AZ patterns, autoscaling, load balancing, managed service capabilities and appropriate disaster-recovery design. Measure availability at the application boundary instead of assuming a service is resilient because two instances exist.
Test expected failure modes, including unhealthy targets, capacity exhaustion, an Availability Zone problem and a bad software release. Understand why backup, data replication, high availability and failover automation solve different parts of the problem.
Make telemetry explain failures
CloudWatch metrics, alarms, logs and traces, together with CloudTrail and application-level observability, help relate a customer symptom to deployments, permissions and dependencies. Build dashboards that answer questions with a named owner rather than collecting every available chart.
When a service slows after a change, establish the time window, affected users, error rates and dependency behavior. Instrument critical transactions before an incident so the response team has enough context to choose containment instead of guessing.
Respond to incidents and operational events safely
EventBridge, Lambda, Systems Manager Automation and other AWS services can automate repeatable actions, but a response workflow is a privileged actor. Bound its permissions, trigger conditions, concurrency, rollback and audit trail. Not every error should cause an instance reboot or a global block.
Prepare runbooks for deployments that fail health checks, exhausted quotas, compromised identities, unreachable dependencies and unexpected cost spikes. An incident response plan should include verification that the corrective action restored the user-facing service.
Automate security without creating blind spots
Security and Compliance is 17% of DOP-C02 scored content, not a ten-percent afterthought. Prepare around identity and permissions, data protection, secrets management, compliance detection, policy automation, encryption and audit evidence.
A practical pipeline should prevent secrets from entering source control, scan dependencies, validate infrastructure policy and restrict deployment identity. Review exceptions and remediation changes with the same discipline as application code.
Choose a realistic study strategy
AWS identifies two or more years of experience provisioning, operating and managing AWS environments as an expected candidate background. Build small labs that join services into a delivery and operations system rather than memorizing a long list of console screens.
Practice scenarios that require choosing among plausible tradeoffs: low-risk deployment versus speed, managed service versus operational control, failover versus data recovery, and automation versus blast radius. Review wrong answers by identifying which requirement the rejected option failed to satisfy.