I passed the Claude Certified Developer – Foundations (CCDV-F) exam with a score of 941. The pass mark is 720.
The exam only launched in July 2026, so there isn't much prep material out there yet. No Udemy course, no well-worn Reddit threads, no "top 50 questions" gists. So I did the obvious thing for an exam about Claude: I used Claude to prepare for it.
Here's the exact workflow, the prompts, and what I'd tell anyone sitting it next.
Step 1: Turn the exam guide into mock exams
Start with the official scope. I used this CCDV-F exam guide, which lays out the domains the exam covers.
I pasted the guide into Claude and asked it to generate full mock exams from it. My setup:
- Model: Opus. For generating realistic, well-reasoned questions and explanations, the extra horsepower is worth it.
- Tool: Cowork. It handles multi-step tasks well and can save each mock exam as a file you can come back to.
A prompt along these lines works well:
Here is the exam guide for the Claude Certified Developer – Foundations exam.
<COPY PASTE SCOPE HERE>
Generate a full-length mock exam that covers every domain in the guide,weighted the way the guide weights them. Use the same question style as the real exam. Don't show the answers until I've submitted mine, then mark me and explain why each wrong answer was wrong.
Step 2: Over-prepare with a harder difficulty
If you want to over-prepare (I did), ask Claude to make the mocks harder than it thinks the real exam will be. Think of it as load testing: if you're comfortable under peak traffic, normal traffic is easy.
Generate another mock exam, but make it noticeably harder than you
expect the real exam to be: trickier distractors, more edge cases,
and questions that combine multiple domains.
My mix:
| Mock exams | Difficulty |
|---|---|
| 2 | Harder than expected |
| 2 | Normal |
The real exam was nowhere near as difficult as the harder mocks. That gap is exactly what you want walking in. The other added benefit is that you will learn more and it will sharpen you as an Engineer.
As you go, log every question you get wrong. A simple running list works: the question, your answer, the right answer, and one line on why. That list becomes your revision material at the end. You can also ask Claude to keep it for you in a file inside Cowork.
Step 3: Questions first, theory second
Only after a few mocks did I ask Claude for a summary of the facts and concepts to remember for the exam.
Based on the exam guide and the questions I got wrong (attached),
give me a concise summary of the key facts and concepts I need to
know for the exam. Prioritise the areas where I made mistakes.
The order matters. It's the same reason you understand a codebase faster after debugging it than after reading the docs cold. Once you've wrestled with a question and got it wrong, the theory behind it is no longer abstract. It answers a question you already care about, so it's more interesting and much more likely to stick.
In the last few days, go back through your list of wrong answers alongside the summary.
Where to focus: follow the weightings
I didn't hit a domain that felt especially hard, and I scored close to 100% in most of them. So rather than pointing at a tricky topic, my advice is to budget your study time by the blueprint weights. The exam has 53 questions across eight domains, and the weighting is very uneven (source).
| Domain | Weight | Tip |
|---|---|---|
| Applications and Integration | 33.1% | If you haven't built against the Claude API before, a small hands-on project will make these questions click. Make sure it covers auth, requests, streaming, error handling and config. If you've built with the API before, mock exams and a skim of the docs are enough. |
| Model Selection and Optimisation | 16.8% | Know the trade-offs between model tiers and how token usage drives cost. Be ready to pick a model for a given job. |
| Agents and Workflows | 14.7% | Understand the agent loop and common patterns. Building one simple agent teaches more than reading about many. |
| Prompt and Context Engineering | 11.0% | Practise structured prompts and output handling. Know what belongs in context and what doesn't. |
| Tools and MCPs | 10.6% | Define a tool, then stand up a minimal MCP server. The moving parts click once you've wired them yourself. |
| Security and Safety | 8.1% | Treat it like any production app: secrets out of code, keys managed properly, guardrails on inputs and outputs. |
| Claude Code | 3.1% | Light weight. If you use it day to day, you're probably covered. |
| Eval, Testing, and Debugging | 2.6% | Light weight. Know the common API errors and how to handle them. |
The top three domains make up nearly two-thirds of the marks. If you're short on time, start there.
On the exam day
- Read every question thoroughly. The detail that decides the answer is often in the last line.
- Pick the answer that makes sense in practice. Plenty of questions come down to thinking like a software engineer on the job. If an option is technically possible but nobody would ship it, it's probably a distractor.
- Don't panic about time. You get 2 hours. I finished in about 70 minutes with no rush, so there's room to re-read the questions you're unsure of. There’s also an option to flag questions and come back to them at the end.
TL;DR
- Feed the exam guide to Claude (Opus, in Cowork) and generate mock exams.
- Do 2 harder-than-real mocks and 2 normal ones.
- Log every question you get wrong.
- Only then ask Claude for a summary of key facts and concepts.
- Revise your wrong answers alongside the summary.
- On the day: read carefully, think practically.
Good luck. If you've sat the exam too, drop your tips in the comments.
Top comments (0)