CCAR-F Agentic Architecture and Orchestration Practice Question
An agent must classify incoming support tickets and then route each to one of four specialized sub-agents. The architect notices the router sometimes dispatches the same ticket to two sub-agents. Which design change most directly prevents duplicate dispatch?
⚠ Common exam trap
The trap here is assuming that a low temperature or a firm prompt guarantees a single tool call, when the guarantee must come from the tool schema and orchestrator enforcement.
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
✓
Give the router a single `route_ticket` tool whose input schema requires one category, and have the orchestrator execute only the first matching tool_use.
Exactly-once routing is an orchestration invariant. Encode the intent in a single tool with an enumerated category, and enforce it in the host by executing at most one routing tool_use per turn. This combination gives the model a clear decision surface while making duplicate dispatch structurally impossible, regardless of sampling behavior.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Lower the router's temperature to reduce randomness in classification.
Why it's wrong here
Temperature affects sampling variety, not the structural possibility of emitting multiple tool calls. Even at temperature zero, a model can still produce two tool_use blocks if the schema permits it. Duplicate dispatch is a schema and orchestration problem, not a sampling problem, so lowering temperature does not guarantee a single route.
- ✗
Add a system-prompt sentence telling the router to select exactly one category.
Why it's wrong here
Prompt instructions are advisory. A model under ambiguity can still emit two tool_use blocks, especially when the ticket spans categories. Without schema constraints and orchestrator enforcement, the duplicate dispatch remains possible. Prompt text is useful for shaping behavior but insufficient as the sole guarantee for an exactly-once routing rule.
- ✗
Increase the number of categories so each ticket has an obvious best match.
Why it's wrong here
More categories can increase overlap and ambiguity rather than reduce it, and the number of labels does not constrain how many tool calls the model emits. The duplicate dispatch stems from the absence of a single-call schema and orchestrator enforcement, not from insufficient category granularity.
- ✓
Give the router a single `route_ticket` tool whose input schema requires one category, and have the orchestrator execute only the first matching tool_use.
Why this is correct
Constraining routing to one tool with an enumerated single-value input makes the intended behavior explicit, and orchestrator-side enforcement of a single execution provides a deterministic backstop. Even if the model emits multiple blocks, the host honors only the first, guaranteeing exactly one dispatch per ticket while preserving the model's classification role.
About these practice questions
One of 271 original CCAR-F practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.