PMP People — Leading Projects Practice Question
You are managing a project where a key stakeholder requests a scope change that would add significant value but also increase risk and cost. Which TWO actions should you take FIRST?
⚠ Common exam trap
The PMP exam often tests the misconception that a change adding value should be immediately accepted or rejected based on risk alone, when the correct first step is always to document and analyze through the formal change control process.
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
✓
Document the change request and submit it through the change control process
The PMBOK Guide requires that all scope changes be formally documented and submitted through the change control process, regardless of perceived value. This ensures traceability, stakeholder alignment, and proper evaluation before any action is taken. Option C is correct because analyzing the impact on scope, schedule, cost, and risk is a mandatory step within the integrated change control process to inform the decision-making body (e.g., CCB).
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Reject the change because it introduces additional risk
Why it's wrong here
This action is incorrect because a project manager should not unilaterally reject a change request solely based on perceived risk without a formal analysis. All change requests, regardless of initial impression, must first be documented and then thoroughly assessed for their potential impacts on all project constraints and objectives, including opportunities for risk mitigation or potential benefits. A comprehensive evaluation through the change control process is essential to make an informed decision, rather than an immediate dismissal.
- ✓
Document the change request and submit it through the change control process
Why this is correct
This is the correct initial action when a stakeholder requests a change. All proposed changes, regardless of their origin or perceived importance, must be formally documented as a change request. Subsequently, this documented request must be submitted into the integrated change control process, which ensures a structured review, analysis, and approval or rejection by the appropriate change control board or authorized personnel. This systematic approach maintains project control and traceability.
- ✓
Analyze the impact of the change on scope, schedule, cost, and risk
Why this is correct
This is a crucial and correct step within the integrated change control process, typically performed after a change request has been documented and before a decision is made. A thorough analysis involves evaluating the potential effects of the proposed change across all project baselines and constraints, including scope, schedule, cost, quality, resources, and risk. This comprehensive impact assessment provides the necessary data for the change control board or project sponsor to make an informed decision regarding the change's approval or rejection.
- ✗
Accept the change because it adds value to the project
Why it's wrong here
Unilaterally accepting a change request, even if it appears to add value, is an incorrect action for a project manager. Bypassing the formal integrated change control process can lead to uncontrolled scope creep, unmanaged risks, and unforeseen negative impacts on project baselines, such as schedule delays or budget overruns. All changes must undergo proper documentation, analysis, and formal approval to ensure alignment with project objectives and stakeholder expectations.
- ✗
Update the project baseline to include the new scope
Why it's wrong here
This action is premature and incorrect because project baselines (scope, schedule, cost) can only be updated *after* a change request has been formally approved through the integrated change control process. Updating a baseline without prior approval signifies a lack of control and can invalidate the project's performance measurement baseline. The baselines serve as the reference point for measuring project performance, and any modification requires strict adherence to the established change management procedures.
Go deeper
Related to this question
Learn chapter
Introduction to the PMP Exam and Project Management Basics
Key term
Change Control Process
A formal, structured procedure used to manage any changes to a project's scope, schedule, budget, or requirements, ensuring every modification is reviewed, approved, tested, and documented before implementation.
About these practice questions
One of 800 original PMP 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 by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PMP practice question is part of Courseiva's free PMI 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 PMP exam.