One domain is worth a third of the CCDV-F exam: Applications and Integration, 33% of your 53 questions, all of it living in the mechanics of calling Claude in production. The questions are not trivia; they hand you request payloads, error responses, and cost dashboards, and ask what a developer who has shipped this stack does next. This guide covers the territory in the exam's own proportions: the Messages API contract, streaming and vision, the prompt caching rules that generate the most wrong answers, Batch API economics, and the cloud access paths with their differing model identifiers. Every mechanism comes with the trap the exam builds from it.
Start Here
This is the deep dive on the heaviest domain. For the whole exam, start at the complete guide; to see this domain asked properly, the six practice tests weight it at the real 33%, and the free sample questions previews the style.
CCDV-F exam update on December 7, 2026
From December 7, 2026, CCDV-F has 70 questions (60 scored, 10 unscored) in 120 minutes and new domain weights led by Applications and Integration at 20% instead of 33.1%, with Eval, Testing, and Debugging up to 10%, following the updated exam guide Anthropic published on November 17. If you test on December 7 or later, prepare from the updated guide; what changes on the CCDV-F exam lists every change. This article follows the current guide, and we will revise it for the new one. If you are nearly ready now, a date before December 7 lets you sit the version you studied for.
The Messages API contract
Every integration question sits on the same base call: a model identifier, a maximum output length, and a list of messages with roles. The system prompt rides in its own field, multi-turn history is replayed by your code (the API is stateless; memory is your job), and the response arrives with content blocks plus the metadata the exam loves: a stop reason (finished naturally, hit the length cap, or requesting a tool) and token usage on both sides. Two graded reflexes: check the stop reason before trusting an answer that might be truncated, and know that current top-tier models manage their own reasoning depth adaptively with an effort control, while the old thinking-budget and sampling parameters from older tutorials are rejected with validation errors, a modern trap the exam sets deliberately.
Errors get the production treatment: rate limits and overload errors deserve retries with exponential backoff, authentication and validation errors do not (retrying a malformed request forever is a stem's punchline), and streaming exists so long responses render token by token instead of after a silent wait, which is the graded fix for "users think the app is frozen."
Try 15 CCDV-F practice questions free
They come from the CCDV-F practice tests, and each option shows its explanation once you answer.
- 6 timed practice exams
- Every answer explained
- A score for each domain
- $19.99 one-time
Prompt caching: the byte-identical rule
Caching bills repeated prompt-prefix tokens at a steep discount, and everything the exam asks follows from one rule: the cached prefix must be byte-for-byte identical between requests. You mark the end of the stable prefix with a cache breakpoint; the first request writes the cache entry, subsequent requests within its lifetime (about five minutes by default, refreshed on use) read it at the discount, and a minimum prefix length (around a thousand tokens) gates eligibility.
The trap wears one costume in many stems: something dynamic rendered into the "stable" prefix. A timestamp in the system prompt, a request ID, a user name interpolated before the breakpoint, each one changes the bytes, every request misses, and the dashboard says caching is enabled while the bill says it is not. The graded diagnosis reads the prefix for the dynamic line; the graded design puts stable content (instructions, schemas, reference documents) before the breakpoint and everything per-request after it.
Batch API: the overnight answer
The Batch API runs requests asynchronously at half the realtime token price, with results delivered inside a 24-hour window and most jobs finishing far sooner. The exam encodes it as a workload-matching question: two hundred thousand documents to classify overnight is a batch stem, a customer-facing chat is not, and the discriminating constraint is always latency tolerance. Supporting facts worth having cold: batches are fire-and-collect (submit, poll or fetch results), individual requests inside a batch fail individually, and combining batch with caching stacks the savings on shared prefixes.
Which lever for which complaint
| The stem complains about | Graded lever | Why |
|---|---|---|
| Input cost on repeated system prompts | Prompt caching | Stable prefix billed at the cached rate |
| Cost on huge offline workloads | Batch API | Half price when latency does not matter |
| Perceived slowness on long answers | Streaming | First tokens render immediately |
| Cost on simple high-volume tasks | Smaller model tier | Capability matched to task, biggest single saving |
| All of the above at once | Route, then cache, then batch | Levers compose; tier choice comes first |
Vision and multimodal input
Image input arrives as content blocks alongside text (base64 or referenced), and the exam keeps its vision questions practical: images consume input tokens proportional to size, so resolution is a cost decision; and the developer-shaped questions (extract the table from this screenshot, describe this diagram) belong to the same request anatomy as everything else, not a separate API.
Three questions from the CCDV-F practice tests
A travel-booking backend proxies the Messages API behind its own REST layer. During a fare-sale traffic spike, upstream calls begin returning HTTP 429 with a retry-after header while other requests still succeed. What should the backend do with the failed requests?
[object Object]
Correct. Respecting retry-after with exponential backoff is the intended handling, and the official SDKs retry 429 and 5xx responses this way by default.
A. Hammering the endpoint during a rate-limit window amplifies the overload and keeps the account pinned at its limit; the response explicitly says how long to wait.
B. Key rotation is an availability workaround that dodges the organization's provisioned limits rather than respecting them, and it leaves the underlying overrun unaddressed.
C. That describes a 413 request-too-large response. A 429 is about request rate, is temporary, and the identical payload can succeed after the window resets.
A fintech team ships a customer-support chat backend on the Messages API. After they enable adaptive thinking to improve answer quality, the handler that reads response.content[0].text starts throwing intermittent type errors in production, but only on some responses. Logging shows the failing responses are the ones where the model reasoned before answering. What is the cause?
[object Object]
Correct. Thinking blocks appear ahead of text blocks in the response, so position-based access breaks; type-based dispatch over the content list is the reliable pattern.
A. There is no separate answer field. The final text still arrives as a text block inside the same content array; only its position can shift.
B. The SDK helpers assemble thinking and text blocks alike into the final message. The failure is positional indexing in the handler, not the accumulator.
C. Thinking does share the max_tokens budget, but that produces truncation with a max_tokens stop reason, not the observed type error on responses that completed normally.
A push-notification service for a delivery app must label every incoming message as urgent or routine before fan-out. Volume peaks around two million classifications per day, each label is a simple two-way call, and the product team caps added latency at a few hundred milliseconds. Which model tier fits this workload best?
[object Object]
Correct. Haiku is built for exactly this profile: massive volume, trivial per-item difficulty, and tight latency budgets, at the lowest cost per call.
A. Lowering effort reduces reasoning depth but does not change per-token pricing, which stays several times higher than Haiku for a task that gains nothing from the reserve.
B. Capability beyond the task buys nothing here: a two-way label does not need frontier reasoning, and Opus costs and latency are far higher per call.
C. Sonnet is a reasonable general default, but nothing requires it for a trivial label task; the stated latency and volume constraints point a tier lower.
Full CCDV-F set: 6 timed exams, every answer explained, $19.99 one-time.
See the practice testsBedrock, Vertex, and the model-ID trap
Claude is reachable three ways: the first-party API, Amazon Bedrock, and Google Vertex AI. The exam cares that you know why an organization picks a cloud path (existing cloud commitments, procurement, IAM integration, data residency) and one mechanical fact with outsized question yield: model identifiers differ per platform. The same model carries a different ID string on Bedrock and Vertex than on the direct API, credentials flow through the cloud provider's auth rather than an Anthropic key, and a stem about a working integration that 404s after "just changing the endpoint" is testing exactly this.
Build it, then submit it for grading
The structured-output pipeline and prompt-eval tasks exercise the exact request anatomy, caching, and validation mechanics this domain grades, in your own editor with your own key.
- Build a Structured-Output Extraction & Review Pipeline with Claude ~3hintermediateRubric-graded ProOpen project
- Engineer a Claude Decision Prompt and Prove It with Eval ~3hintermediateRubric-graded ProOpen project
Worked scenario: the cache that never hits
A support tool sends a 6,000-token system prompt with a cache breakpoint on every request. Traffic is steady at hundreds of requests per hour, but cache read tokens stay at zero. The prompt template starts with "Current time: {now}" for the model's context.
The diagnosis is one line: the rendered timestamp sits inside the cached prefix, so no two requests share bytes and every request writes instead of reads. The fix ladder the exam rewards: move dynamic values after the breakpoint (or into the user message), keep the instruction block stable, and verify with cache-read metrics rather than the enabled flag. Distractors will offer longer lifetimes, bigger prefixes, and the Batch API, all of which leave the poisoned first line exactly where it was.
Worked scenario: the frozen dashboard
An internal analytics assistant takes 40 seconds to answer long questions, and users file "it hangs" tickets. Responses are correct when they arrive. The team debates a faster model tier versus more tokens.
The stem describes perception, and the graded answer is streaming: render tokens as they generate and the same 40-second answer feels alive at second one. Tier changes trade quality for a latency the users never actually complained about (they complained about silence), and token limits are unrelated. A second-order graded point: pair streaming with a stop-reason check so a truncated long answer is detected rather than shipped.
Key Takeaways
0/6 completedNext steps
A third of the exam deserves a third of your drilling: the practice tests ask this domain at full weight with per-option explanations, and the mistakes article catalogs the traps this guide defuses. Preparing beyond one cert? Preporato Pro covers every exam and task on the site.
Sources:
![Claude API Integration for CCDV-F: Streaming, Caching, Batch [2026]](/blog/ccdv-f-claude-api-integration-guide.webp)