Use a completed test
A timed exam-ready test is preferred when one is available.
Claude Certified Developer · Anthropic
Choose your next best preparation step
Use your completed test evidence, Personalized Study Plan, and remaining study schedule to choose your next practical step.
✓READYNext step✓Testevidence▤Studyplan→Nextaction
How readiness guidance works
How readiness guidance is formed
Your completed test evidence and study-plan progress are combined to recommend one practical next step.
Check the current plan
Compare the remaining schedule with the tasks still planned in your study plan.
Choose the next action
Practice, reinforce gaps, or continue the plan with fresh evidence.
What readiness means for Claude Certified Developer – Foundations
Readiness means you can translate requirements into a production-oriented Claude system and defend its agent, API, model, prompt, context, evaluation, security, tool, and MCP decisions.
- You can apply the published objectives without notes in fresh scenarios.
- You can produce code, configuration, traces, tests, metrics, or security evidence for important decisions.
- You can identify why plausible alternatives fail the stated requirement.
Guidance only — not a pass prediction.
CCDV-F readiness by exam domain
Domain evidence is weighted with the official blueprint percentages, which total 100%; these are official approximate item proportions, not internal guidance weights.
| Exam dimension | Weight | Evidence focus |
|---|---|---|
| Agents and Workflows | 14.7% | Readiness to apply and explain the published Agents and Workflows objectives in fresh production-oriented scenarios. |
| Applications and Integration | 33.1% | Readiness to apply and explain the published Applications and Integration objectives in fresh production-oriented scenarios. |
| Claude Code | 3.1% | Readiness to apply and explain the published Claude Code objectives in fresh production-oriented scenarios. |
| Eval, Testing, and Debugging | 2.6% | Readiness to apply and explain the published Eval, Testing, and Debugging objectives in fresh production-oriented scenarios. |
| Model Selection and Optimization | 16.8% | Readiness to apply and explain the published Model Selection and Optimization objectives in fresh production-oriented scenarios. |
| Prompt and Context Engineering | 11% | Readiness to apply and explain the published Prompt and Context Engineering objectives in fresh production-oriented scenarios. |
| Security and Safety | 8.1% | Readiness to apply and explain the published Security and Safety objectives in fresh production-oriented scenarios. |
| Tools and MCPs | 10.6% | Readiness to apply and explain the published Tools and MCPs objectives in fresh production-oriented scenarios. |
What to review before your next practice test
Use these fixed study suggestions from the published Readiness package before you test again.
1Priority 1 — Agent Architecture
- Distinguish deterministic workflows from agents that dynamically direct steps and tool use.
- Select manager, supervisor, and subagent structures based on task uncertainty, isolation, and coordination needs.
2Priority 2 — Agent Construction with Claude
- Implement the request, tool-call, tool-result, and continuation loop.
- Choose between custom harnesses, the Claude Agent SDK, self-hosted deployment, and Anthropic-hosted options.
Maintain: Agent Patterns and Frameworks
- Use Smart Review to prioritize weighted gaps.
- Require fresh implementation or trace evidence before increasing a rating.