PMI-RMP · Question #82
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
The correct answer is C. Add the identified risk to the risk register.. All identified risks - regardless of their probability or impact level - must be added to the risk register. The risk register is the primary document for tracking all risk information including description, probability, impact, triggers, owners, and planned responses. It is not
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 a quality control management control chart.
- BAdd the identified risk to the issues log.
- CAdd the identified risk to the risk register.
- DAdd the identified risk to the low-level riskwatchlist.
How the community answered
(33 responses)- A3% (1)
- B12% (4)
- C79% (26)
- D6% (2)
Explanation
All identified risks - regardless of their probability or impact level - must be added to the risk register. The risk register is the primary document for tracking all risk information including description, probability, impact, triggers, owners, and planned responses. It is not an issue (issues are events that have already occurred, so B is wrong). A quality control chart (A) is unrelated to risk tracking. A low-level risk watchlist (D) is reserved for risks that are below a threshold of concern; this risk has significant impact and secondary risks, so it warrants full documentation in the risk register.
Topics
Community Discussion
No community discussion yet for this question.