Claude Certified Developer - Foundations (CCDV-F) Flashcards¶
35 cards from this guide's fact sheet and notes. Click a question to reveal the answer.
To study with spaced repetition, download flashcards.csv and import it into Anki or Quizlet (comma separated, first row is the header). Back to the study guide.
Exam logistics¶
How long is the Claude Certified Developer - Foundations (CCDV-F) exam?
120 minutes
How many questions are on the Claude Certified Developer - Foundations (CCDV-F) exam?
53 multiple-choice and multiple-response
What is the passing score for Claude Certified Developer - Foundations (CCDV-F)?
720 / 1000
What does the Claude Certified Developer - Foundations (CCDV-F) exam cost?
$125 USD
How is the Claude Certified Developer - Foundations (CCDV-F) exam delivered?
Pearson VUE - online proctored or test center
How long is Claude Certified Developer - Foundations (CCDV-F) valid for?
12 months (free non-proctored renewal via Partner Academy)
Claude api fundamentals¶
max_tokens (claude api fundamentals)
the required cap on response length, including thinking and text.
Content block (claude api fundamentals)
a typed piece of a message: text, image, document, tool_use, tool_result or thinking.
stop_reason (claude api fundamentals)
the field that says why generation ended: end_turn, max_tokens, stop_sequence, tool_use, pause_turn, refusal or model_context_window_exceeded.
anthropic-version header (claude api fundamentals)
pins the API contract so old behavior keeps working; new behavior lands behind new versions or opt-in beta headers.
Messages api and streaming¶
Server-Sent Events (messages api and streaming)
the transport streaming uses; each event is a JSON object on a data: line.
message_start (messages api and streaming)
the first streaming event, delivering the initial Message object with empty content.
Stateless conversation (messages api and streaming)
the server keeps no history, so every request must include the full message history you want Claude to see.
stop_sequences (messages api and streaming)
strings that halt generation when Claude emits one; stop_reason becomes stop_sequence.
Tool use function calling¶
tool_use block (tool use function calling)
the content block in an assistant message where Claude asks you to run a tool; it carries an id, a name and an input.
tool_result block (tool use function calling)
your answer to a tool_use, sent in a user message with a matching tool_use_id.
tool_choice (tool use function calling)
sets whether Claude may call tools: auto (Claude decides), any (must call one), tool (must call a named tool) or none.
Forced tool choice (tool use function calling)
tool_choice any or tool, which forces a tool call; on Claude Opus 5.5, Sonnet 5.5, Fable 5.1 and Mythos 5.1 it returns a 400 error, so use auto with strict tool use or structured outputs there.
Prompt caching and batch api¶
Prompt caching (prompt caching and batch api)
stores a prefix of your request server-side and replays it cheaply on later requests with the same prefix.
cache_control (prompt caching and batch api)
the marker placed on a content block that makes it, and everything before it, a cache breakpoint.
Batch API (prompt caching and batch api)
runs jobs asynchronously at a 50% discount, with results within 24 hours.
custom_id (prompt caching and batch api)
your correlation key on each batch request, used to map results back to your records.
Files api citations and pdfs¶
Files API (files api citations and pdfs)
lets you upload content once and reference it by ID across many requests.
Citations (files api citations and pdfs)
attribute spans of Claude's response to specific spans of source documents; enabled with citations: {enabled: true} on document blocks.
document block (files api citations and pdfs)
the content block used to send a PDF, by base64, URL or file_id.
Error handling rate limits retries¶
429 rate_limit_error (error handling rate limits retries)
you hit a requests-per-minute or tokens-per-minute ceiling; retryable with backoff.
retry-after header (error handling rate limits retries)
the official SDK honors it when present on a retried error; a tier spend-cap 429 has no retry-after and keeps failing until access resumes.
Circuit breaker (error handling rate limits retries)
after N consecutive failures, stop sending requests for a cooldown and test occasionally with a single request.
Exponential backoff with jitter (error handling rate limits retries)
the retry pattern for retryable errors, with capped attempts.
Agents and workflows¶
Workflow (agents and workflows)
code-orchestrated: your program decides the steps and their order, and the model fills in the content of each step.
Agent (agents and workflows)
model-driven: Claude decides which tool to call next, observes the result, and keeps going until it judges the task done.
Prompt chaining (agents and workflows)
break a task into sequential API calls, each feeding the next, with optional programmatic gates between steps.
Routing (agents and workflows)
classify the input first, then dispatch to a specialized prompt and often a specialized model.
Orchestrator-workers (agents and workflows)
a central model call decomposes the task dynamically, farms subtasks to worker calls, and synthesizes the results.
Evaluator-optimizer (agents and workflows)
one call generates, a second evaluates against criteria, and the generator retries with the feedback until it passes or a retry cap hits.