Claude Certified Architect – Foundations Practice Question 13: Multi Agent Tradeoffs

Claude Certified Architect, Foundations · Test 2 · question 3 of 10

Agent Architecture & Orchestrationhard

A team proposes replacing its working single-agent coding assistant with a multi-agent system: a planner, a coder, a tester and a reviewer, each with its own context. The assistant makes coordinated edits across tightly coupled modules where each change depends on decisions made in the others. The budget is fixed and the task value per request is modest. Anthropic's published experience with multi-agent systems says this decision should rest on which assessment?

Select one answer
Show answer and explanation

Answer:

  • B. Multi-agent systems use many times more tokens than a single agent and suit parallelizable, high-value work; tightly coupled coding tasks are a poor fit, so keep the single agent

B is correct. Anthropic reports that agents use about 4x more tokens than chat and multi-agent systems about 15x more, so the task value must justify that cost. Domains where all agents must share the same context, or where there are many dependencies between agents, are a poor fit, and most coding tasks have fewer truly parallelizable pieces than research. Multi-agent shines on breadth-first, parallelizable work whose information exceeds a single context window.

A is wrong because more agents is not automatically better; coordination and cost are real trade-offs and the lack of shared context hurts coupled edits. C is wrong because total tokens rise, since each agent repeats context and agents exchange messages. D is wrong because no guidance mandates the smallest model for every role, and weak models in a dependent chain make coordination worse.

Reference: How we built our multi-agent research system

Practice Test 2 ›

Study guides for Claude Certified Architect, Foundations