Guides / Failed CCDV-F
Failed CCDV-F? Here's what to do next
A failed attempt on Claude Certified Developer is recoverable. You can retake after a 14-day wait, up to 4 attempts in any rolling 12 months, and the retake fee is $125. This guide turns the rules into a plan.
1. Know your retake window
The wait grows with each failed attempt, so it pays to make the next sitting count.
| If you have failed | You can retake after | Fee for that attempt |
|---|---|---|
| 1 time | 14 days | $125 |
| 2 times | 30 days | $125 |
| 3 times | 90 days | $125 |
| 4 attempts used | Until the oldest attempt is more than 12 months old | - |
Full exam fee each attempt, with your Partner Network tier discount applied if you have one. Retake rules from Anthropic's Partner Academy FAQ, last checked 2026-09-21. Enter your fail date in the retake calculator for your exact earliest date.
2. Plan the cost of the next attempt
Every attempt is $125 before any tier discount, so 4 attempts in a window is at most $500 in exam fees. Add your own study or training spend in the cost calculator to see the full picture before you rebook.
3. Find where you lost points
Before you rebook, work out what to change. Take the free CCDV-F diagnostic for a per-domain score ranked weakest-first, and check whether your Pearson VUE score report gives any breakdown by domain.
Where the points are
The blueprint tells you where a re-study hour buys the most. The three heaviest domains carry about 65% of the exam.
| Domain | Exam weight | Practice questions here |
|---|---|---|
| Applications & Integration | 33% | 83 |
| Model Selection & Optimisation | 17% | 43 |
| Agents & Workflows | 15% | 38 |
| Prompt & Context Engineering | 11% | 27 |
| Tools & MCPs | 10% | 25 |
| Security & Safety | 8% | 20 |
| Claude Code | 3% | 7 |
| Eval, Testing & Debugging | 3% | 7 |
Developer weight is concentrated: Applications & Integration is about a third of the exam by itself. That domain is API mechanics - the stateless Messages API, stop_reason values and what each one demands of your loop, the streaming event lifecycle, and which errors are retryable. After that come model selection and optimisation, agents and workflows, and prompt and context engineering.
Common wrong turns in the heaviest domains
These are exam traps from this site's own CCDV-F lessons, one from each of the heaviest domains first. If you picked one of these on the real exam, that lesson is your next stop.
- Putting the system prompt inside the messages array as a role: system entry. The Messages API takes system as its own top-level parameter, separate from messages. A messages array with a system role either errors or is silently misinterpreted depending on the client library. Review: 1.1 - The Messages API: Requests and Responses
- Choosing the most capable (and most expensive) model tier for every request in an application, regardless of task difficulty. Simple, high-volume tasks rarely need top-tier reasoning capability; using it everywhere burns budget and adds latency without a matching quality benefit. Review: 2.1 - Claude Model Family and Trade-offs
- Using a fixed iteration cap as the primary way the loop decides it's finished. A cap is a legitimate safety net against runaway loops, but using it as the primary stop signal either cuts off a task that genuinely needed more steps or burns iterations a finished task didn't need - stop_reason is the correct primary signal. Review: 3.1 - Building an Agentic Loop
- Treating each input_json_delta fragment as a complete, independently parseable JSON object. Deltas are partial string fragments of one JSON object; only the fully concatenated string, assembled by the time content_block_stop fires, is valid JSON. Review: 1.2 - Streaming Responses
- Assuming reducing the number of API calls is always the most effective cost lever. Cost is driven by token volume across input, cached input, and output - a smaller number of token-heavy calls isn't automatically cheaper than a larger number of lean ones. Review: 2.2 - Token Economics: Counting, Budgeting and Pricing
- Reaching for a multi-agent architecture as the default for any moderately complex task. Added agents mean added coordination overhead, cost, and failure surface; the added complexity should be justified by a concrete need for isolation or parallelism, not applied by default. Review: 3.2 - Single-Agent vs. Multi-Agent Orchestration
4. Re-plan your study time
Set a new exam date on or after your eligible retake date, then let the study time calculator turn it into a daily target and a domain-by-domain split weighted by the blueprint. Then work the weakest domains with drill mode and timed mocks.