The CCDV-F credential is described as "foundational." What does this most directly signal about who should earn it?
It certifies world-class AI research expertise in model training
It proves you can competently build and ship real, production Claude-powered systems
It is meant for non-technical users who chat with Claude applications
It is limited to people whose only skill is writing prompts
Every question on the exam is calibrated to the Minimally Qualified Candidate (MQC). What is the practical consequence of that design for a test-taker?
If you know more than the MQC you should pass comfortably; if you know less, the exam is designed to detect it
Only the single strongest candidate in each testing window passes
The exam ignores tradeoffs and asks only definition questions
Prior certifications are required before you can be considered an MQC
A candidate lets their CCDV-F credential lapse past its validity window. What is required to regain certified status?
Nothing; the credential auto-renews indefinitely
A short free quiz, the same as on-time renewal
Retaking the full exam at full fee
Completing a mandatory prerequisite course first
The Certification and Its Value
Key Points
- The CCDV-F credential is an independent, foundational proof that you can build, integrate, and ship production-grade Claude applications, agents, and workflows.
- It is aimed at working engineers — roughly 1–5 years of software experience and at least 6 months on Claude or a comparable LLM.
- Every item is calibrated to the Minimally Qualified Candidate (MQC): a hands-on technical individual who understands real-world tradeoffs, not just definitions.
- There are no mandatory prerequisites; the credential is earned on exam performance alone and is valid for 12 months.
- On-time renewal is a free, non-proctored assessment on the Anthropic Partner Academy; a lapsed credential requires retaking the full exam at full fee.
The Claude Certified Developer – Foundations certification (exam code CCDV-F) validates that an individual can build, integrate, and ship production-grade applications, agents, and workflows using Anthropic's Claude platform at a foundational level. Earning it sends a clear signal to employers, clients, and teammates: this person can translate a business requirement into a working system that uses Claude — through API integration, agent and tool construction, prompt and context engineering, evaluation, security, and model selection.
A useful analogy is a private pilot's license: it does not certify that you can fly a fighter jet, but it certifies that you can safely and independently operate an aircraft under normal conditions. The CCDV-F says you can safely take a Claude application from the runway of an idea to the cruising altitude of production. Because the underlying technology evolves rapidly, the credential is valid for 12 months from the date it is awarded.
The exam is targeted at the Minimally Qualified Candidate (MQC) — the theoretical person who has just barely enough skill to be considered competent. The audience is AI/ML engineers, technical leads, and senior software engineers. It is explicitly not for non-technical or casual users, individuals without hands-on development experience, or roles limited to prompt writing alone.
Recommended Experience
| Recommended Experience Area | Target Level |
| General software engineering | 1–5 years |
| Hands-on Claude (or comparable LLM) experience | At least 6 months |
| Programming languages | Proficiency in Python and/or TypeScript |
| Interfaces | Fluency with REST APIs and CLI tools |
| Conceptual grounding | LLM fundamentals, agents, context management, MCP |
Notice how often the word tradeoff appears in the MQC profile. That is a strong hint about the exam's cognitive level: it rarely asks "what is X?" and far more often asks "given these constraints, which of these four reasonable-sounding approaches is best?"
Visual animation — coming soon
The CCDV-F credential is described as "foundational." What does this most directly signal about who should earn it?
It certifies world-class AI research expertise in model training
It proves you can competently build and ship real, production Claude-powered systems
It is meant for non-technical users who chat with Claude applications
It is limited to people whose only skill is writing prompts
Every question on the exam is calibrated to the Minimally Qualified Candidate (MQC). What is the practical consequence of that design for a test-taker?
If you know more than the MQC you should pass comfortably; if you know less, the exam is designed to detect it
Only the single strongest candidate in each testing window passes
The exam ignores tradeoffs and asks only definition questions
Prior certifications are required before you can be considered an MQC
A candidate lets their CCDV-F credential lapse past its validity window. What is required to regain certified status?
Nothing; the credential auto-renews indefinitely
A short free quiz, the same as on-time renewal
Retaking the full exam at full fee
Completing a mandatory prerequisite course first
A candidate reasons: "The cut score is 720 out of 1,000, so I only need to answer about 72% of questions correctly." Why is this reasoning flawed?
A scaled score is not the same as percent-correct; the raw percentage needed is set by a standard-setting study
The passing score is actually 620, not 720
The exam has no fixed passing score at all
Percent-correct and scaled score are always identical by definition
Because the CCDV-F is criterion-referenced, what is true about how you are evaluated?
Only a fixed top percentage of candidates can pass, regardless of skill
You are measured against a fixed competency standard (the MQC), not against other candidates
You are ranked on a curve against everyone in your testing window
Your per-domain percentages determine pass or fail
Your score report shows per-domain percent-correct figures. What role do those figures play in the pass/fail decision?
You must pass each individual domain to pass the exam
The lowest domain percentage is used as your final score
They are informational only; only the total scaled score decides pass/fail
Domain percentages replace the scaled score entirely
With 53 items in 120 minutes (~2 min 15 sec each), what pacing strategy does the chapter recommend?
Spend equal time on every item regardless of difficulty
Answer the ones you know quickly, then bank time for dense multi-part scenario questions
Skip all scenario questions to save time
Answer every question in strict order without skipping
Exam Format and Scoring
Key Points
- The exam is 53 items in 120 minutes (~2 min 15 sec per item), mixing multiple-choice and multiple-response formats; each item states how many responses to select.
- It is scored on a 100–1,000 scale with a 720 cut score; the fee is $125 USD and delivery is proctored (Pearson VUE, online or test center).
- A scaled score is not percent-correct; the raw percentage needed to reach 720 is fixed by a standard-setting study, keeping passing difficulty constant across forms.
- The exam is criterion-referenced: you are measured against a fixed standard (the MQC), never ranked against other candidates.
- Per-domain percentages are informational only; only the single total scaled score determines pass or fail.
| Attribute | Detail |
| Exam code | CCDV-F |
| Number of items | 53 |
| Item format | Multiple-choice and multiple-response; each item states how many responses to select |
| Time limit | 120 minutes |
| Delivery | Proctored: online-proctored and/or test center (Pearson VUE) |
| Passing score | Scaled score of 720 on a scale of 100–1,000 |
| Exam fee | $125 USD |
| Validity period | 12 months from award date |
| Result reporting | Pass/fail with scaled score, plus percent-correct by domain |
A scaled score is not the same as "percent correct." A raw score is converted through a statistical process into a point on the 100–1,000 scale, letting Anthropic keep the difficulty of passing constant even when candidates receive slightly different question sets. Do not walk in assuming you can miss 28% of questions.
The CCDV-F is criterion-referenced: each candidate is measured against a fixed performance standard, not against other candidates. Contrast this with a norm-referenced exam graded on a curve, where only a fixed share passes.
| Dimension | Criterion-Referenced (CCDV-F) | Norm-Referenced (the alternative) |
| You are compared to... | A fixed standard (the MQC) | Other test-takers |
| Can everyone pass? | Yes, if all are qualified | No, a fixed share is capped out |
| "Graded on a curve"? | No | Yes |
| What passing means | You met a defined bar of competence | You beat enough peers |
The passing standard was established through a formal standard-setting study, in which trained subject-matter experts judged the performance expected of a minimally qualified candidate. Your score report shows per-domain percent-correct, but those figures help you understand performance — they do not determine pass/fail. Only the total scaled score does, so you cannot "fail" a single domain.
Visual animation — coming soon
A candidate reasons: "The cut score is 720 out of 1,000, so I only need to answer about 72% of questions correctly." Why is this reasoning flawed?
A scaled score is not the same as percent-correct; the raw percentage needed is set by a standard-setting study
The passing score is actually 620, not 720
The exam has no fixed passing score at all
Percent-correct and scaled score are always identical by definition
Because the CCDV-F is criterion-referenced, what is true about how you are evaluated?
Only a fixed top percentage of candidates can pass, regardless of skill
You are measured against a fixed competency standard (the MQC), not against other candidates
You are ranked on a curve against everyone in your testing window
Your per-domain percentages determine pass or fail
Your score report shows per-domain percent-correct figures. What role do those figures play in the pass/fail decision?
You must pass each individual domain to pass the exam
The lowest domain percentage is used as your final score
They are informational only; only the total scaled score decides pass/fail
Domain percentages replace the scaled score entirely
With 53 items in 120 minutes (~2 min 15 sec each), what pacing strategy does the chapter recommend?
Spend equal time on every item regardless of difficulty
Answer the ones you know quickly, then bank time for dense multi-part scenario questions
Skip all scenario questions to save time
Answer every question in strict order without skipping
Which single domain accounts for roughly one-third of the exam — more than the bottom five domains combined?
Agents and Workflows
Applications and Integration
Model Selection and Optimization
Tools and MCPs
What is the recommended way to allocate study time using the blueprint?
Give every domain exactly equal time to be safe
Weight time roughly in proportion to domain weights, then personalize against your own gaps
Study only the two smallest domains since they are easiest
Ignore the blueprint and study in textbook order
An engineer already builds production REST integrations daily. How should they refine the pure weight-based plan?
Trim Applications and Integration hours and redirect them to a weaker area like MCP server authoring
Double the Applications and Integration hours since it is the largest domain
Drop all study of the small domains entirely
Study every domain for identical hours regardless of strengths
Together, which three top-weighted domains make up nearly two-thirds (~64.6%) of the exam?
Claude Code; Eval, Testing, and Debugging; Security and Safety
Applications and Integration; Model Selection and Optimization; Agents and Workflows
Prompt and Context Engineering; Tools and MCPs; Security and Safety
Agents and Workflows; Claude Code; Tools and MCPs
The Eight-Domain Blueprint
Key Points
- The content blueprint defines eight domains, each with a domain weight — the approximate proportion of scored items drawn from that domain.
- The distribution is deliberately lopsided: Applications and Integration alone is 33.1%, more than the bottom five domains combined.
- The top three domains — Applications and Integration (33.1%), Model Selection and Optimization (16.8%), and Agents and Workflows (14.7%) — total ~64.6%.
- The smallest domains, Claude Code (3.1%) and Eval/Testing/Debugging (2.6%), together account for under 6%.
- Allocate study time in proportion to the weights, then personalize against your own gaps versus the MQC profile.
| # | Content Domain | Weight | Approx. Items (of 53) |
| 1 | Agents and Workflows | 14.7% | ~8 |
| 2 | Applications and Integration | 33.1% | ~18 |
| 3 | Claude Code | 3.1% | ~2 |
| 4 | Eval, Testing, and Debugging | 2.6% | ~1 |
| 5 | Model Selection and Optimization | 16.8% | ~9 |
| 6 | Prompt and Context Engineering | 11.0% | ~6 |
| 7 | Security and Safety | 8.1% | ~4 |
| 8 | Tools and MCPs | 10.6% | ~6 |
| — | Total | 100% | 53 |
Figure 1.1: The eight exam domains grouped by weight tier
graph TD
Exam["CCDV-F Exam: 53 items"] --> High["High-weight tier (64.6%)"]
Exam --> Mid["Mid-weight tier (29.7%)"]
Exam --> Low["Low-weight tier (5.7%)"]
High --> AppInt["Applications and Integration (33.1%)"]
High --> ModelSel["Model Selection and Optimization (16.8%)"]
High --> Agents["Agents and Workflows (14.7%)"]
Mid --> Prompt["Prompt and Context Engineering (11.0%)"]
Mid --> Tools["Tools and MCPs (10.6%)"]
Mid --> Security["Security and Safety (8.1%)"]
Low --> Code["Claude Code (3.1%)"]
Low --> Eval["Eval, Testing, and Debugging (2.6%)"]
Here is where the blueprint becomes a study tool. The naive approach gives every domain equal time; the blueprint tells us that is a mistake. Suppose you have 40 hours to study allocated purely by weight:
| Domain | Weight | Proportional Hours (of 40) |
| Applications and Integration | 33.1% | ~13.2 |
| Model Selection and Optimization | 16.8% | ~6.7 |
| Agents and Workflows | 14.7% | ~5.9 |
| Prompt and Context Engineering | 11.0% | ~4.4 |
| Tools and MCPs | 10.6% | ~4.2 |
| Security and Safety | 8.1% | ~3.2 |
| Claude Code | 3.1% | ~1.2 |
| Eval, Testing, and Debugging | 2.6% | ~1.0 |
Nearly 26 of your 40 hours should go to just the top three domains. That does not mean ignore the small domains — a couple of easy points still count toward 720 — but mastering the Claude API, model selection, and agent construction is where the exam is won or lost. Then adjust up or down based on an honest self-assessment against the MQC profile: the blueprint gives the ideal allocation; your self-assessment personalizes it.
Visual animation — coming soon
Which single domain accounts for roughly one-third of the exam — more than the bottom five domains combined?
Agents and Workflows
Applications and Integration
Model Selection and Optimization
Tools and MCPs
What is the recommended way to allocate study time using the blueprint?
Give every domain exactly equal time to be safe
Weight time roughly in proportion to domain weights, then personalize against your own gaps
Study only the two smallest domains since they are easiest
Ignore the blueprint and study in textbook order
An engineer already builds production REST integrations daily. How should they refine the pure weight-based plan?
Trim Applications and Integration hours and redirect them to a weaker area like MCP server authoring
Double the Applications and Integration hours since it is the largest domain
Drop all study of the small domains entirely
Study every domain for identical hours regardless of strengths
Together, which three top-weighted domains make up nearly two-thirds (~64.6%) of the exam?
Claude Code; Eval, Testing, and Debugging; Security and Safety
Applications and Integration; Model Selection and Optimization; Agents and Workflows
Prompt and Context Engineering; Tools and MCPs; Security and Safety
Agents and Workflows; Claude Code; Tools and MCPs
The chapter compares MCP to USB-C. What does that analogy convey about MCP's role?
It is one universal protocol connecting agents to many external tools, replacing fragmented custom integrations
It is a proprietary adapter unique to each individual service
It is the model tier used for the hardest reasoning tasks
It is the HTTP channel that carries messages to the model
What best describes the Claude Agent SDK's relationship to Claude Code?
It exposes the same tools, agent loop, and context management that power Claude Code, run inside your own process
It is an unrelated product with no shared components
It is only the HTTP Messages API with no agent loop
It replaced Claude Code, which no longer exists
In a production multi-tier routing design, which model tier typically classifies incoming requests and handles the simple ones directly?
Opus
Sonnet
Haiku
The official SDK
Why does the chapter argue that model selection is worth 16.8% of the exam?
Because there is a large price and capability gap between tiers, so wrong choices waste money or quality
Because all three tiers cost exactly the same, so choice is trivial
Because only one model tier actually exists in production
Because model selection is unrelated to cost or latency
What is the role of the official Python/TypeScript SDKs relative to the Claude API?
They replace the API with a different protocol entirely
They wrap the API, handling auth, streaming, token management, and errors so you focus on app logic
They are the open standard for connecting agents to external tools
They select the model tier automatically for every request
The Claude Platform Landscape
Key Points
- The Claude platform is a layered ecosystem: the API is the raw channel; the official SDKs (Python/TypeScript) wrap it to handle auth, streaming, tokens, and errors.
- The Claude Agent SDK exposes the same tools, agent loop, and context management that power Claude Code, run inside your own process (formerly the "Claude Code SDK").
- MCP is the open "USB-C" standard: one universal protocol connecting agents to external tools and data (Slack, GitHub, Postgres, Drive, Puppeteer) instead of custom integrations.
- Three model tiers trade intelligence for speed and cost: Haiku (sprinter/routing), Sonnet (steady builder/bulk work), Opus (careful reviewer/hardest 10–15%).
- Each layer maps directly onto an exam domain — understanding the stack is understanding the exam.
| Component | What It Is | One-Line Purpose |
| Claude API | The HTTP (Messages) API to/from Claude models | The raw channel to the model |
| Official SDKs | Python and TypeScript libraries wrapping the API | Handle auth, streaming, tokens, and errors so you write app logic |
| Claude Code | Anthropic's agentic coding CLI/harness | Lets Claude operate on real codebases; treats MCP as first-class |
| Claude Agent SDK | Library exposing the same tools, agent loop, and context management that power Claude Code | Run the agent loop inside your own process |
| MCP | The Model Context Protocol, an open standard | One universal protocol to connect agents to external tools and data |
The Claude Agent SDK runs the agent loop inside your own process. It was formerly called the "Claude Code SDK" and renamed to reflect a broader vision: the harness that powers Claude Code can power many other agents. MCP connects agents to external tools and data through a single protocol — MCP is to AI tools what USB-C is to devices, one standard plug replacing a drawer full of proprietary adapters.
Figure 1.3: MCP as one universal protocol between an agent and many external systems
graph LR
Agent["Claude agent"] --> MCP["MCP: one universal protocol"]
MCP --> Slack["Slack"]
MCP --> GitHub["GitHub / Git"]
MCP --> Postgres["Postgres database"]
MCP --> Drive["Google Drive"]
MCP --> Puppeteer["Puppeteer"]
The Model Families: Opus, Sonnet, and Haiku
| Model Tier | Strength | Typical Role | Approx. Price (in/out per M tokens) |
| Opus | Highest reasoning; deep multi-step analysis | "Careful reviewer" for the hardest 10–15% of tasks | ~$5 / $25 |
| Sonnet | Balanced performance vs. cost | "Steady builder" for the bulk of medium-complexity work | ~$3 / $15 |
| Haiku | Fastest and most cost-efficient | "Sprinter" for high-volume, low-complexity tasks | ~$1 / $5 |
Note the roughly 5x price gap between Opus and Haiku on output tokens — that gap is precisely why model selection is worth 16.8% of the exam. The most sophisticated production systems use all three tiers together: Haiku routes and handles simple requests, Sonnet does the bulk medium-complexity work, and Opus handles the 10–15% requiring deep reasoning.
Figure 1.2: Multi-tier model routing in a production application
flowchart TD
Request["Incoming request"] --> Haiku["Haiku: classify and route"]
Haiku --> Simple{"Complexity?"}
Simple -->|"Simple: handle directly"| HaikuOut["Haiku response"]
Simple -->|"Medium: bulk work"| Sonnet["Sonnet: code, docs, extraction"]
Simple -->|"Hard: deep reasoning (10-15%)"| Opus["Opus: multi-step analysis"]
HaikuOut --> Response["Final response"]
Sonnet --> Response
Opus --> Response
Every layer maps onto an exam domain: the SDK and API to Applications and Integration, the model tiers to Model Selection, the Agent SDK to Agents and Workflows, MCP to Tools and MCPs, and Claude Code to its own domain. Understanding the stack is not separate from passing the exam; it is the exam.
Visual animation — coming soon
The chapter compares MCP to USB-C. What does that analogy convey about MCP's role?
It is one universal protocol connecting agents to many external tools, replacing fragmented custom integrations
It is a proprietary adapter unique to each individual service
It is the model tier used for the hardest reasoning tasks
It is the HTTP channel that carries messages to the model
What best describes the Claude Agent SDK's relationship to Claude Code?
It exposes the same tools, agent loop, and context management that power Claude Code, run inside your own process
It is an unrelated product with no shared components
It is only the HTTP Messages API with no agent loop
It replaced Claude Code, which no longer exists
In a production multi-tier routing design, which model tier typically classifies incoming requests and handles the simple ones directly?
Opus
Sonnet
Haiku
The official SDK
Why does the chapter argue that model selection is worth 16.8% of the exam?
Because there is a large price and capability gap between tiers, so wrong choices waste money or quality
Because all three tiers cost exactly the same, so choice is trivial
Because only one model tier actually exists in production
Because model selection is unrelated to cost or latency
What is the role of the official Python/TypeScript SDKs relative to the Claude API?
They replace the API with a different protocol entirely
They wrap the API, handling auth, streaming, token management, and errors so you focus on app logic
They are the open standard for connecting agents to external tools
They select the model tier automatically for every request