Mock Exam · Set 4

This is practice paper four of five for AWS's DevOps Engineer Professional exam (DOP-C02), and it's built with a deliberate tilt. If you have limited study time left, the highest-leverage move isn't spreading it evenly across all six blueprint domains — it's mastering the three that together make up 56% of the real exam: SDLC Automation, Configuration Management & IaC, and Security & Compliance. This paper reflects that math directly: thirty scenario-based questions, and more than three-quarters of them come from those three domains rather than a proportional split. Sit the exam guide first if you haven't, and keep Set 5 sealed as your final, evenly-weighted dress rehearsal.

Where Set 4 fits among the five DOP-C02 papers

☺ Like you're 10: Four practice papers built from the same blueprint, but this is the one where three chapters get most of the questions on purpose.

All five DOP-C02 papers on this site draw from the same six-domain blueprint and use scenario-based, single-best-answer questions in the same style as the real exam, so a score on one paper is genuinely comparable with a score on another — what changes across the set is the shape of the coverage, not the topics themselves. Sets 1 through 3 split their questions roughly proportional to the official blueprint weights, giving you broad, balanced practice across all six domains. Set 4 abandons that balance on purpose, concentrating repetitions on the three domains a time-constrained candidate should master first. Set 5 is held back as the closest thing to a genuine, evenly-weighted cold run.

If you haven't yet worked through the six blueprint pages and at least one earlier paper, this is a defensible place to start rather than the wrong one — precisely because it concentrates your first pass on the highest-value material. But don't mistake a good Set 4 score for exam readiness by itself: it deliberately under-samples Resilient Cloud Solutions, Monitoring & Logging, and Incident & Event Response, which are still a combined 44% of the real exam. Follow it with Set 1 or Set 2 for the balanced coverage this paper intentionally skips, and see the study plan for where all five fit across your weeks of prep.

Exam conditions — sitting it for real

☺ Like you're 10: One clock, no notes, every question answered — the same rules the real exam actually uses.

A mock paper only measures what the conditions you sit it under allow it to measure. The real DOP-C02 exam is closed-book — no second monitor, no notes, no AWS documentation open in another tab — so a paper worked with a browser tab open somewhere else has measured your search skills, not your readiness.

1. One timer, started once. The real exam runs 75 questions in 180 minutes — roughly 2.4 minutes per question. Thirty questions at that same pace is about 72 minutes; round up to 75 minutes and don't pause it once it starts.
2. Leave the domain chips on "All 30". Filtering by domain during a sitting turns one paper into six easy little ones; use the chips afterward, for revision, not during.
3. Answer every question. The real exam has no penalty for a wrong answer, and neither does this paper — an unanswered question is a guaranteed zero, while a considered guess between two options is a coin flip you were offered for free.
4. Commit before you read the explanation. The reveal is instant and generous — read it before choosing and you've converted a test into a reading exercise.
5. Write down every question where you eliminated correctly but still second-guessed yourself. That hesitation is exactly what answer triage & elimination is built to train away.
6. Don't immediately re-sit. Go re-derive the two or three questions that stalled you against the actual AWS documentation, then come back and use Shuffle / reset — question order and option order both reshuffle, so you can't pass by remembering which button was green.

Why this paper leans on three domains

☺ Like you're 10: Three of the six chapters are worth more than half your grade combined — so this paper gives you extra practice on exactly those three.

AWS's own exam guide states the six DOP-C02 domain weights plainly, and they are not close to even. SDLC Automation alone is 22% — nearly a quarter of the entire exam from one domain. Add Configuration Management & IaC (17%) and Security & Compliance (17%) and three of the six domains already account for 56 of the exam's 100 weighted points, while the remaining three domains — Resilient Cloud Solutions, Monitoring & Logging, and Incident & Event Response — split the other 44% roughly evenly. A candidate who studies all six domains for equal amounts of time is spending disproportionate effort on the lighter half of the blueprint relative to what it's actually worth on exam day.

Reading a DOP-C02 scenario question fast

☺ Like you're 10: Find the AWS services hiding in the story, then find the one word that tells you what "best" actually means here.

Real DOP-C02 questions are almost never "what does service X do." They're a paragraph of scenario, a constraint, and four plausible-sounding options where two are usually wrong for a subtle reason rather than an obvious one. Three habits make these faster and more reliable to answer:

• Name the services in the stem before you read the options. A question mentioning "cross-account," "no plaintext credential," or "before it reaches a human" is telling you which service family the answer lives in — IAM/KMS, Secrets Manager, EventBridge/Automation — before you've seen a single option.
• Circle the qualifier word. "MOST operationally efficient," "LEAST development effort," "with the fewest ongoing costs" — these words eliminate options that technically work but fail the actual constraint. A correct-sounding option that ignores the qualifier is the classic trap.
• Ask what problem each wrong option actually solves. A tempting wrong answer on this exam is rarely nonsense — it's usually a real AWS feature that solves a slightly different problem than the one in the stem. Naming that different problem is how you eliminate it with confidence instead of a guess.

The paper — 30 questions

☺ Like you're 10: Pick an answer. It turns green or red right away and tells you why yours was wrong too.

Click an option to lock it in — the correct answer is marked, your mistake (if any) is marked, and the explanation appears underneath immediately. Each explanation covers both the right answer and the most tempting wrong one, because the near-miss is exactly what's worth understanding on a scenario-heavy paper. The counter and bar above the questions track your progress and score; the chips filter by domain for revision afterward; Shuffle / reset reshuffles both the questions and the options and starts a fresh attempt. Your best score is remembered on this device only — nothing is sent anywhere.

Scoring yourself, honestly

☺ Like you're 10: Write down your score per domain, not just the one big number at the top.

The counter gives you a raw percentage, but AWS's real scoring doesn't work in simple percentages — the pass mark is a scaled score of 750 out of 1000, and AWS states explicitly that the scaling accounts for question difficulty across exam forms rather than mapping cleanly to "75% correct." Treat any percentage on this page, including this one, as a thermometer rather than a certified predictor. What matters more than the headline number is the shape underneath it — and on a deliberately skewed paper, that shape needs a slightly different read than on a balanced one.

What to do with the wrong answers

☺ Like you're 10: Keep a list of what you got wrong and why your answer was wrong — that list becomes your whole revision plan.

Whatever you scored, the paper has only done its job if it produces a list. For every miss, write — in your own words — why the option you picked was wrong, not why the correct one was right. That's a different sentence, and it's the one that stops you repeating the same mistake once the real exam changes the service names and constraints on you.

mkdir -p ~/dop-c02-revision
cat > ~/dop-c02-revision/set4-wrong-answers.md <<'EOF'
# DOP-C02 Mock Set 4 — wrong answers

| Q | Domain | What I picked | Why MY answer was wrong | Page to re-read |
|---|--------|----------------|--------------------------|------------------|
|   |        |                |                          |                  |
EOF
open ~/dop-c02-revision/set4-wrong-answers.md

After a few papers, sort the rows by domain. If most of your misses sit in SDLC Automation, Configuration Management & IaC, or Security & Compliance, that's expensive to leave unfixed given their combined weight — treat it as this week's priority, not a someday task. If they're spread evenly but share a shape — every question that hinged on a cross-account KMS key policy, say, or every question about which CodeDeploy hook runs when — you've found something cheaper to fix than a domain-wide gap: a specific mechanic worth drilling once and remembering.

The fastest way to make a mechanic like a KMS grant or a CodePipeline change-set gate permanently intuitive is to actually run it once instead of only ever reading about it. Pick one from your wrong-answers list and reproduce it for real:

# Example: reproduce the cross-account KMS question for real, on a throwaway pair of accounts
aws kms create-key --description "pipeline-artifact-key" --query 'KeyMetadata.KeyId' --output text

# Grant the cross-account deployment role decrypt access via the key policy,
# then confirm the account without an explicit grant is denied:
aws kms decrypt --ciphertext-blob fileb://artifact.enc --key-id <key-id> --profile other-account
# ...and re-run it after adding the grant to see the same call succeed.

The calculation or the permission model stops being an exam trick the moment it's attached to a command you actually ran and a denial you actually saw flip to success.

Where each domain is taught

☺ Like you're 10: Every question here traces back to one of six pages. Go back to the page, not to a search engine.

Nothing on this paper is examined that isn't taught somewhere in this course. The six blueprint pages below are the answer key at exam depth — and given this paper's skew, the first three cards are where a short-on-time candidate should spend the next study session.

Around them sits the rest of the DOP-C02 kit: the study plan for pacing across all five papers, the service reference and answer triage & elimination for technique, know it cold and the closed-book strategy for the final week, and the shared course tools — the flashcards, the exam simulator, and the glossary for anything a question assumed you already knew. For the underlying practices rather than more multiple choice, see secrets & credential management, testing in the pipeline, and compliance as code & policy enforcement — all three lean directly into this paper's heaviest domains. The AWS Developer Tools suite page covers CodePipeline, CodeBuild, and CodeDeploy hands-on.