Most exam guides tell you which domains matter. The Claude Certified Developer Foundations guide (CCDV-F) goes further: Section 6 assigns a weight to each of 25 individual skills. That turns the blueprint into something more useful than a list of topics. It tells you where the points are, which skills you probably already have, and how to split your study time. This guide turns those weights into a four-week plan. If you are still deciding between exams, start with how the CCDV-F compares with the Architect exam.
Start with the format
Section 5 of the exam guide (CCDV-F) sets out the basics:
- 53 items in 120 minutes, which works out to about 2 minutes 15 seconds per item.
- Multiple-choice and multiple-response items. Each item states how many responses to select.
- A scaled passing score of 720 on a scale of 100 to 1,000.
- Proctored delivery, online or at a test center.
The multiple-response format deserves attention early. An item that asks for two answers rewards reading each option on its own merits rather than picking the single best one, and that habit takes practice to build.
Where the points are
Section 6 of the guide (CCDV-F) gives each domain an approximate share of the scored items:
- Applications and Integration: 33.1%
- Model Selection and Optimization: 16.8%
- Agents and Workflows: 14.7%
- Prompt and Context Engineering: 11.0%
- Tools and MCPs: 10.6%
- Security and Safety: 8.1%
- Claude Code: 3.1%
- Eval, Testing, and Debugging: 2.6%
The top three domains add up to 64.6%, nearly two-thirds of the exam. The bottom two add up to 5.7%. As a rough guide, 33.1% of 53 items is about 17 or 18 questions, while 2.6% is one or two. The guide describes its weights as approximate shares of scored items and does not say how many of the 53 are scored, so treat those counts as estimates, not a promise.
One trap is worth flagging. Claude Code carries only 3.1% as a domain, but Claude Code topics also appear elsewhere. The Configuration Management skill under Applications and Integration covers CLAUDE.md files, settings.json, model version pinning and plugin dependencies. Low domain weight does not mean you can skip the tool.
About a fifth of the exam is general engineering
Four of the 25 skills describe software engineering that is not specific to Claude:
- Software Engineering Foundations (7.4%): REST APIs, JSON, asynchronous programming, version control, code review and refactoring.
- Technical Fundamentals (6.1%): basic engineering practices such as integrating with SDKs that wrap REST APIs, and websockets.
- Understanding Requirements (3.4%): functional and infrastructure requirements based on business requirements and solution architecture.
- Systems Life Cycle (2.8%): the frameworks used to develop, run and maintain IT systems.
Together that is 19.7% of the exam. For working developers, this is a head start: these are skills you use every week. For career changers, it is a warning. Section 4 of the guide (CCDV-F) recommends one to five years of software engineering experience, proficiency in Python or TypeScript, and fluency with REST APIs and command line tools. None of that is a formal prerequisite, but a fifth of the exam assumes it.
The six skills that matter most
Sorted by weight, the six largest skills account for 39.4% of the exam on their own:
- Claude Application Design (8.6%): how Claude interprets instructions across Claude Code, Desktop, claude.ai, the API and SDKs, plus content boundaries, schema design, session hygiene and plugin management.
- Software Engineering Foundations (7.4%).
- Claude API Mechanics (6.8%): messages, tools, streaming, vision, thinking, caching, batch use, and choosing between realtime and batch requests.
- Technical Fundamentals (6.1%).
- Agent Construction with Claude (5.3%): the Claude Agent SDK, custom agent loops and harnesses, self-hosted versus Anthropic-hosted deployment, and hooks for deterministic actions.
- LLM Fundamentals (5.2%): tokens, context windows, sampling, non-determinism, model options such as extended thinking and effort levels, and zero-shot to multi-shot prompting.
If your time is short, these six come first.
A four-week plan
This plan assumes the background Section 4 recommends, including at least six months of hands-on work with Claude or a comparable LLM system. Each week groups related skills and carries roughly a quarter of the exam's weight.
Week 1: Building on the API (19.5%)
Claude API Mechanics, Claude Application Design and Configuration Management. Work directly against the Messages API: streaming, tool use, vision input and prompt caching. Decide when a job belongs in the batch API rather than realtime calls. Set up a CLAUDE.md file and settings.json for a real repository, and pin a model version so you can explain why that matters.
Week 2: Models, tokens and context (27.8%)
All of Model Selection and Optimization (16.8%) and Prompt and Context Engineering (11.0%). Compare model tiers on the same task for quality, latency and cost. Track token usage and model the cost of a workload, with and without caching. Then practice the prompt side: clear instructions, few-shot examples, system versus user placement, and managing a growing context window through pruning and compaction. Finish with output handling: validate structured output and parse defensively instead of trusting a confident answer.
Week 3: Agents and tools (25.3%)
Agents and Workflows (14.7%) and Tools and MCPs (10.6%). Learn when a fixed workflow beats an agent, and how supervisor hierarchies and subagents divide a task. Build a custom tool with a precise description and real error handling; the case for tool error messages written for the model applies directly here. Write a small MCP server and review the common MCP server design mistakes before you do. The Agentic Customization skill (4.1%) asks you to choose between built-in tools, custom tools, Skills and MCP servers, so practice explaining that choice for a given use case.
Week 4: Security, the small domains, and a full mock (27.4%)
Security and Safety (8.1%), Claude Code (3.1%), debugging (2.6%), and the general engineering skills under Applications and Integration (13.6%). On security, work through the AI Application Security skill as Section 6 describes it: prompt injection awareness and mitigation, jailbreak defense, untrusted input handling, data leakage prevention and PII handling. Then cover the Claude Hooks skill, which the guide frames as using hooks for guardrails that prevent destructive actions, and review how you manage secrets and API keys across development and production. For debugging, practice telling an integration-layer failure apart from a model-output failure by reading traces. Then take a full timed mock and review every miss by skill, not just by domain.
Build one thing that covers the blueprint
Section 7 of the guide (CCDV-F) recommends building and operating at least one Claude application that exercises the API, integrates one or more tools, applies basic prompt and context engineering, and includes simple security and evaluation practices. The four weeks above map onto that build: the API layer in week 1, model and prompt decisions in week 2, tools and an agent loop in week 3, guardrails and tests in week 4.
Building also gives you something to show. A finished, well-documented repository is evidence for an employer in a way a score report is not, and the steps for turning a study build into a portfolio project apply to either exam.
Practice the format, not just the content
Section 7 also points to the guide's sample questions in Section 8 for item style. Those are few, and they are illustrative rather than drawn from the live bank. For volume, our CCDV-F practice questions cover all eight domains, and each explanation covers why every other option is wrong. Use them in two ways: short domain drills during the four weeks, and a full 53-question mock under the 120-minute limit at the end. When a timed mock goes badly, look at which skills the misses cluster in before rereading anything.
Before and after exam day
- Eligibility and cost: registration currently runs through organizations in the Claude Partner Network, and our guide to getting your employer to pay explains who can register and how partner discounts work.
- Scheduling: under Section 10 of the guide (CCDV-F), you register through Anthropic Partner Academy and schedule with Pearson VUE. You can cancel or reschedule up to 24 hours before your appointment.
- On the day: the ID, workspace and conduct rules in Sections 11 and 12 match the Architect exam's, so our walkthrough of exam-day logistics, from ID checks to online proctoring applies.
- If you don't pass: Section 11 sets waiting periods of 14, 30 and 90 days after the first three failed attempts, and up to four attempts in a rolling 12 months. See how retakes and waiting periods work.
- After you pass: under Section 14, the credential is valid for 12 months and on-time renewal is a free, non-proctored assessment. Our guide to how the free renewal works covers the same process for the Architect credential.
Where to start
Read Section 6 of the guide once, end to end, and mark each of the 25 skills as strong, partial or new. Put the new and partial skills from the top six into week 1 or 2, whatever the plan above says. The weights tell you where the points are; your own gaps tell you where the work is.
FAQ
How many questions are on the CCDV-F exam?
Section 5 of the exam guide (CCDV-F) lists 53 items in 120 minutes, a mix of multiple-choice and multiple-response items. Each item states how many responses to select. The passing score is a scaled 720 on a scale of 100 to 1,000.
Which CCDV-F domains carry the most weight?
Under Section 6 of the guide (CCDV-F), Applications and Integration carries 33.1%, Model Selection and Optimization 16.8%, and Agents and Workflows 14.7%. Together those three domains are 64.6% of the exam.
How much of the CCDV-F is about Claude Code?
The Claude Code domain is weighted at 3.1% in Section 6 of the guide (CCDV-F). Claude Code topics also appear under Configuration Management, which covers CLAUDE.md files, settings.json and plugin dependencies, so the tool matters more than the domain weight suggests.
Do I need experience before taking the CCDV-F?
There are no mandatory prerequisites. Section 4 of the guide (CCDV-F) recommends one to five years of software engineering experience, at least six months of hands-on work with Claude or a comparable LLM system, proficiency in Python or TypeScript, and fluency with REST APIs and command line tools.