Latest PMI-RMP Practice Questions BY Spencer

The project manager should evaluate the risk with the team and update the issueing to address the concerns of the stakeholders and local businesses.

This concern is a potential risk that could affect the project's reputation, stakeholder satisfaction, and profitability. The project manager should evaluate the risk with the team and update the issue log, which is a tool for documenting and monitoring the resolution of issues that arise during the project. The issue log should include information such as the issue description, the priority, the owner, the status, and the actions taken. The project manager should also communicate with the stakeholders and the local businesses to address their concerns and seek a mutually beneficial solution. The project manager should not ignore the concern, as it could escalate into a bigger problem. The project manager should not discuss the concern with the local business owners alone, as this could bypass the stakeholders and create more conflicts. The project manager should not update the key risks and perform a quantitative risk analysis, as this is a time-consuming and complex process that may not be necessary for this type of risk. The project manager should not adjust the construction work hours to after business hours, as this could incur additional costs, disrupt the project schedule, and affect the workers' safety and productivity.Reference: PMI, 2017. A Guide to the Project Management Body of Knowledge (PMBOK Guide) -- Sixth Edition. Newtown Square, PA: Project Management Institute, Inc., pp.115-116, 408-4091

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.

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