AWS DevOps Engineer Professional course and practice exam: DOP-C02

This AWS DevOps Engineer Professional course has 30 video lessons and 33 graded labs, and its AWS DevOps Engineer Professional practice exam follows the official exam objectives: a 20-question sampler free with an account, the full question bank and timed mock exams with Pro.

Automation, configuration, resilience, monitoring and incident response on AWS

Prepares you for DOP-C02: SDLC automation, configuration management and infrastructure as code, resilient cloud solutions, monitoring and logging, incident response, and security and compliance.

Advanced · 2 hours · 30 lessons · 34 labs

AWS DevOps Engineer Professional exam guide

The AWS DevOps Engineer Professional exam (AWS Certified DevOps Engineer – Professional, by Amazon Web Services (AWS)): 180 minutes; questions: 75 total (65 affect score); pass mark: 750 (on a scale of 100–1,000); cost: USD 300.

  • Format: 75 questions (65 scored, 10 unscored pretest); multiple choice or multiple response
  • Duration: 180 minutes
  • Questions: 75 total (65 affect score)
  • Pass mark: 750 (on a scale of 100–1,000)
  • Cost: USD 300
  • Valid for: 3 years
  • Delivery: Pearson VUE testing center or online proctored exam
  • Prerequisites: None required; 2 or more years of experience provisioning, operating, and managing AWS environments recommended

Exam domains and weights

  • SDLC Automation: 22%
  • Configuration Management and IaC: 17%
  • Resilient Cloud Solutions: 15%
  • Monitoring and Logging: 15%
  • Incident and Event Response: 14%
  • Security and Compliance: 17%

A 20-question practice sampler is free with an account; Pro adds the full question bank and timed mock exams.

10 AWS DevOps Engineer Professional sample questions with answers: free to read, no account needed.

Common questions

How long is the AWS DevOps Engineer Professional exam?

The AWS DevOps Engineer Professional exam lasts 180 minutes.

How many questions are on the AWS DevOps Engineer Professional exam?

75 total (65 affect score).

What is the AWS DevOps Engineer Professional passing score?

The pass mark is 750 (on a scale of 100–1,000).

How much does the AWS DevOps Engineer Professional exam cost?

USD 300.

Is there a free AWS DevOps Engineer Professional practice test?

Yes. A 20-question practice sampler is free with an account; Pro adds the full question bank and timed mock exams.

Source: AWS Certified DevOps Engineer – Professional exam guide (DOP-C02) (Amazon Web Services (AWS)), checked 2026-10-02.

Who it is for

Advanced level.

For engineers who build and run delivery pipelines, automation and monitoring on AWS, and want the DevOps Engineer Professional certificate.

What you don't need yet:

What helps:

No formal prerequisites. The courses under "Take first" cover what helps.

Take first:

Learning paths:

Nobody needs to know everything before they start. Each course builds on the one before, so a learning path takes you there step by step.

What this exam proves, and what it doesn't

DevOps Engineer Professional is a multiple-choice and multiple-response exam: passing shows you can judge AWS delivery and operations designs. It doesn't test hands-on skill; our graded labs replay recorded AWS behaviour, not a live account.

Exam objectives this course teaches

AWS Certified DevOps Engineer – Professional

Labs

34 labs, 33 of them graded: you write the code, it runs, and graded labs check the result. The outline lists each lesson's labs.

What is free

Start free: First module free with an account. Pro: Every course, lab, handbook, practice exam and certificate.

Course outline

Start Here

  1. Two Hundred Accounts And One Bad Deploy (1 lab): You can trace one production incident across all six DOP-C02 domains, name the control from each domain that would have stopped or shortened it, and weigh the trade-off between them the way the exam does.
  2. Surviving A Hundred And Eighty Minutes (2 labs): You can pace seventy-five long scenario questions in 180 minutes, find the deciding constraint in a stem before reading the options, use least operational overhead as a tie-breaker, and run a flag-and-return first pass.

SDLC Automation

  1. CodePipeline: Stages, Actions And The Key Nobody Shared (1 lab): You can build a multi-stage CodePipeline with a manual approval, cross-account deploy roles and KMS-encrypted artifacts, choose a V2 execution mode and trigger, and diagnose why a cross-account action cannot read its artifacts.
  2. CodeBuild: The Build That Passed With Failing Tests (3 labs): You can write a buildspec with phases, finally blocks, report groups, caching and secrets from Secrets Manager, predict which phase failure stops a build, and make failing tests fail the pipeline.
  3. Artifacts: Where Packages And Images Live, And Die (1 lab): You can decide where each kind of artifact lives, configure CodeArtifact upstreams and package origin controls, use ECR scanning, replication and immutable tags, and write an ECR lifecycle policy that never expires the image production runs.
  4. CodeDeploy: Hooks That Never Ran (1 lab): You can write AppSpec files for EC2, ECS and Lambda, predict the order CodeDeploy runs lifecycle hooks in, choose a deployment configuration, and configure automatic rollback on failures and alarms.
  5. Strategies Across Compute: The Canary That Saw Nothing (1 lab): You can choose in-place, rolling, immutable, blue/green, canary or linear deployment for EC2 and Auto Scaling, ECS and Lambda against a stated constraint, and size a canary and its alarm so it can actually detect a bad release.
  6. Deployment Strategies: Blue Green (1 lab): You can describe blue green deployment and weigh its fast rollback against the cost of a second production sized environment.

Configuration Management And IaC

  1. CloudFormation In Depth: Replace Or Update? (1 lab): You can lint a template with cfn-lint, predict from the registry schema whether a change set updates or replaces each resource, protect stateful resources with DeletionPolicy, UpdateReplacePolicy and stack policies, and use drift detection, custom resources, creation signals and rollback triggers.
  2. StackSets: Eighty Failures Before Lunch (1 lab): You can deploy a StackSet across accounts and Regions with service-managed permissions and automatic deployment, set concurrency, failure tolerance and concurrency mode so a bad template stops early, and place CDK Pipelines and global resources correctly.
  3. Accounts At Scale: Vending, Guardrails And SCPs (1 lab): You can automate account vending with Control Tower Account Factory and customizations, choose between preventive, detective and proactive controls, and evaluate service control policies at every level of an organisation against real policy documents.
  4. Systems Manager At Fleet Scale: Compliant And Unpatched (2 labs): You can configure Patch Manager baselines and spot one that never approves, run commands across a fleet with safe rate controls, and choose between Run Command, State Manager, Automation and Parameter Store for a fleet task.

Resilient Cloud Solutions

  1. High Availability Across Tiers: What Fails Over By Itself? (1 lab): You can combine Multi-AZ and multi-Region designs with Route 53 health checks and routing, Aurora Global Database, DynamoDB global tables and Amazon Application Recovery Controller, including Region switch plans, and say which layer fails over automatically and which waits for a decision.
  2. Scaling Patterns: When Capacity Arrives Too Late (1 lab): You can choose target tracking, step, scheduled or predictive scaling, use lifecycle hooks and warm pools for slow-booting instances, size groups for failover, and scale ECS services and Lambda concurrency correctly.
  3. Recovery To RTO And RPO: Backups Nobody Could Delete (1 lab): You can match each workload's RPO and RTO to the cheapest approach that meets both, configure AWS Backup plans with cross-account copies, Vault Lock and restore testing, and use Elastic Disaster Recovery for servers.
  4. Testing Resilience: The Experiment That Would Have Been The Outage (1 lab): You can design an AWS Fault Injection Service experiment with a hypothesis, bounded targets, actions and CloudWatch alarm stop conditions, check a template before it runs, and use Resilience Hub to choose what to test.

Monitoring And Logging

  1. Collecting Logs And Metrics: The Disk Nobody Measured (1 lab): You can configure the CloudWatch agent for memory, disk and log collection with valid retention, centralise logs with subscription filters and Firehose, use cross-account observability, and decide where each kind of log should live.
  2. Finding The Problem: The Composite Alarm That Stayed Quiet (1 lab): You can turn logs into metrics with metric filters, combine metrics with metric math, set alarm periods, datapoints and missing-data treatment, predict whether a composite alarm fires, and use Logs Insights, anomaly detection and X-Ray to locate a fault.
  3. Monitoring As Code: The Alarm That Watched Nothing (1 lab): You can define alarms, subscription filters and dashboards in CloudFormation, check that each alarm's namespace, metric and dimensions match a metric that exists, and wire log events and alarm state changes into automation.

Incident And Event Response

  1. EventBridge Rules: The Rule That Matched Nothing (1 lab): You can write EventBridge event patterns with exact values, prefixes, numeric ranges, anything-but, exists and $or, test them against recorded events that must match and must not, and route events to targets across accounts and Regions.
  2. Remediation As Code: A Public Bucket Appears (1 lab): You can evaluate AWS Config rules over configuration items, attach automatic remediation with Systems Manager Automation, combine it with preventive Block Public Access and EventBridge-triggered fixes, and handle legitimate exceptions without disabling the control.
  3. Troubleshooting Failed Deployments: Read The First Failure (1 lab): You can read CloudFormation stack events, CodeDeploy deployment and lifecycle diagnostics, and ECS service and task events to find the first failure, name its root cause, recover a stack stuck in UPDATE_ROLLBACK_FAILED, and fix it.
  4. Incident Tooling: Eighteen Minutes To Find A Human (1 lab): You can route customer-impacting alarms to a paging service and OpsCenter through a composite alarm, start runbooks from EventBridge, use AWS Health events to tell an AWS issue from your own, explain why Incident Manager is closed to new customers, and drill a response before you need it.

Security And Compliance

  1. Identity At Scale: The Boundary That Blocked The Admin (1 lab): You can grant access across accounts with IAM Identity Center permission sets, use ABAC with session tags, delegate role creation safely with permissions boundaries, and evaluate the result against real AWS managed policies.
  2. Automating Data Protection: Keys, Secrets And A Partner Shortcut (1 lab): You can grade a KMS key policy for open principals, separation of duties and rotation, automate Secrets Manager rotation and detect failed rotations, and choose organisation-wide controls such as S3 Block Public Access and Macie.
  3. Security Hub, GuardDuty And Inspector: Signal, Noise And Response (1 lab): You can aggregate GuardDuty, Inspector and Security Hub findings across accounts and Regions, suppress expected noise with automation rules, predict which findings resolve themselves, and route the rest to automated responses with EventBridge.
  4. Auditing: Who Opened Port Twenty Two? (1 lab): You can answer who changed a resource, as which person, and what else that session did, using organisation CloudTrail trails and CloudTrail Lake, prove log integrity, use Config aggregators for configuration history, and collect evidence with Audit Manager.
  5. Pipeline Security: The Build Role That Could Do Anything (1 lab): You can replace an over-privileged pipeline role with a least-privilege one generated from activity, scan code, dependencies and images inside the pipeline with Amazon Inspector, and sign artifacts so only what the pipeline built can be deployed.

Mock And Review

  1. Long-Stem Clinic: When Two Answers Both Work (1 lab): You can take a long Professional scenario, strike the options that break a hard requirement, and use the deciding phrase to choose between two options that both work, across all six domains.
  2. The Full Mock And Your Review Plan (1 lab): You can sit a timed 75-question mock weighted like DOP-C02, read the score report by domain, find the misses that cost the most once domain weights are applied, and turn them into a short review plan and a booking decision.

Certification courses