PK0-005 Project Life Cycle Practice Question

During project execution, a team member identifies a potential risk that was not included in the risk register. The project manager logs it and begins the risk assessment process. Where should this risk be recorded?

⚠ Common exam trap

PK0-005 often tests the distinction between risk register (potential future events) and issue log (current problems), so candidates must recognize that a newly identified risk belongs in the risk register even if discovered during execution.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Risk register

The risk register is the correct answer because it is the formal document where all identified risks, including newly discovered ones during execution, are recorded, assessed, and tracked. When a team member identifies a potential risk not previously documented, the project manager logs it in the risk register and then performs qualitative and quantitative risk analysis to determine its probability and impact. This ensures the risk is managed alongside all other project risks.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✓
Risk register
Why this is correct
Logging the newly identified risk in the risk register satisfies the stem's requirement to record it during execution. The register is the single repository capturing each risk's description, probability, impact, owner, and response, so assessment outputs and tracking updates are appended there as the risk lifecycle progresses.
✗
Issue log
Why it's wrong here
An issue log tracks problems that have already occurred and are impacting the project, whereas this is a potential future risk still undergoing assessment. It is tempting because both logs record project concerns, but the issue log is for realised events, not unassessed risks.
✗
Change request log
Why it's wrong here
A change request log records formal requests to alter scope, schedule, cost or baselines, not newly identified risks. It is tempting because both logs capture submitted items, but a risk awaiting assessment is not a change; it belongs in the risk register until it is realised or a response requires a change.
✗
Lessons learned
Why it's wrong here
Lessons learned capture retrospective knowledge at project or phase closure, so recording a live risk there delays assessment and hides it from active tracking. It is tempting because lessons learned do document risks, but only after they have been realised and reviewed, not while assessment is beginning.

Go deeper

PK0-005 Project Life Cycle Practice Question

Why each option matters

Option-by-option breakdown

Related to this question