CCAR-P Advanced Agentic Architecture Practice Question
Exhibit
{
"error": "RateLimitError",
"message": "Too many requests in the last 60 seconds",
"retry_after": 5
}Refer to the exhibit. Your agent is receiving this error during a high-concurrency operation. Which implementation correctly handles this scenario?
⚠ Common exam trap
Candidates mistakenly implement aggressive immediate retries upon hitting rate limits, which exacerbates server congestion and leads to extended application downtime.
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
✓
Wait for the duration specified in 'retry_after' before retrying.
The correct implementation is to respect the 'retry_after' header and back off before attempting another call. This prevents the system from entering a crash loop where it hammers the API with failed requests. By implementing an exponential backoff strategy that honors the provided delay, you ensure the agent remains resilient to transient load issues while complying with the service provider's rate constraints, ultimately increasing the reliability of the overall system.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Discard the task and return a failure message to the user.
Why it's wrong here
Discarding the task is a poor user experience. Rate limits are often transient. A well-designed agent should have the capability to wait and retry automatically before giving up, which allows it to handle temporary spikes in traffic without manual user intervention or task failure.
- ✗
Immediately retry the request without any delay.
Why it's wrong here
Immediate retries will almost certainly fail again and potentially exacerbate the rate limit issue. This behavior constitutes a 'retry storm' that can lead to permanent blacklisting of your API key. You must always wait for the specified time or use exponential backoff to allow the system to stabilize.
- ✓
Wait for the duration specified in 'retry_after' before retrying.
Why this is correct
Respecting the 'retry_after' duration is the standard way to handle rate limiting. It aligns your agent's behavior with the server's requirements, ensuring that your retry attempts occur after the limit has reset. This is the most efficient and polite way to interact with rate-limited external APIs.
- ✗
Switch to a backup API key and continue immediately.
Why it's wrong here
Using backup keys to bypass rate limits can lead to account suspension. Most providers track rate limits by organization or underlying billing entity, not just by individual key. You should architect for resiliency through backoff, rather than attempting to circumvent the limits set by the API provider.
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.