Claude Certification Blog
Agentic architecture on CCAR-F: seven objectives, sixteen items, one flat block
The largest domain on the Claude architect foundations exam packs seven objectives into sixteen items — which makes it the one place on the paper where studying evenly is the right call.
Agentic architecture is 27% of CCAR-F — about 16 of 60 items — and it carries seven objectives, more than any other domain on that paper. That arithmetic is the most useful thing about it: seven objectives across sixteen items is a little over two items each, so the domain rewards covering all seven rather than mastering the three with the most interesting vocabulary.
Seven objectives, sixteen items
Most study advice for this exam collapses the domain into “agents” and then into multi-agent design specifically — and the developer exam folds several of these objectives into one skill, which is why borrowed material mis-weights this block in both directions. But orchestration accounts for two of the seven objectives — roughly four items. The other five cover loops, handoff, hooks, decomposition and sessions, and each is worth about as much as the multi-agent material that gets all the attention. The full domain weights put this domain in context against the rest of the paper.
What each objective covers
| Objective | Published name | The question it asks |
|---|---|---|
| O01 | Agentic loops for autonomous execution | Whether autonomy is warranted at all |
| O02 | Coordinator-subagent orchestration | Who dispatches, and who never talks to whom |
| O03 | Subagent invocation and context passing | What the brief contains, because nothing is inherited |
| O04 | Multi-step enforcement and handoff | What survives the seam between two steps |
| O05 | Agent SDK hooks | Interception, and normalising what a tool returns |
| O06 | Task decomposition strategies | Where the workflow divides, and why there |
| O07 | Session state, resumption and forking | Which of three ways to continue is right |
Five of the seven have a post of their own on this site, because they are the ones candidates search for by name: whether to build an agent at all, coordinator and subagent patterns, what hooks are and which layer owns them, decomposition across tracks, and the resumption half of context management. The two that do not are the subject of the next two sections.
The objective people skip
O04 — multi-step workflows with enforcement and handoff patterns — is the least searched-for objective in the domain and worth about two items like all the others. It has no distinctive vocabulary, it sits between the loop objectives and the orchestration ones, and it is easy to read as a summary of both rather than as its own subject.
Its actual subject is the seam. When one step ends and another begins, something has to carry across: what was produced, what was assumed, what remains outstanding. A handoff that passes only the output loses the assumptions, and the next step proceeds on its own guesses about them without anything indicating a substitution happened.
Ask what the next step would have to guess
For any proposed handoff: what does the receiving step need that it is not being given? Anything on that list becomes an assumption, and an assumption made quietly is indistinguishable from a fact until something built on it turns out wrong.
Enforcement is not instruction
The other half of O04 is enforcement, and it carries the distinction that runs through the entire exam. A step that must not proceed under certain conditions needs something that prevents it, not something that discourages it. Where the scenario uses absolute language, an option that states the constraint as guidance has answered a different question.
This is the same judgment examined as hooks in O05, as permission configuration on the Claude Code domain, and as guardrail placement on the architect professional exam. It arrives here as a workflow property: the rule is not a thing the workflow tries to observe, it is a thing the workflow cannot violate. The security-facing version is in prompt injection and guardrails.
Resume, fork, or start again
O07 is decided by circumstances rather than by preference. Resuming restores accumulated working state, which is exactly what you want when that state is still true and exactly what you do not want when the situation has changed underneath it. Forking is for two directions that share a starting point and diverge afterwards — running the same session twice interleaves both explorations into one history instead.
Starting fresh with a written summary is the option candidates undervalue, and it is the right answer whenever the old session’s conclusions may no longer hold. Carrying forward a short statement of what is established costs one paragraph; carrying forward a stale conclusion costs whatever gets built on it.
How to spend the block
If this domain gets a quarter of your study time, matching its weight, split that time roughly evenly across the seven objectives rather than by interest. That advice is unusual on these exams, where uneven weighting is the norm and one domain can be a third of a paper. It follows here from the arithmetic: seven objectives, sixteen items, no objective large enough to carry the domain on its own.
Then check the two nobody drills. If you can state in one line what has to cross a handoff, and which of resume, fork or fresh-start a described situation calls for, you have covered about four items that most candidates meet cold.
Key takeaways
- Twenty-seven percent, sixteen items, seven objectives. The largest domain on CCAR-F and the one with the most ground.
- Multi-agent design is two of seven. Roughly four items, not the whole domain, which is how it usually gets studied.
- Study this domain evenly. No objective is big enough to carry it, so breadth beats depth here specifically.
- Handoff is about the seam. Whatever the next step is not given becomes an assumption, silently.
- Enforcement is structural. Where the scenario says the rule must always hold, guidance is the wrong mechanism.
- Resume, fork, or start fresh. Circumstances decide it, and resuming restores stale conclusions along with good state.
Sixteen items is more than a quarter of the paper
A domain this broad is where an interest-led study plan quietly fails: five objectives feel covered, two were never opened, and both appear. Timed papers built to the published 60-item allocation put all seven in front of you. Our claude certification study guide covers how to sequence them.
See the CCAR-F blueprintQuestions
Frequently asked
The follow-up questions people search next.
What is the biggest domain on CCAR-F?
Agentic Architecture and Orchestration, at 27% of the exam — roughly 16 of 60 items. It also carries seven objectives, more than any other domain on that paper, which works out at a little over two items each.
What does the handoff objective cover?
Implementing multi-step workflows with enforcement and handoff patterns — what has to be true at the seam between two steps for the second one to proceed correctly, and what stops it proceeding when that is not true. It is the objective with the least distinctive vocabulary and the one most often skipped.
Should I resume a session or start a new one?
Resuming brings back accumulated state, which is an advantage when the state is still true and a liability when it is not. Forking is for exploring two directions from a shared starting point. Starting fresh with a written summary is right when the situation has changed underneath the old session.
How much of CCAR-F is about multi-agent systems?
Two of the seven objectives in this domain — coordinator-subagent orchestration and subagent invocation with context passing — so roughly four items. The domain is much broader than multi-agent design, which tends to absorb most of the attention.
How should I split study time across the seven objectives?
Roughly evenly, because each is worth about two items. That is unusual advice on an exam where uneven weighting is otherwise the rule, and it follows from the arithmetic: a domain with seven objectives and 16 items rewards breadth over depth.
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.