CCAR-P Practice Question: Stakeholder Communication and Lifecycle Management
Midway through a Claude integration project, a business stakeholder asks you to add a feature that would let end users upload arbitrary documents and have Claude answer questions about them. The feature is not in the signed statement of work, and the delivery team is two weeks from the first production milestone. What should you do first?
⚠ Common exam trap
The trap here is treating a mid-project change request as either an automatic yes or an automatic no, when the architect's job is to price the change and let the accountable sponsor choose.
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
✓
Perform a lightweight impact assessment covering effort, risk, cost, and milestone impact, then present options with a recommendation to the sponsor and stakeholder.
Scope changes mid-project are normal, and the disciplined response is a fast, lightweight impact assessment that converts an informal ask into a decision the sponsor can make with eyes open. Presenting effort, risk, cost, and milestone impact alongside options respects both the signed commitment and the stakeholder's underlying need.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Escalate the request to the project management office and let them decide whether to approve the change.
Why it's wrong here
Escalation without analysis hands the PMO a decision it cannot make well, because only the delivery team can size the technical effort and risk. The architect owns the impact assessment; the governance body owns the approval. Skipping the assessment delays the decision and weakens the architect's credibility as a trusted advisor.
- ✗
Accept the request and absorb the work into the current sprint so the stakeholder sees responsiveness.
Why it's wrong here
Absorbing unplanned work into a milestone sprint is scope creep by another name. It silently consumes buffer, endangers the committed production date, and sets a precedent that signed scope can be changed verbally. If the milestone then slips, the architect owns the failure while the stakeholder never formally weighed the trade-off.
- ✓
Perform a lightweight impact assessment covering effort, risk, cost, and milestone impact, then present options with a recommendation to the sponsor and stakeholder.
Why this is correct
Change requests are handled through impact assessment, not instant acceptance or refusal. Quantifying effort, new risks such as document-handling and prompt-injection exposure, incremental API cost, and the effect on the committed milestone lets the sponsor make an informed trade-off, which is the architect's proper role in lifecycle management.
- ✗
Decline the request and tell the stakeholder to raise it at the next quarterly planning cycle.
Why it's wrong here
A flat refusal with no analysis treats a potentially valuable request as noise and damages the relationship. The stakeholder may have a genuine business driver, and deferring without understanding it forfeits the chance to shape a cheaper interim option or to trade it against lower-priority scope.
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.