CCAR-P Advanced Agentic Architecture Practice Question
Exhibit
{
"error": {
"type": "overloaded_error",
"message": "Overloaded"
}
}Refer to the exhibit. An agentic loop receives this response from the Anthropic API during a critical multi-step operation. Which strategy should the architect implement to ensure the agent completes its task successfully?
⚠ Common exam trap
Candidates often suggest increasing the model temperature or changing the system prompt. These do not solve transient infrastructure issues and will result in repeated failures during high-traffic periods.
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
✓
Implement exponential backoff with jitter in the orchestrator
Transient API errors like 'overloaded_error' are common in high-traffic environments. A robust agentic architecture must handle these gracefully using exponential backoff. This prevents the agent from failing the entire task due to a temporary service interruption and ensures that the long-running state of the agent's work is preserved and resumed.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Immediately terminate the agent and alert the user
Why it's wrong here
Terminating the session on a transient error is a poor user experience and leads to wasted computational work. Since 'overloaded_error' is usually temporary, the system should attempt to recover automatically rather than forcing the user to restart the entire multi-step process from the beginning, losing all current progress.
- ✗
Restart the entire agentic loop from the first message
Why it's wrong here
Restarting from scratch is inefficient and costly, as it repeats all previous tool calls and reasoning steps. This significantly increases latency and token usage. The system should instead retry the specific failed request, maintaining the existing conversation history and state to continue exactly where the error occurred.
- ✓
Implement exponential backoff with jitter in the orchestrator
Why this is correct
This is the standard resilience pattern for distributed systems. Retrying the request after an increasing delay, combined with a small amount of randomness (jitter), helps mitigate congestion on the API server while allowing the agent to eventually proceed with its task once the service stabilizes.
- ✗
Reduce the temperature of the next request to 0
Why it's wrong here
The error shown is a service-level error related to API capacity, not a model generation error. Changing the temperature has no effect on the server's ability to process the request and will not resolve the 'overloaded' status. It is an irrelevant parameter change for this specific technical failure.
About these practice questions
One of 262 original CCAR-P 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-P 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-P exam.