CAPM Practice: Determine how to document project controls of predictive, plan-based projects

When a risk materializes: (1) the risk register should be updated to mark the risk as 'occurred/triggered'; and (2) the issue log should be updated with the resulting problem and resolution tracking. The risk register tracks the risk lifecycle; the issue log manages the active problem. Both should be updated to maintain complete project records.

**Why not A:** Tracking the risk only in the risk register as "occurred" is incomplete. While the risk register should be updated, the materialized risk has created an active problem that needs resolution tracking — which is the purpose of the issue log. Both documents should be updated.

**Why not B:** Tracking the event only in the issue log misses the need to update the risk register. The risk register should reflect that this risk has materialized, completing the risk lifecycle record. Using only the issue log loses the connection between the risk and its planned response.

**Why not C:** A change log tracks change requests and their disposition. While the materialized risk may eventually lead to a change request, the immediate need is to document the occurred risk and the active issue requiring resolution — which are tracked in the risk register and issue log respectively.