Evidence and transparency
A study guide is a stack of claims, and most do not tell you which claims you can bet an exam fee on. This page does. Everything these guides assert is sorted into three classes — confirmed by Anthropic, cross-validated from the sitting behind this guide, or ours alone — so you know what to memorise, what to discount, and how to check us.
This appendix exists because the reverse question is fair. Five domain pages assert numbers, name traps and rank difficulties — and a reader booking a $125 exam deserves to know which assertions come from Anthropic and which come from us. The sorting rule is simple: a claim is confirmed if Anthropic prints it; cross-validated if we observed it in the sitting behind this guide and it is consistent with what Anthropic prints; ours if it is teaching structure or judgment. Nothing here is new material to learn — it is the metadata for the other five pages.
01Three evidence classes
Printed by Anthropic — in the official CCAR-F exam guide (version 1.0, effective July 2026), on the official exam page, or in the Claude documentation. If Anthropic revises the source, we revise the guide; every confirmed claim below names where it is printed.
Not printed by Anthropic, but observed in the sitting behind this guide and consistent with the official material. One sitting is one draw — four of the six scenarios — so treat these as strongly indicative, not guaranteed. Your sitting can differ honestly.
The teaching structure, the study order, the emphasis, the trap collections, the difficulty ranking. Derived from experience, defended in the text, endorsed by nobody. Anthropic has not reviewed this guide, and we are not affiliated with them.
02The official numbers — verified October 2026
We re-pulled the official exam guide on October 5, 2026 and checked every number these guides quote against it. The domain weights first, because the study plan follows from them:
| Domain | Weight | Evidence |
|---|---|---|
| 01 Agentic architecture and orchestration | 27% | Confirmed — blueprint, section 4 |
| 02 Tool design and MCP integration | 18% | Confirmed — blueprint, section 4 |
| 03 Claude Code configuration and workflows | 20% | Confirmed — blueprint, section 4 |
| 04 Prompt engineering and structured output | 20% | Confirmed — blueprint, section 4 |
| 05 Context management and reliability | 15% | Confirmed — blueprint, section 4 |
The logistics, same check:
| Fact | Value | Evidence |
|---|---|---|
| Items | 60 multiple-choice and multiple-response; each item states how many responses to select | Confirmed — section 3 |
| Scenarios | 4 drawn at random from a bank of 6 | Confirmed — sections 3 and 5 |
| Time and fee | 120 minutes, $125 USD | Confirmed — section 3 |
| Pass mark | Scaled 720 on a scale of 100–1,000 | Confirmed — section 3 |
| Score report | Pass/fail plus percent-correct by domain | Confirmed — section 3 |
| Credential | Valid 12 months | Confirmed — section 3 |
| Retakes | 14 days after the first fail, 30 after the second, 90 after the third; four attempts per rolling twelve months, fee each time | Confirmed — section 10 |
| Profile | Six-plus months hands-on recommended — recommended, not required | Confirmed — section 2 |
03The six official scenario contexts
Section 5 of the exam guide names all six scenarios the bank draws from — and, more useful, says which domains each one primarily tests. Your sitting sees four of the six at random, which is why two candidates can walk out with honest but opposite stories about what the exam emphasised. The six, condensed but faithful:
| Scenario | What it frames | Primary domains |
|---|---|---|
| 01 Customer support resolution agent | An Agent SDK agent handling returns, billing disputes and account issues over custom MCP tools (get_customer, lookup_order, process_refund, escalate_to_human); 80%+ first-contact resolution target | D1, D2, D5 |
| 02 Code generation with Claude Code | Team development workflows: custom slash commands, CLAUDE.md configuration, plan mode versus direct execution | D3, D5 |
| 03 Multi-agent research system | A coordinator delegating to specialised subagents — one searches the web, one analyses documents, one synthesises, one writes the report | D1, D2, D5 |
| 04 Developer productivity tools | Exploring unfamiliar codebases and legacy systems over the built-in tools (Read, Write, Bash, Grep, Glob) and MCP servers | D1, D2, D3 |
| 05 Claude Code for continuous integration | Automated code review, test generation and pull-request feedback; prompts that stay actionable and minimise false positives | D3, D4 |
| 06 Structured data extraction | Unstructured documents in, JSON-schema-validated structured data out; edge cases handled, downstream systems fed | D4, D5 |
Now read the last column as a study map — this part is our inference, not Anthropic’s. Context management (D5, the lightest domain at 15%) is a primary domain in four of the six scenarios, more than any other domain — the random draw makes it unavoidable; nobody skips it by luck. The heaviest domain (D1, 27%) anchors three scenarios. Prompt engineering (D4) is primary in only two, but pairs with Claude Code configuration in the CI scenario, which is exactly where schema-enforced output meets automation. Study the domains by weight, then rehearse them through these six lenses: for each scenario you should be able to say what a good design looks like and the two ways it usually goes wrong.
04How wrong answers are written
The exam guide ships sample questions with full explanations, and the explanations do something most prep material does not: they classify every wrong option by its failure mode instead of just labelling it incorrect. Three families cover most of what those explanations show — and the same families recur in the traps sections of our five domain pages. The classification itself is cross-validated: consistent between the official explanations and the sitting behind this guide.
| Failure mode | What the wrong option does | Where you will meet it |
|---|---|---|
| Probabilistic where deterministic is required | Proposes a prompt instruction or few-shot examples to enforce a business rule that needs a programmatic gate. The official explanation for the refund-skipping sample question names this failure exactly. | D1 enforcement, D2 tool ordering, D5 escalation |
| Solves a different problem | Addresses availability, cost or routing when the stem asks about ordering, provenance or latency. Right tool, wrong axis — the favourite shape of an option that sounds sensible. | Every domain |
| Over-engineered | Adds a classifier, a labelled dataset or a routing layer where rewriting a tool description would do. | D2 tool design, D4 prompt engineering |
Practical use: when you eliminate options, name the failure mode out loud — “that is probabilistic enforcement”, “that solves availability, not ordering”, “that is over-engineering for a description fix”. An option you can classify is an option you can discard in seconds. The traps sections of the domain pages drill exactly this, one domain at a time; treat this table as the index.
05What is ours alone
- —The difficulty ranking — that CCAR-F is the hardest of the three certifications, ambiguity included — is one candidate’s experience across all three sittings. Anthropic makes no such claim.
- —The count “roughly 25 of the 60 questions are technical in wording” was tallied in a single sitting. One draw, one candidate: honest, but approximate by construction.
- —The study order (weight order, Domain 01 first) and the claim that hours should follow marks available — our judgment, argued on the Start here page.
- —Every trap in the domain pages: collected from the sitting and the official explanations, curated by us. Representative, not exhaustive — no independent guide’s trap list is exhaustive either, whatever the page count.
- —The glossary phrasing, the trees and flows, the quiz questions: written for this guide, not sourced from Anthropic.
06Verify us
Every confirmed claim on this page is checkable in minutes, and the checking is free. If you find a number here that contradicts the official guide, trust the guide — then tell us, because the error is ours.
Where to check
- The official CCAR-F exam page — registration, and the exam guide PDF that is the source of truth for weights, scenarios and policies ↗
- Claude documentation — where every technical fact in the five domain pages is anchored ↗
- The exam write-up behind this guide — the sitting, the resources, the exam-day tactics
- The guide hub — including the independent cross-checks (CertSafari, dnacenta) we check our coverage against