PK0-005 Practice Question: The primary difference between a risk and an…

Answer analysis

Option-by-option breakdown

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

• ✗

  Risks are documented in the issue log; issues are documented in the risk register

  Why it's wrong here

  The logs are reversed: risks belong in the risk register, issues in the issue log. It is tempting because both artefacts track project concerns, and a risk that materialises does migrate into the issue log, so the two documents are genuinely linked in practise.

• ✓

  A risk is an uncertain future event; an issue is a current problem

  Why this is correct

  A risk is a potential future occurrence with uncertain probability and impact, managed through response planning. An issue has already materialised and requires active resolution. The axis of difference is uncertainty versus current reality, not severity or ownership.

• ✗

  Risks are always negative; issues can be positive or negative

  Why it's wrong here

  Risks can be positive (opportunities) as well as negative, so the premise is false. It is tempting because most risk registers focus on threats, and negative wording dominates everyday project language, making the claim feel accurate despite opportunities being formally tracked too.

• ✗

  There is no difference; the terms are interchangeable

  Why it's wrong here

  Risks are uncertain future events that may or may not occur, whereas issues are already materialised problems requiring resolution; the terms are distinct and never interchangeable. It tempts because both are logged and managed, and would be correct only if the organisation deliberately merged the two registers.

Go deeper

Related to this question