PMP · Question #1420
A project team member raised a risk that the threat of country-wide power cuts may affect the project time line for a software development project. In the last month, this risk materialized and the…
The correct answer is B. Log it in the risk register and work with the relevant owner to implement the mitigation action plan. C. Analyze the impact of the issue and submit a change request to update the project schedule. Upon a materialized risk that has impacted the project timeline, the project manager must implement the pre-defined mitigation plan and then formally analyze the impact to initiate a change request for the updated project schedule.
Question
Options
- AAsk the team member to work overtime to make up the lime lost so that the project schedule is
- BLog it in the risk register and work with the relevant owner to implement the mitigation action plan.
- CAnalyze the impact of the issue and submit a change request to update the project schedule.
- DInform the project sponsor that the risk has materialized and request that the project budget be
- EExtend the project deadline and update the project schedule to reflect the delay.
How the community answered
(25 responses)- A16% (4)
- B72% (18)
- D8% (2)
- E4% (1)
Why each option
Upon a materialized risk that has impacted the project timeline, the project manager must implement the pre-defined mitigation plan and then formally analyze the impact to initiate a change request for the updated project schedule.
Asking team members to work overtime is a reactive measure that might not resolve a two-month delay caused by a country-wide power cut, and it's generally unsustainable and doesn't address the formal project management steps required.
When a risk materializes and becomes an issue, the project manager should refer to the risk register, identify the assigned risk owner, and ensure that the predefined mitigation or contingency action plan for that specific risk is implemented to address the issue.
Since the project timeline has already been extended by two months, this constitutes a significant change to the project baseline. The project manager must formally analyze the complete impact of this issue on all project constraints and then submit a change request through the integrated change control process to formally update the project schedule.
While informing the project sponsor is generally good practice for significant issues, requesting a budget increase is an assumption, and the immediate impact mentioned is on the timeline; formal impact analysis and change requests should precede such specific requests.
Extending the project deadline and updating the schedule without analyzing the full impact and going through a formal change request process can lead to uncontrolled project changes and is not a best practice.
Concept tested: Risk response implementation, Integrated Change Control, Issue Management
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/perform-integrated-change-control
Topics
Community Discussion
3
Orla P.Jun 6, 2026B and C are your two picks here. Once a risk materializes it becomes an issue, so you log it in the risk register with that status and execute whatever mitigation plan was already in place (B), and you formally analyze the schedule impact then submit a change request through integrated change control to update the baseline (C). The other options either skip the formal process, overburden the team without authorization, or jump straight to outcomes without going through the proper channels first.
Bao N.Jun 8, 2026Solid breakdown, just worth flagging that in some frameworks you log the realized risk as an issue in the issue log rather than updating its status in the risk register, so depending on your organization's PMO standards that distinction could trip you up on the exam.
Wei W.Jun 10, 2026I almost picked C and E, but E skips the register and change control process, so B and C it is.