Field Notes — What Test-Takers Report
Every other page in this course teaches you the material. This one asks a narrower and more awkward question: what did people who actually sat DOP-C02 choose to publish afterwards — how the three hours felt, where their concentration broke, what turned up on screen that they hadn't studied? The good news is that this record genuinely exists; DOP-C02 has been live since 2023 and has accumulated real write-ups. The catch is that it is unevenly distributed: the detailed English accounts are mostly a couple of years old, the newest and most detailed accounts are in Japanese, and the top of your search results is almost entirely vendor marketing rather than evidence. This page names every account it uses, says plainly what each one is worth, and flags the places where a confident-sounding claim in a public write-up is simply wrong.
Imagine you want to know what a ride at a theme park is really like before you queue for it. Plenty of people have been on it and written honest reviews — but when you search, the first three pages are shops selling ride T-shirts, and "The Ultimate 2026 Ride Guide" written by someone who has never queued. The real reviews are further down. The newest and most detailed ones happen to be written in a language you don't read, which is annoying but fixable — you can translate them. And one review says something surprising: the ride has a new section that isn't on the park's official map yet. That last one is the most useful thing anybody wrote, and it's the reason this page exists.
How much public evidence there actually is
☺ Like you're 10: Lots of people have written about this test. The problem isn't that the reviews are missing — it's that they're buried, some are old, and the newest ones are in Japanese.
Before quoting anybody, it is worth stating the shape of the record honestly, because that shape should change how you read the rest of this page. DOP-C02 replaced DOP-C01 in 2023 and has had roughly three years to accumulate first-hand write-ups. It has. There is no shortage of people who sat this exam and published something afterwards. But four things about that pile matter more than its raw size.
1. The English-language first-hand accounts are mostly thin, and mostly old
The genuinely narrative ones — the write-ups that tell you what the room felt like, how many questions the author flagged, at what point their concentration gave out — cluster in 2023 and 2024. Most recent English content titled "exam experience" turns out to be study-plan-shaped: a resource list plus generic advice, with no score, no exam date, and no exam-day texture at all. Those are useful as reading lists. They are not evidence of a sitting, and this page does not treat them as such.
2. The most current, score-bearing accounts are in Japanese
This is an unusual thing to have to tell an English-speaking reader, and it is genuinely useful. Qiita — a large Japanese developer-writing platform — returns roughly 187 results for DOP-C02, a large share of them tagged 合格体験記 ("pass experience report"). Several are from May–August 2026 and report exact scaled scores. If you want first-hand evidence about the exam as it exists now rather than as it existed in 2024, that is where it lives, and machine translation handles it fine.
3. The top of your search results is not evidence
Searching "DOP-C02 exam experience" reliably surfaces practice-dump sites, Udemy course listings, mobile-app store pages and content-farm "2026 Guides" above actual first-hand write-ups. This is not a minor annoyance; it is the main obstacle to doing this research yourself, and it is why this page names its sources rather than gesturing at "the community."
4. The single most valuable finding isn't a tactic — it's a documented gap
The most actionable thing in the entire public record is a drift between AWS's own exam guide and the live exam, corroborated by two independent candidates and checkable against AWS's own published documents. It gets its own section below.
Start from what AWS itself guarantees
☺ Like you're 10: Before trusting anybody's story, read the rulebook. It's short, it's free, and it's the only part that's guaranteed true.
Individual accounts are anecdotes; the official documents are the floor. Two of them matter, and — this trips people up — they publish different facts. The exam guide (currently version 1.6) covers content, question types and scoring. The certification product page covers duration, price, languages and validity. Neither one contains the other's numbers, which is exactly why third-party pages tend to mix them up.
| What it says | Which document says it |
|---|---|
| Two question types only — multiple choice (one correct answer, three distractors) and multiple response (two or more correct out of five or more options) | Exam guide v1.6 |
| 65 questions that affect your score, plus 10 unscored questions that do not, and are not identified on the exam | Exam guide v1.6 |
| Scaled score of 100–1,000; minimum passing score 750 | Exam guide v1.6 |
| Compensatory scoring — "you do not need to achieve a passing score in each section. You need to pass only the overall exam." | Exam guide v1.6 |
| Unanswered questions are scored as incorrect; there is no penalty for guessing | Exam guide v1.6 |
| Target candidate: 2 or more years of experience provisioning, operating and managing AWS environments, plus SDLC and programming/scripting experience | Exam guide v1.6 |
| Explicitly out of scope: advanced networking, deep security recommendations, database performance optimisation, full-stack application development | Exam guide v1.6 |
| 180 minutes, 75 questions, 300 USD | Certification product page — not the exam guide |
| Pearson VUE testing centre or online proctored exam; available in English, Japanese, Korean and Simplified Chinese; certification valid for 3 years | Certification product page |
The price, the clock and the question count above are quoted from AWS's own certification product page, and the scoring and question-type facts from exam guide version 1.6. AWS revises all of these without much notice — it has already replaced DOP-C01 with a materially different exam once. Treat every figure on this page as "true as of this check" and verify on AWS's official DOP-C02 page before you hand over a card or build a study calendar around a specific number. The DOP-C02 Exam page carries the same figures with the registration and proctoring logistics attached.
The six domain weights — unchanged since launch
One reassuring finding: the domain weightings are identical in exam guide v1.0 and v1.6. Whatever else has drifted, the shape of the exam has not. That means a study plan built on these weights is durable in a way that a study plan built on the service list is not.
| Domain | Weight | Where it's taught here |
|---|---|---|
| D1 — SDLC Automation | 22% | SDLC Automation |
| D2 — Configuration Management and IaC | 17% | Configuration Management & IaC |
| D6 — Security and Compliance | 17% | Security & Compliance |
| D3 — Resilient Cloud Solutions | 15% | Resilient Cloud Solutions |
| D4 — Monitoring and Logging | 15% | Monitoring & Logging |
| D5 — Incident and Event Response | 14% | Incident & Event Response |
↗ DOP-C02 exam guide (HTML, docs.aws.amazon.com)
Compensatory scoring changes your triage. You do not have to clear a bar in each of the six domains — only overall. That means a domain you are genuinely weak in is a problem worth its weight and no more: 14% of the exam is 14% of the exam, not a separate gate you can fail on. It also means the fastest route to a pass is usually shoring up a mediocre big domain rather than perfecting a small one. Combine that with "no penalty for guessing" and the exam-day rule is simple: every question gets an answer, including the ones you have no idea about.
The drift: AWS's own service list no longer matches the live exam
☺ Like you're 10: The park's official map is out of date. One ride was taken off the map but is still in the free sample brochure, and there's a new ride the map has never mentioned that people keep being sent to.
This is the single most useful thing in the public record, and unusually for a field-notes page, it is checkable — not one person's recollection, but a comparison of two AWS documents plus two independent candidate reports. Here is what the documents show.
| Service | Exam guide v1.0 (launch era) | Exam guide v1.6 (current) | What candidates report |
|---|---|---|---|
| AWS CodeCommit | In the in-scope Developer Tools list, and named in a task statement | Absent entirely — not in the service list, not in any task statement | Still the opening scenario in AWS's own free sample-questions PDF |
| AWS CodeConnections | — | Appears nowhere in the in-scope list | Reported appearing repeatedly on the live exam by one candidate, and listed among frequently-seen topics by another |
| AWS CodeStar | Listed | Still listed | AWS has since wound the service down |
| AWS OpsWorks | Listed | Still listed | AWS has since wound the service down |
| AWS Proton | Listed | Still listed | Closed to new customers |
| Fault Injection | "AWS Fault Injection Simulator (AWS FIS)" | Still "AWS Fault Injection Simulator (AWS FIS)" | AWS has renamed it Fault Injection Service; two candidates flag it as a topic they met |
Who reported it
@boloyome, writing on Qiita on 10 June 2026, published a post whose title translates as "The story of meeting a service I'd never heard of when I took the AWS DOP." He reports that AWS CodeConnections appeared repeatedly on his exam, that he had never encountered it before, and that he was unsettled to find it absent from the official service reference list. He had expected CodeCommit as the default CodePipeline source and found CodeConnections filling that role instead. He had about a year of AWS experience at the time.
Irene Bonso, writing up her 2025 sitting for Tutorials Dojo, independently lists AWS CodeConnections and AWS Fault Injection Service among the topics that came up frequently on her exam. She and @boloyome sat in different years, wrote in different languages, and almost certainly never read each other. That is what makes this worth acting on rather than filing as one person's bad luck.
A third data point, weaker but consistent: Camille, in DEV Community study notes published in January 2026, also flags AWS Fault Injection Service as a topic to know.
Two concrete consequences. Don't over-invest in CodeCommit. The current guide has dropped it entirely; the fact that AWS's free sample questions still lead with it is a stale artefact, not a signal. Do learn CodeConnections — what it is, what it replaces, and how a CodePipeline source stage wires to a third-party Git provider through it — even though the official in-scope list does not name it. And treat the whole appendix as a minimum: the guide's own wording says the service list "is non-exhaustive and is subject to change." A service being absent from the list is not evidence that it is absent from the exam. Our AWS Developer Tools page and the Service & Command Reference are where to shore this up.
His own conclusion is the right one to borrow: when an unknown service name appears in a question, reason from where it sits in the service graph rather than panicking that you failed to memorise an exhaustive list. A source-stage connector between CodePipeline and an external Git host does a specific job, and the job constrains the plausible answers, whether or not you have heard the product name before. That is a transferable skill and it is cheaper to build than a memorised catalogue that goes stale anyway.
The English-language accounts
☺ Like you're 10: Seven real people, all findable by name. Here's what each one is actually worth.
Every account below was opened and read. All are real, findable and attributable. They are ordered by how much genuine exam-day substance they carry, not by how confident they sound.
| Author & piece | What it contributes | The caveat | Link |
|---|---|---|---|
| Tolu Nimi — "Passing AWS DevOps Engineer Pro (DOP–CO2) — Tips and Notes" Medium, 12 Oct 2024 | The richest English exam-day narrative available. Sat remotely via Pearson VUE. Flagged 25 of 75 questions and began the flagged review with 45 minutes left; many of the flagged ones were multi-select "choose 3 of 5 or 6." Warns that at home you likely won't be allowed pen and paper and must keep your head visible to the camera. Includes a long service-by-category breakdown of what he saw most. | Contains a scoring claim that is wrong — see the corrections section below — and one timing report that shouldn't be generalised. | Medium |
| Simon Mafany E. — "How I passed the challenging AWS Certified DevOps Engineer Professional -2024!" Medium, 12 Oct 2024 | The best account of pacing and stamina, and the source of the 2.4-minutes-per-question arithmetic. Passed first attempt without holding DVA or SOA, on 2 months+ of prep alongside a full-time job. Answered 74 of 75 — one flagged and forgotten. Credits hands-on memory specifically: how cfn-init and cfn-signal behaved, and how deployment hooks failed. | None material. Also includes his own "retired services still in the exam guide" list — naming OpsWorks, CloudWatch Events and CodeStar — which independently supports the drift section above. | Medium |
| Rishab Kumar — "How I passed the AWS DevOps Engineer Professional Exam" DEV Community, 26 May 2023 | The useful outlier: the low-prep data point. Passed with 756 — six points over the line — saying he "didn't have any specific preparation" and decided to wing it on the back of a year of DevOps work with TeamCity, CloudFormation, Terraform and Azure DevOps. Sat in person at a Pearson VUE centre, using "almost two and a half hours out of the three hours allotted." Found the questions lengthier than Azure's AZ-400 and lost focus around question 30–35. | A sample of one, and an early-2023 sitting. Read it as evidence that experience alone can get you across — but only just. | DEV Community |
| Suraj Solanki — "My Journey to Cracking the AWS DevOps Professional Exam" Medium, 28 Aug 2025 | The best study method in the English set: map every revision topic to a specific piece of work you actually did. Exam day at home via Pearson VUE, no technical issues, finished with ~15 minutes to review flagged questions, trusted first instinct. | No score reported, and a Senior DevOps Engineer's baseline is not a beginner's. | Medium |
| Irene Bonso — "My AWS Certified DevOps Engineer Professional Exam Experience in 2025" Tutorials Dojo | The most detailed online-proctoring logistics account: booked a midnight slot, checked in at 11:30 PM, shifted her sleep schedule the day before, proctor asked for ID and a room scan. Notably, her result did not appear on screen — the pass email arrived roughly 16 hours later. Her list of frequently-seen topics is one of the two CodeConnections corroborations. | Commercial interest disclosed: she is a Software Engineer at Tutorials Dojo and the post recommends her employer's paid study guide and practice exams throughout. A real account in a commercially interested venue. | tutorialsdojo.com |
| Ekant Mate (AWS APN Ambassador) — "How I passed my AWS Certified DevOps Engineer – Professional (DOP-C02)?" Medium / AWS in Plain English, 27 Oct 2023 | A recertification account, and the highest score anywhere in this page's evidence: 911/1000, having first certified in May 2020. Reports format and domains largely unchanged from DOP-C01, with content refreshed for newer services — useful evidence about the C01→C02 transition. | Paywalled. It is a Medium member-only story; only the introduction is publicly readable. Cite the score and the framing, not the body. | Medium (member-only) |
| Husain Yusuf — "How I prepared for AWS DevOps Engineer Professional (DOP-C02) Exam" DEV Community, 1 Dec 2024 | One genuinely good observation: "all the answer options could be implemented" — the discrimination is use-case fit, not technical validity. That single line explains more about DOP-C02's difficulty than most paragraphs written about it. | Thin. No score, no prep duration, no exam-day detail. Listed for completeness; don't lean on it. | DEV Community |
Husain Yusuf's "all the answer options could be implemented" and Tolu Nimi's observation that associate-level exams usually have one answer that "stands out" whereas DOP-C02 "required a deeper understanding of the concepts and technologies to identify the best answer" are the same finding from two directions. DOP-C02 rarely offers you a wrong answer to eliminate on technical grounds. It offers you four things that would all work, and asks which one fits the stated constraint — cost, RTO, operational overhead, blast radius, least privilege. That is a different reading skill from associate-level exams, and it is what Answer Triage & Elimination drills.
The Japanese-language corpus — the current, score-bearing material
☺ Like you're 10: The newest reports are all in Japanese, several list their exact score, and your browser can translate them in one click.
These are the most recent first-hand accounts found in any language, and unlike most of the English set, several report exact scaled scores. Qiita's DOP-C02 search runs to roughly ten pages. Four posts were read in detail; several more were confirmed to exist and are listed after the table.
| Author & date | Score & background | What makes it worth reading | Link |
|---|---|---|---|
| @Crowncrow 「AWS認定 DOP合格体験記」 25 June 2026 | 815. Already held six AWS certifications (AIF, SAA, SOA, DVA, SCS, SAP). | Finished in about 100 minutes of the 180 including review; the results email arrived the same evening. States directly that 「DOP向けの教材は、かなり乏しい」 — "study materials for DOP are quite scarce" — which is a first-hand corroboration of the thin-resources problem from someone with six certifications to compare against. On technique: you can usually halve the options on service characteristics alone, and the exam is won on the final discrimination between the two that remain. | Qiita |
| @boloyome 「AWS DOP 受けたら知らないサービスに遭遇した話」 10 June 2026 | No score given. About one year of AWS experience at the time of sitting. | The CodeConnections account described above — the strongest single finding on this page. His conclusion generalises well: reason from where an unknown service sits in the service graph rather than trying to have memorised an exhaustive list. | Qiita |
| @Michie3214 「【AWS DOP-C02】Udemy問題集×Geminiの対話型学習で合格した話」 28 July 2026 | Passed first attempt in July 2026 — the most recent verified sitting. Infrastructure/cloud engineer holding CLF, SAA, SAP, DVA and SOA, with Linux and EKS experience. | A distinctive and well-documented method: three passes over a 226-question set, using an LLM to interrogate each explanation, tracked in a spreadsheet. Reports accuracy on previously-unseen questions rising 42.4% → 83.7% across the cycles. Found the real exam comparable in difficulty to his practice material. | Qiita |
| @Rabbit_booK (Works Human Intelligence) 「AWS DOPが楽しかった話」 31 July 2026 | Declines to give his scaled score, describing it as unremarkable. About a year as an SRE, holding CLF, AIF, SAA, SOA and DVA. | The fast-prep data point: one week of study. Finished the first pass with 20 minutes left but could not review every flagged question. Scored 65% on the official 20-question sample set beforehand, and notes that the sample questions run harder than the real exam. | Qiita |
Also confirmed to exist but not mined individually: @Michinoku (14 June 2026, 合格記), @244-pine-rice-cakes (24 June 2026, first-attempt pass via CloudTech), @motuneko253 (a score table recording DOP-C02 846, passed 2 November 2025), and @damako_eng (June 2026 study notes). They are listed here so you know the corpus is deeper than the four above, not because this page is relying on them.
Go do this yourself before you book. Search Qiita for DOP-C02, sort by newest, and skim the first two pages with your browser's translate turned on. You are looking for three things and nothing else: a scaled score (proof of a real sitting), a date within the last six months, and any service name you don't recognise. Write the unrecognised service names into a list. That list — not somebody's resource roundup — is the highest-value gap analysis available to you, because it is drawn from the exam as it currently exists rather than as its guide describes it. Cross-check anything you find against the Service & Command Reference, and add genuine gaps to Flashcards.
How the 180 minutes actually went
☺ Like you're 10: Nobody said the questions were confusing. They said the questions were long, and that they ran out of concentration before they ran out of clock.
Here is where the accounts converge hardest, across both languages and three years. The adversary in DOP-C02 is not obscurity — it is reading volume and the fatigue that comes with it. Simon Mafany states the arithmetic that drives everything else: "Questions are very lengthy, and you have practically 2.4 minutes to read a question, understand it, read the options, analyze them, eliminate distractors, before select[ing] the best option." That figure is simply 180 minutes divided by 75 questions, and it is the number every tactic on this page exists to protect.
His account of what that felt like is the most quoted thing in the English corpus for a reason: "After the first hour, I felt tired already but still had almost 2/3 of the questions. At the end of the se[cond] hour, I almost lost my concentration." Rishab Kumar reports the same failure mode with a different marker — struggling with focus from around the thirtieth to thirty-fifth question. Two independent people, two years apart, describing a concentration cliff somewhere in the middle third. The proctoring specifics these accounts describe around that clock — the room scan, the no-pen-and-paper rule when you sit at home, when the result actually appears — are collected on Exam Day — What to Expect.
Read the bars together and a pattern falls out that is more useful than any single account. The spread is enormous — one candidate was finished, reviewed and gone at 100 minutes; another was still working with 20 minutes left and could not get back to every flag. What separates them is not intelligence but how much of the answer was already decided before the question appeared. @Crowncrow, with six certifications behind him, describes halving the options on service characteristics alone; that is a decision made in seconds, not minutes, and it is what buys back the eighty minutes.
Every account that mentions flagging describes the same protocol, unprompted: flag, answer anyway, move on. Nobody leaves a flagged question blank — with no penalty for guessing, an unanswered question is a guaranteed zero and a guessed one isn't. Simon Mafany's single miss was a question he flagged and never returned to, which is the exact failure mode this protocol exists to prevent. Set the answer first, then flag it. Answer Triage & Elimination has the full four-pass version.
"I did the arithmetic before I did anything else, because the arithmetic is the plan. Two point four minutes a question. Not 'about three.' A paragraph-long scenario, five options that all work, and a hundred and forty-four seconds. Once I'd written that number on the top of my notes, every other decision made itself — why I stopped re-reading options, why I answered before flagging, why I stopped trying to be certain. Certainty costs about forty seconds a question, and I did not have forty seconds a question to spend."
Where the accounts get it wrong
☺ Like you're 10: Even the good reviews contain a couple of mistakes. Here they are, so you don't copy them.
An honest field-notes page has to correct its own sources. Three claims circulate in public DOP-C02 write-ups that do not survive contact with AWS's own documents.
1. "You must pass at least 57 questions"
Tolu Nimi's write-up states a raw question threshold — a version of "750 means you need n correct out of 65." This is a candidate misconception, and it is the most common one about AWS professional exams. 750 is a scaled score on a 100–1,000 range. AWS states plainly that scaled scoring exists to "equate scores across multiple exam forms," which is precisely what makes it non-convertible to a fixed raw count: the whole point is that a slightly harder form and a slightly easier form map different raw scores to the same scaled 750. AWS does not publish the conversion. Nobody outside AWS can compute it. Any page that gives you a raw question target is guessing, however confidently it phrases it.
2. "Surprisingly, I had 190 minutes"
Also from Nimi's account, against an official 180 on AWS's product page. This is one person's report of one sitting; it may reflect an accommodation, a localisation, or a policy in force at that time. It is not a reason to plan for 190 minutes. Plan for 180. If you get more, that is a gift; if you planned for it and didn't get it, you have designed your pacing around ten minutes that don't exist.
3. "The exam includes ordering, matching and case-study questions"
This one comes from a third-party study guide, not from a candidate — Towards the Cloud's 8-week study plan, published in 2021 and updated since. It is a good, concrete example of how third-party guides drift ahead of the facts. AWS did introduce those three new question types from August 2024, so the claim is not invented out of nothing. But the first exams to carry them were AI Practitioner and Machine Learning Engineer – Associate, with Security – Specialty (SCS-C03) following in December 2025. No official source puts them on DOP-C02, and exam guide v1.6 states only two question types: multiple choice and multiple response. Prepare for two.
Separate observation from inference. "I flagged 25 questions" is an observation and almost certainly true. "You should expect to flag 25 questions" is an inference from a sample of one. "I had 190 minutes" is an observation; "the exam is 190 minutes" is wrong. Then watch how third-party sites launder single reports into fact — a number appears once in one person's honest write-up, gets repeated without attribution on a prep site, and three sites later it is being stated as a specification. Every number in this page's official-facts table names the document it came from precisely so you can check whether that has happened.
Things that look like field notes and aren't
☺ Like you're 10: Some articles are titled "How I passed" but never actually describe passing. Useful, but a different thing.
These are named deliberately, because a page that quietly folded them in with the real accounts would be inflating its own evidence base. All four are worth reading. None of them is testimony about a sitting.
| What it is | Why it isn't a field note | Still worth reading for |
|---|---|---|
| Pushkar Patil — "How I Passed…", Medium, 2 March 2025 | A 3-minute study-plan template: a 30-day plan, a resource list, and generic exam-day tips ("hydrate," "trust your gut"). No score, no exam date, no personal exam-day narrative. | Its format facts are correct. Cite it as a study plan, never as evidence of a sitting. |
| "Paul's Tech Notes" — DOP-C02 study guide (mangh.am) | Explicitly a documentation-first study guide. The author makes no personal claims about sitting the exam at all — which is honest, not a flaw. | Its exam facts are accurate and it correctly identifies guide v1.6 as current. A good reference link. |
| Danny Steenman / Towards the Cloud — "8-Week Study Plan" (towardsthecloud.com) | No personal sitting claimed. Also carries the incorrect question-types claim corrected above. | The week-by-week structure is reasonable; verify its format claims against the exam guide before believing any of them. |
| Ntombizakhona Mabaso — DEV Community guide series (dev.to) | A guide series mapped to exam guide v1.6, not an experience report. | The facts are accurate and the domain mapping is clean. |
r/AWSCertifications is where a lot of candidates assume the real discussion lives, and it may well be. This page cannot tell you, because the research behind it could not retrieve Reddit content — the site was not accessible to the tooling used, and general searches surfaced no threads. So no assertion is made here about what Reddit's DOP-C02 threads say, contain, or agree on. If you can read them, read them; just apply the same observation-versus-inference test to anything you find there, and remember that a forum comment has even less traceability than a signed blog post.
The resources the genuine accounts converge on
☺ Like you're 10: Almost everyone used the same short list — and almost everyone said the free stuff from AWS was better than they expected.
Two findings stand out before the list. First, AWS's own free material is underrated. The official sample-questions PDF contains exactly 20 questions with a full answers section explaining why each distractor is wrong — closer to real question style than most paid material, and free. @Rabbit_booK scored 65% on it before sitting and reports it runs harder than the real exam, which makes it a useful conservative readiness gauge. (Bear in mind the CodeCommit staleness flagged above.) Second, the paid landscape is genuinely thin: @Crowncrow — holding six AWS certifications and therefore in a strong position to compare — states outright that study materials for DOP are scarce, and worked around it with a Japanese Udemy question set and, unexpectedly, a Developer Associate textbook whose chapter exercises he found close to Professional level.
| Resource | Type | Who named it | Note |
|---|---|---|---|
| Official sample questions (20, with explanations) | Official · free | Simon Mafany, @Rabbit_booK | Explains why each distractor is wrong. Still opens with a CodeCommit scenario — treat that specific question as historical. |
| Official exam guide v1.6 | Official · free | Simon Mafany, and every guide worth reading | The only authority for scoring and question types. Its service appendix is the one part not to read as complete. |
| AWS Skill Builder Exam Prep course | Official · free tier | Simon Mafany | Singled out by several candidates as worth the time. |
| AWS DevOps Blog & service documentation | Official · free | Simon Mafany | The most reliable route to services that post-date the exam guide's appendix. |
| Stephane Maarek (Udemy) | Paid course | Simon Mafany, Suraj Solanki | The most-named DOP-specific course in the English accounts. |
| Adrian Cantrill | Paid course | Tolu Nimi | Named alongside KodeKloud in the richest exam-day account. |
| Neal Davis | Paid course | Simon Mafany | Used for the DVA and SOA groundwork rather than DOP itself. |
| KodeKloud AWS learning path | Paid hands-on labs | Tolu Nimi | Hands-on labs, which is where every account says the marginal hour is best spent. |
| Jon Bonso / Tutorials Dojo practice exams & cheat sheets | Paid practice | Tolu Nimi, Simon Mafany, Suraj Solanki, Irene Bonso | The single most-named third-party resource. Note the conflict on Irene Bonso's recommendation — she works there. |
| Japanese Udemy question sets (225–226 questions) | Paid practice | @Crowncrow, @Michie3214 | @Crowncrow rates his set harder than the real exam; @Michie3214 found his comparable. |
↗ Official DOP-C02 sample questions (PDF)
On this site, the equivalent progression is Know It Cold for the facts that must come back without a lookup, Self-Check for untimed drilling with explanations, and the five mock exams run at full length under a real 180-minute clock — because, on this evidence, the thing you most need to rehearse is not knowledge but concentration at minute 110.
Two study methods worth stealing
☺ Like you're 10: Two people described exactly how they studied, in enough detail that you could copy it. Most people don't.
Suraj Solanki: map every topic to work you actually did
The best method in the English set, and it costs nothing. Rather than revising a topic list abstractly, he pairs each revision topic with a specific project memory: multi-account CI/CD ↔ a real GitHub Actions and CodePipeline setup he built; DR strategies ↔ actual disaster-recovery drills he ran; EventBridge ↔ the time he auto-restarted failed ECS tasks. The mechanism is not sentimental — an episodic memory is far more durable than a definition, and DOP-C02 questions are scenarios, which means recall is being cued by situations rather than by terms. If you have production experience, this converts it into exam performance. If you don't, the substitute is building the thing: our capstone lab track exists to manufacture exactly these memories, and The Baseline You Need First is the honest inventory of what DOP-C02 assumes you already have before any of this starts paying off.
Simon Mafany's account independently supports the same claim from the other end. What he credits for specific correct answers is not a course but hands-on memory — recalling how cfn-init scripts and cfn-signal actually behaved, and how deployment hooks failed. Those are things you know because something broke while you were watching, not because you read them.
@Michie3214: three passes, with an LLM interrogating every explanation
The most recent verified sitting, and the most rigorously documented method. Three complete passes over a 226-question set, tracked in a spreadsheet, using an LLM to interrogate each question's explanation rather than simply reading it — asking why the wrong options are wrong, what would have to change for a distractor to become correct, and what the underlying constraint really is. His reported accuracy on previously-unseen questions rose 42.4% → 83.7% across the cycles, which is the right metric to track: accuracy on questions you have already seen measures memory of the question, not knowledge of the material.
Steal the interrogation, not the tool. Take ten questions you got wrong in Self-Check and for each one write three sentences: (a) what constraint in the scenario actually decided the answer — cost, RTO, operational overhead, least privilege, blast radius; (b) what would have to change in the scenario to make your wrong answer the right one; (c) which of the six domains the question was really testing. Sentence (b) is the one that does the work, because it forces you to treat the distractor as a valid design for a different problem — which is exactly what Husain Yusuf meant by "all the answer options could be implemented." Track your accuracy on unseen questions only. Both methods are instances of the same principle — retrieval and elaboration beat re-reading — set out cert-neutrally on How to Study for the Exam.
The consensus that survives all of it
☺ Like you're 10: Strip away the different courses and languages and everybody says the same five things.
Eleven accounts across two languages and three years, with wildly different backgrounds — a first-timer with a year's experience, a recertifier scoring 911, someone who winged it and scraped 756, someone who prepped for a week, someone who prepped for two months. What they agree on is short, and it is worth more than any individual write-up.
| The consensus | What it means for your next study session |
|---|---|
| Hands-on beats theory. Every account that explains why a specific answer came back credits something they had built, broken, or watched fail. | Spend the marginal hour in the capstone or a drill, not on a fourth video. |
| Question length is the adversary, not obscurity. Nobody described the content as cryptic. Several described the reading as exhausting. | Practise at full length, timed. A 20-question set does not rehearse the thing that actually breaks. |
| 2.4 minutes per question is the arithmetic that drives every tactic. | Stop re-reading options. Decide, answer, flag if unsure, move. |
| Flag-and-move-on is universal — and always with an answer already selected. | Never leave a flagged question blank. There is no penalty for guessing and a blank is a guaranteed zero. |
| All the options are implementable. The discrimination is use-case fit against a stated constraint, not technical validity. | Read for the constraint first — cost, RTO/RPO, operational overhead, least privilege, blast radius — then read the options. |
One further thing follows from the shape of the record rather than from any single account: your service list will be stale before your exam is. The drift documented above is not a one-off — it is what happens when a certification's appendix updates more slowly than AWS ships and retires services. Treat "check recent first-hand posts for service names I don't recognise" as a standing part of prep rather than a task you complete once. For turning everything else here into weeks and sessions, the DOP-C02 study plan is the schedule.
Before you book, you should be able to say all five out loud without looking: the two question types the current guide allows; how many of the 75 questions are scored; what a scaled 750 does not tell you; which service the current exam guide has dropped and which one candidates report meeting that the guide never lists; and what your average seconds-per-question budget is. If any of those needs a lookup, you are not ready to spend $300 finding out.
Doing your own research without getting farmed
☺ Like you're 10: Search smarter, and check every claim against the rulebook before you believe it.
This page will go stale too — that is the nature of it. So here is the method rather than just the output.
- Start from the official documents, not the search results, so every later claim has something to be checked against. A write-up that contradicts the guide on scoring or question types is wrong, however confident it sounds.
- Search Qiita for the exam code, sorted by newest, and look for the 合格体験記 tag — the highest-yield single move available to an English-speaking candidate.
- Filter for three markers of a real sitting: a scaled score, a date, and some exam-day texture. An article with none of the three is a study plan wearing a field-note title.
- Note who is selling something — not to dismiss them, but to weight their resource recommendations differently from their exam-day observations.
- Collect unfamiliar service names into a gap list. It is the only part of this the official guide structurally cannot give you.
- Re-check anything numeric on the product page before you book. Price, duration, question count, validity and languages all live there, and all change.
"I lost an entire evening to a '2026 Ultimate Guide' before I noticed it never once said who had taken the exam. Four thousand words, a bullet list of every AWS service, and not a single sentence beginning with 'I.' Now that's the first thing I check — does anybody in this article claim to have sat in the chair? If not, it's a reading list. Reading lists are fine. They're just not evidence, and I'd been reading it like it was."
Foxy: Good news — people have actually written this exam up. Seven in English, a whole shelf in Japanese. Bad news: page one of my search was four dump sites and a mobile app.
Nutty: That's why I catalogue by author, not by search rank. Seven names in English. Four Japanese posts read properly, four more confirmed to exist. Everything filed with a date and a score, or clearly marked as having neither.
Timmy: And one of the seven says you need fifty-seven questions right. He passed, he was generous enough to publish, and that sentence is still wrong. Seven-fifty is a scaled score. There is no conversion.
Gizmo: Nobody's going to check! Just say fifty-seven, it sounds so much more actionable! 🤑
Timmy: No. "AWS does not publish the conversion" is a true sentence. It's a better sentence than a helpful invented one.
Benny: The bit that actually changed my prep was the service list. The guide dropped CodeCommit. Two different candidates say CodeConnections turned up on the live exam, and it's on no official list at all.
Professor Owl: Which is the general lesson, Benny. The appendix is a floor. It says so in its own wording — non-exhaustive, subject to change. Study the shape of the service graph and an unfamiliar name stops being frightening.
Sol: And do the arithmetic before anything else. Two point four minutes a question. Everything else on this page is downstream of that number.
Pip: One more from the accounts — at a testing centre the result is usually on screen. One candidate sat it online at midnight and waited about sixteen hours for the email. Don't panic-refresh; that's someone's real experience, not a failure signal.
Foxy: Fine. So the honest summary is: plenty of evidence, badly ranked, half of it in Japanese, and two of its numbers are wrong.
Timmy: That's the summary. Which is why we wrote the names down.
1. Which two documents publish DOP-C02's facts, and which of them states the price and the 180-minute clock? 2. What does the current exam guide say about AWS CodeCommit, and what do candidates report about AWS CodeConnections? 3. Why can't a scaled score of 750 be converted into "n questions correct"? 4. What does compensatory scoring change about how you treat a weak domain? 5. Where is the most recent first-hand DOP-C02 evidence published, and what should you be looking for in it? 6. Name one published claim about DOP-C02 that this page corrects, and say what the official source actually states.
Check your answers
- The exam guide (currently v1.6) publishes question types, the 65-scored/10-unscored split, the 100–1,000 scaled range, the 750 minimum, compensatory scoring and the domain weights. The certification product page publishes the 180 minutes, 75 questions, 300 USD, the languages and the 3-year validity. Neither document contains the other's numbers, which is why third-party pages mix them up.
- Exam guide v1.6 does not mention CodeCommit anywhere — it was in the launch-era v1.0 list and has been dropped — while AWS's own free sample-questions PDF still opens with a CodeCommit scenario. CodeConnections appears nowhere in the v1.6 in-scope list, yet two independent candidates (@boloyome on Qiita, June 2026; Irene Bonso, 2025) report meeting it on the live exam. The appendix is a floor, not a ceiling.
- Because scaled scoring exists specifically to equate scores across different exam forms that vary slightly in difficulty — so the same raw count can map to different scaled scores on different forms, and vice versa. AWS does not publish the conversion, so any stated raw target is a guess.
- There is no per-domain pass bar — you pass only the overall exam. So a weak domain costs you exactly its weight (as little as 14%), not a separate gate, and the right question is always "where does the next study hour buy the most scaled points," which usually means shoring up a mediocre large domain rather than perfecting a small one.
- Qiita, the Japanese developer-writing platform — roughly 187 results for
DOP-C02, many tagged 合格体験記, with several detailed 2026 sittings reporting exact scaled scores. Look for three markers: a scaled score, a recent date, and any service name you don't recognise (that last one is your gap list). - Any one of: (a) the claim that you "must pass at least 57 questions" — 750 is scaled and has no published raw conversion; (b) the report of "190 minutes" — the product page states 180, so plan for 180; (c) the third-party claim that DOP-C02 includes ordering, matching and case-study questions — exam guide v1.6 states only multiple choice and multiple response, and the new types debuted on other AWS exams.
Next: turn all of this into a schedule with the DOP-C02 study plan, or find out where you actually stand with Mock Exam · Set 1 at full length and on the clock.