GSLC · Question #495
A project team member has just identified a new project risk. The risk event is determined to have significant impact but a low probability in the project. Should the risk event happen it'll cause…
The correct answer is D. Add the identified risk to the risk register. All identified project risks must be recorded in the risk register regardless of their probability or impact level, as it is the authoritative tracking document for project risks.
Question
A project team member has just identified a new project risk. The risk event is determined to have significant impact but a low probability in the project. Should the risk event happen it'll cause the project to be delayed by three weeks, which will cause new risk in the project. What should the project manager do with the risk event?
Options
- AAdd the identified risk to the issues log.
- BAdd the identified risk to a quality control management control chart.
- CAdd the identified risk to the low-level risk watchlist.
- DAdd the identified risk to the risk register.
How the community answered
(22 responses)- A5% (1)
- B5% (1)
- D91% (20)
Why each option
All identified project risks must be recorded in the risk register regardless of their probability or impact level, as it is the authoritative tracking document for project risks.
The issues log records problems that have already occurred and require immediate resolution, not potential future risk events that have not yet materialized.
A quality control management control chart is used to monitor process performance and identify variances in deliverable quality, not to track project risk events.
A low-level risk watchlist is reserved for risks that have both low probability AND low impact; this risk has significant impact and therefore requires full risk register documentation and active monitoring.
The risk register is the central project management artifact used to document every identified risk, including its probability, impact, owner, and planned response. A risk with significant impact but low probability still warrants full documentation in the register so the project manager can monitor it and prepare contingency plans. Excluding it from the register would leave the team unprepared if the risk materializes.
Concept tested: Project risk identification and risk register documentation
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok
Topics
Community Discussion
No community discussion yet for this question.