CCA Study Tips for Domain 1: Agentic Architecture & Orchestration

The fastest way to study Domain 1 (Agentic Architecture & Orchestration, 27% of the CCA-F) is to read the 30 study articles in task order, memorise a short list of mechanisms and their return values, and then drill scenario questions until you can name the mechanism before you read the options. This post gives you that reading order, the memorise-versus-reason split, a practice cadence, and self-check questions.

For what the domain covers and why it is weighted at 27%, see the companion post CCA Domain 1 Explained. This post is only about how to study it.

What order should I read the Domain 1 articles in?

Follow the task numbering on the Domain 1 study guide page. It is already ordered from single-agent basics to multi-agent operations, and each task builds on the previous one. Suggested grouping into sessions:

Session	Articles	Goal
1	Task 1.1: stop_reason Is the Only Loop Control That Matters, The API Is Stateless, Model-Driven Decisions vs Hardcoded Decision Trees, Three Anti-Patterns That Break Agentic Loops	Be able to draw the loop and its six stop values
2	Task 1.2: hub-and-spoke, Sub-Agents See Nothing, decomposition scope, dynamic selection, refinement loop	Explain why a coordinator must pass context explicitly
3	Task 1.3: Task Tool, allowedTools, and the Full AgentDefinition Configuration Surface through Goals + Standards Beat Step-by-Step	Know every AgentDefinition field, resume vs fork, parallel spawning
4	Tasks 1.4 and 1.5: The Model Will Override Your Instructions 4-15% of the Time, the hook articles	Decide prompt vs hook by consequence; know PreToolUse return shapes
5	Tasks 1.6 and 1.7: Dynamic Adds 30% Overhead on Fixed Tasks, multi-pass review, Resume Saves 44% Time and 58% Tokens in CI Pipelines, resume vs fresh	Match strategy to task shape; know when resume is unsafe

Read the Foundations agentic primer (The Agentic Loop: Reason → Act → Observe → Repeat and Five Orchestration Patterns) before session 1 if you have not built an agent before.

What should I memorise, and what should I reason about?

Domain 1 has a small set of facts you simply need to know, and a much larger set of judgements you should practise rather than memorise.

Memorise (flashcard material):

• The six stop_reason values and the action for each (tool_use continue, end_turn stop, max_tokens warn, pause_turn resume, refusal alert, stop_sequence stop).
• PreToolUse return shapes: permissionDecision: "deny" with a reason; "allow" with updatedInput; empty return means allow. updatedInput without an explicit allow is ignored. Source: PreToolUse Returns: deny, allow, modify.
• The five hook types and their lifecycle position (Five Hook Types Across the Full Session Lifecycle).
• AgentDefinition fields: description, prompt, tools, model, and what each controls.
• Task tool inputs and response fields, and the common bug (Task Tool: Three Inputs, Four Response Fields, One Common Bug).
• MCP tool names carry the mcp__server__tool prefix, so a matcher on the bare name misses them.

Reason about (scenario judgement):

• Single agent or orchestration? Only orchestrate when work is parallel, needs isolation, or exceeds one agent’s reliable tool count.
• Prompt or hook? Ask what a miss costs. Financial, legal, security, data integrity means hook; style means prompt. Select by Consequence AND Verifiability is the decision article.
• Chain or dynamic? Fixed steps chain; discovery-driven work adapts; mixed tasks chain with extension points.
• Resume or fresh? Resume when context is stable and expensive to rebuild; fresh when the underlying data may have changed (The Agent Can’t Detect Stale Data).
• Structured or plain-text handoff? Structured, when attribution or fields matter downstream (Structured Data Preserves Attribution, Missing Customer Expectation Drops Satisfaction 23 Points).

Do not memorise the percentages in article titles. They are there to make the point vivid; the exam tests the direction of the effect, not the number.

What practice cadence works for Domain 1?

• After each session, run 15 to 20 Domain 1 practice questions. Before revealing the answer, write down the mechanism you expect (hook, stop_reason, context passing, parallel spawn, resume). If the correct answer uses a different mechanism, that is the note to keep.
• After session 5, do a 40-question Domain 1 block in one sitting to check stamina on scenario reading.
• Every three or four days, review the mistakes tracker. Domain 1 mistakes cluster into three buckets: loop control, missing context, and prompt-vs-hook. If one bucket dominates, reread that task’s articles rather than doing more random questions.
• In the final week, sit the free CCA-F mock exam. It samples by official weight, so you will see roughly 16 Domain 1 questions among 60 (confirm current weights on the official Anthropic / Pearson VUE page before you register).

If you can spare an hour, write a 50-line loop that calls the Messages API, reads stop_reason, appends tool_result blocks, and has one PreToolUse-style guard. Seeing the text-and-tool_use blocks arrive in the same response fixes the most common misconception faster than any reading.

Self-check questions before moving on

Answer these without looking. If any takes more than a sentence, go back to the linked article.

1. A response has both a text block and a tool_use block. Is the turn finished?
2. The coordinator has the customer’s tier in its context. Does the billing sub-agent know it?
3. A hook prints “Blocked” and returns {}. What happens to the tool call?
4. When should you prefer fork over resume for a follow-up evaluation? (Fork Eliminates Anchoring Bias)
5. Three sub-agents have no dependencies on each other. What is the zero-cost speedup? (Parallel Execution: 80% Wall-Clock Reduction, Zero Extra Cost)
6. A four-step code review always runs the same steps. Chain or dynamic?
7. A prompt says “always confirm before rm”. The agent ran rm -rf on “clean up”. What is the fix, and why does stronger wording not work?
8. An open-ended refactor request produces trivial edits. What was skipped? (Without Exploration First, 80% of Effort Goes to Trivial Code)

Mistakes worth reviewing twice

Certain wrong answers recur in practice sets, and reviewing them is worth more than new questions:

• Picking the multi-agent option because it sounds more architectural. Reread Don’t Run Every Agent for Every Query.
• Choosing an iteration cap as the primary loop control.
• Assuming a hook can invoke a tool on the model’s behalf.
• Decomposing too narrowly and losing cross-file findings (Narrow Decomposition Means Missing Coverage).
• Writing step-by-step coordinator prompts when goals and standards score better.
• Missing that a request with four or more concerns needs explicit decomposition (4+ Concerns? Only 38% Get Fully Addressed).

Next step

Start with session 1 on the Domain 1 study guide page today and finish the Domain 1 practice set by the end of the week. When your accuracy holds across two sittings, take the free CCA-F mock exam to see how Domain 1 mixes with the other four, and use the 30-day study schedule to slot the remaining domains around it.