Introduction: The Claude Platform and the CCDV-F Exam

Learning Objectives

Pre-Quiz: The Certification and Its Value

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 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 AreaTarget Level
General software engineering1–5 years
Hands-on Claude (or comparable LLM) experienceAt least 6 months
Programming languagesProficiency in Python and/or TypeScript
InterfacesFluency with REST APIs and CLI tools
Conceptual groundingLLM 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

Post-Quiz: The Certification and Its Value

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
Pre-Quiz: Exam Format and Scoring

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

AttributeDetail
Exam codeCCDV-F
Number of items53
Item formatMultiple-choice and multiple-response; each item states how many responses to select
Time limit120 minutes
DeliveryProctored: online-proctored and/or test center (Pearson VUE)
Passing scoreScaled score of 720 on a scale of 100–1,000
Exam fee$125 USD
Validity period12 months from award date
Result reportingPass/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.

DimensionCriterion-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 qualifiedNo, a fixed share is capped out
"Graded on a curve"?NoYes
What passing meansYou met a defined bar of competenceYou 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

Post-Quiz: Exam Format and Scoring

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
Pre-Quiz: The Eight-Domain Blueprint

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

#Content DomainWeightApprox. Items (of 53)
1Agents and Workflows14.7%~8
2Applications and Integration33.1%~18
3Claude Code3.1%~2
4Eval, Testing, and Debugging2.6%~1
5Model Selection and Optimization16.8%~9
6Prompt and Context Engineering11.0%~6
7Security and Safety8.1%~4
8Tools and MCPs10.6%~6
Total100%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:

DomainWeightProportional Hours (of 40)
Applications and Integration33.1%~13.2
Model Selection and Optimization16.8%~6.7
Agents and Workflows14.7%~5.9
Prompt and Context Engineering11.0%~4.4
Tools and MCPs10.6%~4.2
Security and Safety8.1%~3.2
Claude Code3.1%~1.2
Eval, Testing, and Debugging2.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

Post-Quiz: The Eight-Domain Blueprint

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
Pre-Quiz: The Claude Platform Landscape

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

ComponentWhat It IsOne-Line Purpose
Claude APIThe HTTP (Messages) API to/from Claude modelsThe raw channel to the model
Official SDKsPython and TypeScript libraries wrapping the APIHandle auth, streaming, tokens, and errors so you write app logic
Claude CodeAnthropic's agentic coding CLI/harnessLets Claude operate on real codebases; treats MCP as first-class
Claude Agent SDKLibrary exposing the same tools, agent loop, and context management that power Claude CodeRun the agent loop inside your own process
MCPThe Model Context Protocol, an open standardOne 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 TierStrengthTypical RoleApprox. Price (in/out per M tokens)
OpusHighest reasoning; deep multi-step analysis"Careful reviewer" for the hardest 10–15% of tasks~$5 / $25
SonnetBalanced performance vs. cost"Steady builder" for the bulk of medium-complexity work~$3 / $15
HaikuFastest 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

Post-Quiz: The Claude Platform Landscape

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

Your Progress

Answer Explanations