PMP · Question #1393
The project manager is reviewing the program risks and issues with key stakeholders. One of the stakeholders wants to understand when the risk may potentially become an issue. What artifact should…
The correct answer is D. Risk register. To understand when a risk may potentially become an issue, the project manager should share the risk register with the stakeholder.
Question
The project manager is reviewing the program risks and issues with key stakeholders. One of the stakeholders wants to understand when the risk may potentially become an issue. What artifact should the project manager share with the stakeholder?
Options
- AProject management plan
- BIssue log
- CRisk management plan
- DRisk register
How the community answered
(29 responses)- A10% (3)
- B3% (1)
- C17% (5)
- D69% (20)
Why each option
To understand when a risk may potentially become an issue, the project manager should share the risk register with the stakeholder.
The project management plan is a high-level document outlining how the project will be executed, monitored, and controlled, but it does not contain the detailed, dynamic status of individual risks.
The issue log tracks problems that have already occurred or are actively occurring, not potential future events or the status of identified risks.
The risk management plan describes how risks will be identified, analyzed, and managed throughout the project, but it does not list the specific details or current status of each individual risk.
The risk register is the primary document that details identified risks, including their probability, potential impact, triggers, and current status. This allows stakeholders to track individual risks and understand the conditions under which a risk might materialize into an actual issue.
Concept tested: Risk management artifacts, risk register contents
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok
Topics
Community Discussion
7
Carlos M.Nov 1, 2025D. The risk register is where you track identified risks along with their probability, impact, and potential timing of occurrence, which is exactly what the stakeholder is asking about. The issue log is only for risks that have already materialized into actual problems.
Fatima Z.Nov 2, 2025Spot on, and remember the difference with IPICK: Issues have materialized, Probability and Impact are tracked in the register, Contingency plans live there too, Keep it updated, and new risks get added as you discover them so you are not scrambling later.
Fatima Z.Oct 22, 2025Leaned toward B, but risks live in D, the risk register, before they hatch into issues.
Hiroshi T.Oct 30, 2025A. The project management plan is the living document stakeholders review.
Fatima Z.Nov 1, 2025D is correct here, Hiroshi. Just remember PMIS is the system, not the plan: think Program Management Information System equals the tool that feeds the data, while the project management plan is the strategy.
Olusegun A.Nov 7, 2025Going with B on this one. The question is asking when a risk may potentially become an issue, and the issue log tracks items that have materialized or are on the verge of materializing, so it is the artifact that shows the stakeholder exactly when that transition happens.
Fatima Z.Nov 9, 2025D is correct here, Olusegun. Think RISK REGISTER equals Risks Recorded, because the question is asking about a risk that may potentially become an issue, and that potential lives in the risk register, not the issue log where things have already materialized.