Claude Certification Blog
A two-week CCAR-F study plan for the flattest blueprint in the programme
On the flattest blueprint in the programme, weighting your time to the exam produces a nearly even plan — and moves the risk from studying the wrong thing to leaving something out.
A two-week CCAR-F study plan: a cold timed mock on day one, eleven study days allocated to the published domain weights, and two fresh papers before a decision. The allocation comes out almost even — three days on agentic architecture and two on each of the other four — because CCAR-F is the flattest paper in the programme, and that changes what you have to watch for.
The flattest paper in the programme
Every other post on this site argues the same thing: weight your study time to the blueprint rather than to your interests. Here that argument produces an almost even answer. Agentic architecture is 27% and context management is 15%, so eleven study days split by weight comes out at 3.0, 2.2, 2.2, 2.0 and 1.6 — which rounds to three days and then two, two, two, two.
That is a result, not a failure to prioritise. The comparison worth holding is the developer plan, where one domain takes three of eleven days and two others share a single afternoon. Full weights for all four tracks are in the domain weights post.
The shape of the fortnight
One diagnostic, eleven study days, two mocks, one decision. The diagnostic is first and is not optional: on a flat paper the cold score by domain is the only thing that tells you where your own distribution differs from the exam’s, and it usually does.
Both mocks are fresh and both are late. A paper you have already worked measures how well you remember that paper — which is a different quantity from readiness, and a flattering one.
The day-by-day plan
| Day | Focus | What it covers |
|---|---|---|
| 1 | Cold diagnostic | One timed mock before any study, scored by domain |
| 2 | Agentic architecture: the gate | Whether autonomy is warranted; loops and stopping conditions |
| 3 | Agentic architecture: dividing | Coordinator and subagents; what a brief must carry |
| 4 | Agentic architecture: sessions | Handoff seams, hooks, and resume against fork |
| 5 | Claude Code: configuration | Instruction files, scoping, and what is enforced |
| 6 | Claude Code: workflows | Plan mode, iteration, and unattended runs |
| 7 | Prompt engineering | Criteria over adjectives; what examples actually teach |
| 8 | Structured output and retry | Schemas, batch, and what a second attempt knows |
| 9 | Tool design | Descriptions as the interface; errors a caller can use |
| 10 | Tools: distribution and built-ins | Who holds what, tool choice, and the built-in set |
| 11 | Context and reliability | Silent failures, provenance, and codebase exploration |
| 12 | Mock two, then repair | Fresh paper, then rework only what it exposed |
| 13 | Mock three | Fresh paper again; compare error patterns, not scores |
| 14 | Final read and the gate | Decision rules only, and the go / no-go call |
Three days on agentic architecture is about breadth rather than depth: it holds seven objectives, more than any other domain on the paper, at roughly two items each. Covering all seven beats mastering three, which is the argument in the post on that domain.
On a flat paper, compress rather than cut
If the fortnight shortens, shorten every day rather than deleting a domain. The lightest domain here is still 15% — about nine items — so dropping it costs more than covering everything at two-thirds depth. That is the opposite of the right move on the developer paper.
The risk moves to omission
On an uneven blueprint the failure mode is mis-allocation: spending a week on something worth two items. On a flat one there is no such trap, and the failure mode becomes omission — finishing the fortnight having never opened one of the five.
The two most commonly skipped here are the ones with the least distinctive vocabulary. Tool design looks like a subset of agents until you notice it is 18% on its own and turns on contracts rather than orchestration; and context management looks like a footnote until you notice every failure in it is silent. Between them that is a third of the paper.
What one study day looks like
Ninety minutes in three parts. Twenty reading the objectives for that domain and writing each as a one-line decision rule — a trigger and a response, in your own words. Fifty on practice items from that domain only, closed-book. Twenty on the misses, naming which rule would have caught each.
A miss that maps to no rule you have written is the useful one: it means a rule is missing rather than forgotten. The twelve recurring decision rules are a reasonable starting library, and reading the ask before the options is the habit that makes the practice half go faster.
The gate on day 14
Stated carefully, because the honest version has a hole in it: Anthropic publishes a scaled passing standard of 720 on a 100–1,000 scale and no conversion from raw performance, so no source can tell you what percentage guarantees a pass.
What this plan uses instead is a conservative convention: two fresh timed papers at or above 90% overall, no domain below 80%, and no repeated miss of the same decision rule. On a flat blueprint the second of those three matters most — a single domain at 60% is worth more lost marks here than it would be on an uneven paper. What the scaled score does and does not mean is in the passing score post, and the repair route if the answer is not yet is in the study guide.
Key takeaways
- The flattest paper in the programme. 27% down to 15%, a spread of 1.8 to 1 against the developer exam’s 12.7 to 1.
- Weighting produces a near-even plan. Three days on agents, two on each of the other four — that is the blueprint, not laziness.
- The risk is omission, not mis-allocation. No domain is small enough to skip when the lightest is still nine items.
- Compress, do not cut. If the fortnight shortens, shorten every day rather than deleting a domain.
- Agents get breadth, not depth. Seven objectives at about two items each; cover all seven.
- Watch the per-domain floor. On a flat paper one weak domain costs more than it would on an uneven one.
A flat blueprint hides where you are actually weak
When every domain is worth roughly the same, the published weights stop telling you where to spend time and your own diagnostic has to. One cold timed paper before day two is what turns this plan from an average into yours. Full-length mocks on the published 60-item allocation are free while the platform is in open beta.
Start with a cold diagnosticQuestions
Frequently asked
The follow-up questions people search next.
Can you prepare for CCAR-F in two weeks?
If you already design systems with Claude, two weeks of roughly ninety minutes a day is realistic: eleven study days, a cold diagnostic and two fresh mocks. The blueprint is unusually flat, so the plan is close to even and there is no domain you can safely drop.
Why is this plan almost evenly split?
Because CCAR-F is the flattest paper in the programme. Its heaviest domain is 27% and its lightest is 15%, a ratio of 1.8 to 1, where the developer exam runs 12.7 to 1. Weighting to the blueprint here genuinely does produce a near-even plan.
Which domain gets the most time?
Agentic Architecture and Orchestration, at 27% of the paper — three of the eleven study days. It also carries seven objectives, more than any other domain on that exam, so the time goes on breadth rather than depth.
What if I only have one week?
Keep the diagnostic and both mocks and compress the study days rather than cutting domains. On a flat paper, dropping a domain entirely costs about a sixth of the exam, which is a worse trade than covering everything more thinly.
How is this different from the developer plan?
Almost inverted. The CCDV-F plan concentrates three of eleven days on a single domain worth a third of the paper. Here no domain is worth more than 27%, so the danger is not mis-allocating time but leaving something out.
Keep reading
Related posts
Not affiliated with, or endorsed by, Anthropic or Pearson VUE. Details are summarised from publicly published program information and can change — always confirm against the official exam guide before booking.