CCAR-F Agentic Architecture and Orchestration Practice Question
When designing a multi-agent system, what is the primary benefit of the 'Orchestrator-Worker' pattern compared to a single-agent architecture with 20 tools?
⚠ Common exam trap
Candidates tend to choose monolithic single-agent architectures with dozens of tools, underestimating the context degradation and confusion caused by bloated prompt schemas.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
It reduces the complexity of the orchestrator's context window by offloading details to workers.
As the number of tools increases, the complexity of the prompt and the likelihood of tool selection errors grow. The Orchestrator-Worker pattern simplifies the individual prompts by delegating specific tasks to specialized agents, which improves accuracy and makes the overall system easier to debug and maintain.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
It eliminates the need for a system prompt for the worker agents.
Why it's wrong here
Worker agents still require system prompts to define their specific roles, tool usage constraints, and output formats. In fact, well-defined system prompts for workers are even more important in this pattern to ensure they stay focused on their narrow domain and provide useful feedback to the orchestrator.
- ✓
It reduces the complexity of the orchestrator's context window by offloading details to workers.
Why this is correct
By delegating tasks, the orchestrator only needs to know which worker to call and the final result they provide. This keeps the orchestrator's context window clean of the minute details and intermediate tool outputs used by the workers, reducing noise and the risk of the model getting distracted.
- ✗
It allows the model to bypass the per-token pricing of the Anthropic API.
Why it's wrong here
The Orchestrator-Worker pattern does not change the pricing model of the API; you are still billed for the tokens used by both the orchestrator and all worker agents. While it may optimize token usage by keeping context small, it is not a mechanism for bypassing the standard billing structure.
- ✗
It guarantees that the model will never produce a hallucinated tool name.
Why it's wrong here
While this pattern reduces the probability of hallucinations by narrowing the focus of each agent, it does not provide a functional guarantee. Hallucinations are a property of LLMs, and architects must still implement validation logic in the application to handle cases where the model suggests a non-existent tool.
About these practice questions
This CCAR-F question is part of Courseiva's 271-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Anthropic exam blueprint
This CCAR-F practice question is part of Courseiva's free Anthropic certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CCAR-F exam.