CCAR-P Practice Question: Developer Productivity and Operational Enablement
Exhibit
{
"error": "RateLimitError",
"message": "Too many requests",
"retry_after_ms": 500
}Refer to the exhibit. An application frequently hits rate limits during peak hours. What is the most robust way to improve operational reliability?
⚠ Common exam trap
Candidates often suggest simple retries or increasing quotas, which can cause 'thundering herd' problems and further degrade service availability during peak load.
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 API client layer.
Handling rate limits through exponential backoff is a standard practice to maintain system stability. When the API returns a rate limit error, the client should wait for the specified duration or use a backoff strategy before retrying. This approach prevents overwhelming the service, respects API quotas, and ensures that the application recovers gracefully from traffic spikes, ultimately leading to a more resilient and professional-grade production architecture.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Catch the error and retry the request immediately in a loop.
Why it's wrong here
Immediate retries can lead to a thundering herd problem, where the application continuously hammers the API, worsening the rate limiting issue. This approach ignores the need for backoff, likely resulting in repeated failures and potential service degradation for other parts of the application or other API users.
- ✓
Implement exponential backoff with jitter in the API client layer.
Why this is correct
Exponential backoff with jitter is the recommended pattern for handling transient API errors. By introducing randomness (jitter), the client prevents synchronized retries from multiple instances, effectively smoothing out load. This ensures the application adheres to rate limits while maximizing successful request completion during high-traffic periods.
- ✗
Increase the timeout duration for all API calls in the application.
Why it's wrong here
Increasing timeouts does not address the fundamental issue of rate limiting. If the API is rejecting requests due to volume, waiting longer for a response will not result in a successful request. It only delays the error handling process and may lead to resource exhaustion in the client application.
- ✗
Switch to a synchronous architecture to serialize all API requests.
Why it's wrong here
Serializing requests eliminates concurrency but significantly decreases throughput and user experience. It is not a scalable solution for high-load scenarios. A robust design should support high concurrency through intelligent request management and backoff strategies rather than artificially constraining the system to sequential processing, which limits growth potential.
About these practice questions
This CCAR-P question is part of Courseiva's 262-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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-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.