CCAR-F Agentic Architecture and Orchestration Practice Question
An agentic architecture uses Claude to resolve customer support tickets by invoking database lookup and refund tools. During execution, the model frequently makes redundant API calls for the same user ID within a single turn. Which orchestration pattern best resolves this issue while maintaining deterministic behavior?
⚠ Common exam trap
Candidates often suggest re-prompting the model to be 'more careful,' which is non-deterministic and unreliable, instead of implementing architectural caching to solve the root cause of redundant calls.
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
✓
Cache read-only tool responses locally for the duration of the conversation turn to short-circuit identical invocations.
Implementing a caching mechanism for read-only tool outputs directly prevents redundant executions within the agent loop. Caching preserves state consistency, reduces latency, and protects downstream services from rate limits. This approach is critical in production agentic architectures where unnecessary tool calls degrade user experience and inflate operational costs.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the model temperature to encourage more diverse reasoning paths and avoid repetitive loops.
Why it's wrong here
Increasing model temperature introduces stochastic behavior, which worsens infinite loops and reduces the reliability of multi-step tool invocation sequences. Deterministic agent workflows require low temperatures to ensure consistent execution paths and precise tool parameter generation.
- ✗
Implement an aggressive timeout policy that terminates the agent session immediately upon detecting duplicate tool calls.
Why it's wrong here
Terminating the session on a duplicate call aborts the ticket mid-resolution, discarding valid work and returning no answer to the customer. Aggressive timeouts suit runaway or hung sessions, not a deterministic deduplication requirement where the same user ID recurs legitimately.
- ✓
Cache read-only tool responses locally for the duration of the conversation turn to short-circuit identical invocations.
Why this is correct
Caching read-only tool outputs within the session context successfully eliminates redundant API calls without altering core model logic. This practice ensures high throughput, minimizes database load, and preserves predictable execution states across multi-turn agent interactions.
- ✗
Remove the tool definition from the system prompt dynamically once the agent attempts a second invocation.
Why it's wrong here
Removing the tool definition mid-turn alters the model's available action space between invocations, making subsequent behaviour non-deterministic and potentially blocking legitimate lookups for other user IDs. Dynamic tool pruning suits progressive capability disclosure, not deduplicating repeated calls within one turn.
Visual reference
About these practice questions
Courseiva writes every CCAR-F question from scratch — 271 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.