CAP · Question #37
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 B. Add the identified risk to the risk register.. The risk register is the master log of all identified project risks, regardless of probability or impact level. Every identified risk must be recorded there first. The issues log is for problems that have already occurred-not future risks. A quality control chart tracks defect tr
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 risk register.
- CAdd the identified risk to the issues log.
- DAdd the identified risk to the low-level risk watchlist.
How the community answered
(50 responses)- A4% (2)
- B74% (37)
- C14% (7)
- D8% (4)
Explanation
The risk register is the master log of all identified project risks, regardless of probability or impact level. Every identified risk must be recorded there first. The issues log is for problems that have already occurred-not future risks. A quality control chart tracks defect trends, not risks. While a low-level risk watchlist is appropriate for risks with both low probability AND low impact, this risk has significant impact, which means it requires active monitoring and a documented response strategy in the risk register. The risk register captures the risk description, probability, impact, risk score, and planned responses.
Topics
Community Discussion
No community discussion yet for this question.