CCAR-P Practice Question: Stakeholder Communication and Lifecycle Management
Exhibit
{
"error": "Rate limit exceeded",
"retry_after": 30,
"code": "429"
}Refer to the exhibit. Your application is hitting rate limits. A stakeholder is concerned about the user impact. What is your communication strategy?
⚠ Common exam trap
Candidates often focus solely on the technical fix (e.g., increasing limits) without addressing the communication aspect, leaving stakeholders unaware of the system's resilience and current recovery status.
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
✓
Explain the rate limit, the automatic retry mechanism, and the scaling plan.
When hit by technical constraints, the architect must communicate the limitation, the current mitigation (retry logic), and the plan for long-term scaling. This is vital because stakeholders need to know that the system is self-healing, but also that you are actively working on increasing capacity. Clear communication prevents panic and demonstrates that the system was designed with resilience in mind, maintaining stakeholder trust during temporary service interruptions.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Tell them the service is unusable and wait for Anthropic to fix it.
Why it's wrong here
Telling stakeholders the service is unusable is inaccurate and shows a lack of architectural ownership. Rate limits are a standard part of API usage that should be handled by robust application logic, such as exponential backoff. This answer deflects responsibility rather than explaining how the system is currently managing the issue.
- ✓
Explain the rate limit, the automatic retry mechanism, and the scaling plan.
Why this is correct
This provides a comprehensive answer that covers the problem (rate limits), the immediate fix (retry mechanisms), and the long-term solution (scaling). This approach demonstrates control, foresight, and a proactive management style, which reassures the stakeholder that the issue is understood and being handled correctly according to architectural best practices.
- ✗
Ignore the issue until the stakeholder asks about it again.
Why it's wrong here
Ignoring a known, recurring error is a failure to manage the application lifecycle. Proactive communication is essential for maintaining trust. By the time a stakeholder asks, the issue could have already negatively impacted users. Being transparent from the start is much better than waiting for the stakeholder to discover the issue.
- ✗
Blame the engineering team for poor code quality.
Why it's wrong here
Assigning blame within the team is toxic and unprofessional. The architect represents the entire team and should focus on solutions. Even if the code needs improvement, the focus should be on the technical path to resolution, not on creating internal conflict. This behavior destroys team morale and professional relationships.
About these practice questions
Courseiva writes every CCAR-P question from scratch — 262 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-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.