Home / Claude Certified Architect – Foundations / Objective 1.2

Domain 1: Agentic Architecture & Orchestration · 27% of the exam · Full exam outline

1.2 Orchestrate multi-agent systems with coordinator-subagent patterns

What this objective covers

Hub-and-spoke architecture where a coordinator agent manages all inter-subagent communication, error handling, and information routing. How subagents operate with isolated context—they do not inherit the coordinator's conversation history automatically. The role of the coordinator in task decomposition, delegation, result aggregation, and deciding which subagents to invoke based on query complexity. Risks of overly narrow task decomposition by the coordinator, leading to incomplete coverage of broad research topics. Designing coordinator agents that analyze query requirements and dynamically select which subagents to invoke rather than always routing through the full pipeline. Partitioning research scope across subagents to minimize duplication (e.g., assigning distinct subtopics or source types to each agent). Implementing iterative refinement loops where the coordinator evaluates synthesis output for gaps, re-delegates to search and analysis subagents with targeted queries, and re-invokes synthesis until coverage is sufficient. Routing all subagent communication through the coordinator for observability, consistent error handling, and controlled information flow.

Practice questions

Question 1easy

An architect is deciding where a lead agent with parallel subagents is worth its extra token cost. Which workload fits that architecture best?

Included in Sample: sample every domain.See plans

Choose an answer to check it. Afterward, select any option to review its explanation.

Multi-agent runs use far more tokens than chat, so they only make sense when the task's value covers that cost.

Multi-agent systems pay off on valuable, heavily parallel work whose information exceeds a single context window: subagents explore separate directions at once, each in its own context.

Parallel subagents are overkill for a simple lookup. One agent with a few tool calls covers it.

Code changes look like divisible work, which makes this tempting. But tightly coupled steps need shared context, and agents are not yet good at coordinating in real time, so this is named as a poor fit.

Question 2easy

In Anthropic's Research system, how do the lead agent and its subagents divide the work on a user query?

Included in Master: master every domain.See plans