PMP · Question #911
A project is late due to a large number of scope changes. This was raised as a risk in the risk register during the initiation phase. The team is afraid that they will be blamed in case of failure…
The correct answer is C. Refer to the risk register and follow the mitigation plan. The project is experiencing a known risk (scope changes causing delays) that was identified during initiation. The project manager's first action should be to address this pre-identified risk.
Question
Options
- AAsk the team to document the impact of the risk in detail.
- BRefer to the change log and ensure that changes are documented.
- CRefer to the risk register and follow the mitigation plan.
- DAsk the sponsor for their advice on the way forward.
How the community answered
(28 responses)- A7% (2)
- B4% (1)
- C75% (21)
- D14% (4)
Why each option
The project is experiencing a known risk (scope changes causing delays) that was identified during initiation. The project manager's first action should be to address this pre-identified risk.
While documenting impact is part of risk management, referring to the already established mitigation plan in the risk register is the immediate next step when a known risk materializes.
The change log documents changes, but the core issue is the impact of these changes (a known risk), which should be handled by the risk register's mitigation plan.
Since the scope changes were identified as a risk in the risk register during the initiation phase, the project manager's primary responsibility is to refer to the existing risk management plan and follow the defined mitigation strategy for this specific risk. This proactive approach leverages prior planning to address the current issue effectively.
Consulting the sponsor for advice should occur after the project manager has explored and attempted to implement the predefined risk response, as the sponsor would expect the PM to follow established processes first.
Concept tested: Risk response implementation
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/risk-management
Topics
Community Discussion
7
Dervla O.Mar 11, 2026C is the move here, and the key is that first word in the stem: the risk was already identified and raised. When a known risk materializes, your first stop is always the risk register to execute the planned response, not start a new documentation cycle or escalate to the sponsor. A is a trap because you already have the analysis from initiation, and B is a close second but it serves the change process rather than solving the immediate schedule threat. Read the stem twice on this one, because the phrase "raised as a risk" is your signal to use the risk process.
Mei-Ling H.Apr 4, 2026I first leaned toward A because the team is afraid of blame, so documenting the impact in detail seemed like a natural protective step. But re-reading the stem: the risk was already identified in the risk register during initiation, which means a mitigation plan should already exist, and the qualifier 'first' means you follow that plan before doing anything else.
Ingrid P.Mar 4, 2026C, since the risk was already identified the mitigation plan is your roadmap. Does anyone know if the mitigation plan should be created during Initiation or Planning?
Hiroshi T.Mar 16, 2026Going with A. The risk was already identified in the risk register during initiation, but the team is now reacting emotionally out of fear of blame rather than presenting actionable data. Before the PM can escalate or make any decision on an extension, there needs to be a clear, documented impact analysis so leadership has something concrete to evaluate. Option C sounds tempting since the risk register exists, but if the mitigation plan had been working we would not be in this situation, so you need fresh analysis of the actual realized impact. Getting the team to document the impact also shifts them out of a defensive mindset and back into
Dervla O.Mar 16, 2026Actually it is C because the risk was already identified with a documented mitigation plan, so the correct move is to execute that plan rather than pause for fresh analysis. The question is testing whether you follow the process already in place, not whether you restart impact assessment from scratch.
Grace U.Mar 22, 2026C is right, but I can see why D tempts people given the team's fear of blame. Since this risk was already identified during initiation, the risk register and its mitigation plan are exactly where you turn first instead of escalating to the sponsor.
Mei-Ling H.Mar 25, 2026Agree on C but want to add that the key qualifier is already identified during initiation, which means the PM owns executing the mitigation plan, not escalating.