What the exam covers
CCAR-F reports on a scaled range of 100–1000 with a cut at
720, and its questions are distributed across
5 domains by published weight rather than evenly. Those
weights are the single most useful thing in the exam guide: they tell you
where the marks are, and they rarely match where candidates spend their time.
| Domain | Share of exam | Approx. questions |
| Domain 1 — Agentic Architecture & Orchestration |
27.0% |
16 |
| Domain 2 — Claude Code Configuration & Workflows |
20.0% |
12 |
| Domain 3 — Prompt Engineering & Structured Output |
20.0% |
12 |
| Domain 4 — Tool Design & MCP Integration |
18.0% |
11 |
| Domain 5 — Context Management & Reliability |
15.0% |
9 |
See all 52 objectives and their individual weights →
Agentic Architecture & Orchestration is the heaviest at
27.0% — roughly
16 of the
60 questions. Weakness there costs more than weakness
anywhere else, which is exactly what a flat percentage score hides and what
a blueprint-weighted estimate surfaces.
Where to start
Three objectives carry the most weight on CCAR-F. Between them they
are worth roughly
6 of the 60 questions:
-
Apply systematic codebase exploration strategies —
3.0%, about
2 questions
-
Apply context management strategies — subagent isolation, scratchpads, targeted reads —
3.0%, about
2 questions
-
Apply context window optimization — summarization, sliding windows, selective retention —
3.0%, about
2 questions
Which is not the same list as the objectives that feel hardest, and that
gap is where study time usually goes missing. A week spent on the topic
that worries you most is a week spent on
3% of the exam at best,
and often on far less.
How we practice it
Our CCAR-F bank holds 946 original items across
52 objectives, each with an explanation and a note on
every option — why the right answer is right, and why each distractor
fails. Items are written against the published objectives. None is recalled
or reproduced from a live exam.
A drill allocates questions by
the published domain weights,
multiplied by how far your measured mastery sits below standard.
So a domain
worth 27% of the
exam that you are weak in dominates your next sitting, while one you have
already mastered drops back to an exposure floor that keeps its estimate
current.
What a question looks like
Taken from the free CCAR-F set, not written for this page —
the correct answer, why it is correct, and a note on why each other option
fails. Scenarios, not recall: nothing here is answerable from a definition.
CCAR-F
Evaluate subagent delegation strategies — goal-oriented vs procedural
A team moves to goal-oriented delegation and finds that subagents reach conclusions the coordinator cannot audit. What restores visibility without giving up adaptability?
-
A
Have the coordinator re-run each subagent's investigation for itself
Re-running each investigation in the coordinator discards the delegation entirely.
-
B
Return to procedural instructions, so that the path is known in advance
Reverting to procedure gives up the adaptability the team moved to goal-oriented delegation to gain.
-
C
Require each conclusion to come back with its evidence and its method
Correct. Goal-oriented delegation controls the destination rather than the route, so control is reasserted through the output contract.
-
D
Reduce each subagent's tool access, so that fewer paths are possible
Narrowing tools limits where the subagent can look without making its reasoning visible.
Goal-oriented delegation controls the destination, not the route — so control is reasserted through the output contract. Requiring evidence and method with every conclusion keeps the coordinator able to audit the reasoning while the subagent stays free to adapt its path.
See all 20 free CCAR-F questions →
What you get for free
A 20-item diagnostic for CCAR-F, spread across
objectives rather than taken off the top, so the sample reflects the shape
of the exam. It produces a first readiness estimate and full explanations,
whether or not you go on to buy.
The other Claude certification exams
All four report on the same 100–1000 scale with the same
720 cut, so a readiness estimate means the same thing
whichever you are sitting. What differs is shape: