CCAR-P Practice Question: Stakeholder Communication and Lifecycle Management
A stakeholder wants to change the project scope halfway through. How do you evaluate the impact?
⚠ Common exam trap
Candidates often agree to changes immediately or reject them outright, failing to perform the necessary formal impact analysis required to assess how scope changes affect project timelines and resources.
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 formal impact analysis and present the trade-offs.
Managing scope creep involves a structured impact analysis, covering cost, timeline, and technical feasibility. The architect must ensure that the stakeholder understands the trade-offs of their request. This is vital for maintaining project alignment and ensuring that the team is not overloaded with un-resourced tasks that will derail the core objectives and negatively impact the quality of the final deliverable.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Accept the change immediately to keep the stakeholder happy.
Why it's wrong here
Accepting changes without analysis is a recipe for project failure. It leads to scope creep, resource overextension, and missed deadlines. The architect must maintain a professional balance between stakeholder satisfaction and the project's actual capacity and goals, ensuring that any changes are viable and clearly defined before moving forward.
- ✓
Perform a formal impact analysis and present the trade-offs.
Why this is correct
A formal impact analysis is the standard professional approach for managing project scope. It forces the team to consider the technical, cost, and time implications of the change. Presenting these trade-offs clearly to the stakeholder allows them to make an informed decision on whether the change is truly worth the required investment.
- ✗
Deny the request without explanation to prevent scope creep.
Why it's wrong here
Denying a request without explanation is unprofessional and damages the stakeholder relationship. The architect should be collaborative and help the stakeholder understand why the request might not be feasible or why it requires a significant change in scope. Transparency is key to maintaining trust even when the answer is no.
- ✗
Work on the request secretly and surprise them later.
Why it's wrong here
Surprising stakeholders with changes is a major risk that often leads to misunderstandings and alignment failures. If the change was not requested or approved, it should not be worked on. This behavior demonstrates a lack of accountability and undermines the governance of the project, creating potential for significant technical debt.
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.