PMP · Question #1025
A construction project to build a fish hatchery is in execution. The operations group notified the project manager about a concern that might turn into a potential issue; however, the concern could…
The correct answer is C. Risk register. A concern that might develop into an issue but is not yet a problem should be recorded in the risk register for tracking and potential mitigation.
Question
A construction project to build a fish hatchery is in execution. The operations group notified the project manager about a concern that might turn into a potential issue; however, the concern could not be addressed. In which project document should the project manager record the concern?
Options
- ARequest for information
- BScope statement
- CRisk register
- DIssue log
How the community answered
(64 responses)- A3% (2)
- B11% (7)
- C78% (50)
- D8% (5)
Why each option
A concern that might develop into an issue but is not yet a problem should be recorded in the risk register for tracking and potential mitigation.
A Request for Information (RFI) is typically used to solicit data from vendors or stakeholders, not to record an internal project concern.
The scope statement defines what is included and excluded from the project and is not the appropriate document for tracking potential operational concerns.
A concern that 'might turn into a potential issue' but 'could not be addressed' signifies an identified future uncertainty with a potential impact, which is the definition of a risk. The risk register is the appropriate document to record such potential problems for further analysis, planning, and monitoring.
An issue log is for problems that have already occurred or are currently happening, whereas this concern is still a potential future event.
Concept tested: Risk identification and documentation
Topics
Community Discussion
7
Grace U.Jul 4, 2026The correct answer is C. The key phrase in this question is that the concern might turn into a potential issue, which means it has not actually happened yet and therefore belongs in the risk register. D is the trap here because people see the word issue and immediately jump to the issue log, but the issue log is strictly for problems that have already materialized. Since the operations group raised a future uncertainty that could not be immediately resolved, you document it as a risk to track and analyze for potential responses later.
Fatima Z.Jul 5, 2026Confirmed C. COULD not be addressed means COULD happen, so it is a risk, not an issue.
Grace U.Jul 8, 2026Right call, and the flip side is that once it actually happens and you are dealing with it, it becomes an issue, so timing is the whole distinction here.
Luis F.Jul 5, 2026C is correct, a concern that might happen is a risk, so it goes in the risk register.
Fatima Z.Jul 6, 2026Co-sign C, just remember the register is for identified risks while the risk report is the summary you feed to stakeholders, so think Register equals Raw, Report equals Rolled-up.
Viktor S.Jul 5, 2026C is correct because the keyword is "potential" - it hasnt happened yet, so it goes in the risk register, not the issue log. The issue log is for things that have already materialized into actual problems, so the real question is where do you draw that line when a concern is actively brewing but hasnt fully triggered?
Luis F.Jul 6, 2026Good call on C, Viktor, but worth noting that if the risk is actively brewing and has crossed into impacting the project right now, even partially, PMI wants you logging it in the issue log AND keeping the risk register entry, they arent mutually exclusive.