The correct answer is C. Revise the risk register to reflect changes in risk status and include new mitigation actions.
The question asks which document should be updated to reflect the current status of risks after a regular project risk review meeting. In standard project risk practice, the risk register is the primary document used to record identified risks, their current condition, ownership, probability, impact, triggers, response actions, and status updates. When risks are reviewed during recurring meetings, the risk manager should update the risk register so it accurately reflects the latest information.
This includes:
* changes in probability or impact,
* status of existing response actions,
* newly identified mitigation activities,
* newly identified risks,
* closed risks,
* secondary or residual risks where relevant.
Why the other options are incorrect:
* A. Maintain the risk response plan and continuously monitor actions taken to mitigate risks. This describes an activity, not the main document that captures the current status of each risk. The question asks specifically which document should be updated.
* B. Ensure that the risk management plan is reviewed to incorporate adjustments in risk strategies. The risk management plan defines the overall approach, methodology, roles, thresholds, and reporting processes for risk management. It is not the document typically updated during routine monthly reviews to show current risk status.
* D. Update the project schedule to reflect the impacts of risks and adjustments to timelines. The schedule may need updates if risks affect timelines, but it is not the core risk tracking document. The direct and primary document for risk status is the risk register.
Best-practice reasoning:
Routine risk monitoring requires accurate and current risk documentation. The risk register is the operational tool used to track ongoing changes in the project's risk profile and response progress.
Reference-aligned basis:
This answer is consistent with standard risk management guidance that emphasizes:
* the risk register as the central repository for identified risks and their status,
* updating the register during monitoring and review activities,
* recording response actions and changes in exposure over time.
References:
PMI, A Guide to the Project Management Body of Knowledge (PMBOK Guide) , Monitor Risks PMI, Practice Standard for Project Risk Management ISO 31000, risk recording, monitoring, and review principles