CCAR-F Agentic Architecture and Orchestration Practice Question
An agent that reconciles invoices is failing intermittently. Logs show it sometimes calls `approve_payment` before `verify_vendor`, even though the system prompt lists `verify_vendor` first. The agent has 12 tools available. Which change most directly reduces this ordering violation?
⚠ Common exam trap
The trap here is believing that listing tools in a particular order in the system prompt reliably enforces execution order, when ordering must be enforced programmatically.
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
✓
Add a programmatic gate that rejects `approve_payment` calls until a successful `verify_vendor` result exists in the conversation state.
Prompt ordering is a soft hint; models can still invert steps under varying context. The reliable fix is a deterministic guard in the orchestrator that inspects conversation state and blocks `approve_payment` until a valid `verify_vendor` result is present. This preserves the tools' distinct roles while guaranteeing the compliance rule.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Reduce the tool count by removing unrelated tools so the model has fewer choices.
Why it's wrong here
Fewer tools can reduce confusion, but it does not enforce the `verify_vendor`-before-`approve_payment` dependency. The model could still select the payment tool first. Tool pruning addresses selection breadth, while this failure is about sequence integrity, so it is a weak and indirect mitigation.
- ✗
Merge `verify_vendor` and `approve_payment` into one tool with a single parameter object.
Why it's wrong here
Combining the tools removes the model's ability to interleave verification with other steps and hides the sequencing problem rather than solving it. It also makes partial failures ambiguous, because the combined tool would need internal branching. The scenario needs ordering enforcement, not tool consolidation.
- ✓
Add a programmatic gate that rejects `approve_payment` calls until a successful `verify_vendor` result exists in the conversation state.
Why this is correct
Enforcing the dependency in the orchestration layer guarantees the invariant regardless of model behavior. Even a well-prompted model can occasionally invert steps, so a deterministic check on conversation state ensures `approve_payment` is only executed after `verify_vendor` succeeds. This is a control, not a suggestion, and it scales as tools grow.
- ✗
Raise the model temperature to encourage more exploratory tool selection.
Why it's wrong here
Higher temperature increases randomness in token selection, making tool choice less predictable, not more. For a compliance-sensitive workflow that must follow a fixed sequence, added randomness would worsen ordering violations. Temperature tuning is not a mechanism for enforcing procedural order between tools.
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.