PMI Updated PMI-RMP Exam Questions and Answers by kasper

In the early stages of a project, the risk management team leader should conduct qualitative risk analysis to prioritize potential risks. This will help the team to focus on the most significant risks and develop appropriate risk response strategies.

 According to the PMI-RMP Handbook, the early stages of the project are the best time to establish the risk management plan, which is a document that describes how risk management activities will be structured and performed on the project. It is one of the main outputs of the Plan Risk Management process. The risk management plan should be developed with the involvement and input of key stakeholders, such as the project sponsor, customer, team members, subject matter experts, and other relevant parties. The risk management plan should also define the roles and responsibilities of the stakeholders in risk management, as well as the reporting and escalation mechanisms.

The risk management team leader, who is a risk management certified candidate in their domain, should educate stakeholders on best practices to perform risk management in the early stages of the project. This is because the stakeholders may have different levels of knowledge, experience, and expectations regarding risk management, especially in an organization that spans across different countries. The risk management team leader should provide training, coaching, and guidance to the stakeholders on how to apply the risk management processes, tools, and techniques, as well as how to use the risk management plan. The risk management team leader should also promote a positive risk culture and encourage stakeholder participation and collaboration in risk management activities.

The other options are not valid for what the risk management team leader should do in the early stages of the project:

Conduct qualitative risk analysis to prioritize potential risks: This is not a valid option because the qualitative risk analysis is part of the Perform Qualitative Risk Analysis process, which comes after the Identify Risks process and before the Perform Quantitative Risk Analysis process. The risk management team leader should not conduct the qualitative risk analysis before developing the risk management plan and identifying the risks.

Plan a solid risk response plan and secure the necessary funding: This is not a valid option because the risk response plan is part of the Plan Risk Responses process, which comes after the Perform Qualitative Risk Analysis and Perform Quantitative Risk Analysis processes. The risk management team leader should not plan the risk response plan and secure the necessary funding before developing the risk management plan, identifying, and analyzing the risks.

Benchmark to an organization which has executed a similar project: This is not a valid option because benchmarking is a technique for risk identification, but it is not the only one. The risk management team leader should use a combination of techniques to identify risks, not just focus on one aspect. Also, benchmarking is not the same as educating stakeholders, which implies providing training, coaching, and guidance on risk management best practices.

PMI-RMP Handbook1, PMBOK® Guide2, Practice Standard for Project Risk Management2

The correct answer is B. Work with stakeholders to achieve consensus on risk thresholds.

Risk thresholds represent the specific levels of risk exposure or variation that stakeholders are willing to accept. Because thresholds are closely tied to stakeholder risk appetite, tolerance, project objectives, business priorities, and governance expectations, they should not be set by the project team alone. The risk manager should therefore work collaboratively with stakeholders to confirm and agree on those thresholds .

The question states that the team member is assessing and confirming thresholds using lessons learned from similar projects. Historical information is useful input, but thresholds for the current project must still be validated with the relevant stakeholders. In a complex, high-risk city-center construction project, many stakeholder interests may influence acceptable risk levels, including cost, schedule, safety, regulatory exposure, public disruption, and contractual obligations. For that reason, stakeholder consensus is the most appropriate action.

Why the other options are incorrect:

A. Develop risk assessment processes and tools to quantify risk thresholds Processes and tools may support analysis, but they do not themselves establish agreed thresholds. Thresholds must reflect stakeholder acceptance levels, not just analytical design.

C. Use subject matter experts and historical data to estimate risk thresholds This is useful supporting input, especially from past projects, but the question asks what the risk manager should do to assess and confirm the thresholds. Estimates from experts and history are not sufficient without stakeholder agreement.

D. Review regulatory requirements and the contract to identify risk thresholds Regulatory and contractual limits are important constraints, but they do not fully define project risk thresholds. Stakeholder tolerance may be narrower than legal or contractual boundaries.

Best-practice reasoning:

Risk thresholds should be established and validated during risk planning in consultation with key stakeholders because thresholds guide evaluation, prioritization, escalation, and response decisions. Without stakeholder agreement, the project may misjudge which risks are acceptable and which require action.

Reference-aligned basis:

This answer is consistent with standard risk management guidance that emphasizes:

risk thresholds are linked to stakeholder risk appetite and tolerance,

thresholds are established during planning,

stakeholder engagement is necessary to define and confirm acceptable levels of risk exposure.

The project manager should discuss the risk response strategies with the stakeholders to handle their expectations. This will help the project manager to align the risk responses with the stakeholder’s risk appetite, preferences, and expectations. It will also help the project manager to obtain the stakeholder’s support and approval for the risk responses. This is the best way to ensure clear visibility on the project risks and progress. Adding buffers to the schedule to accommodate risk (option A) is not a good practice, as it may create false expectations and hide the true impact of risk. Ensuring the risk register includes all identified risks (option B) is important, but it is not enough to handle stakeholder expectations. The project manager also needs to communicate the risk register to the stakeholders and discuss the risk responses with them. Developing a communication plan to share updates on risks (option D) is also a good practice, but it is not sufficient to handle stakeholder expectations. The project manager also needs to involve the stakeholders in the risk response planning process and obtain their feedback and approval. References: PMI, The Standard for Risk Management in Portfolios, Programs, and Projects, 2019, p. 97; PMI, A Guide to the Project Management Body of Knowledge (PMBOK® Guide), 6th ed., 2017, p. 407.

The project manager should develop a communication plan to share updates on risks (D) to handle stakeholder expectations, especially since the organization has a low risk appetite and stakeholders are very engaged. This approach ensures that stakeholders are regularly informed about the project ' s risks and progress, addressing their concerns and expectations. This is supported by the PMI ' s PMBOK Guide, Sixth Edition.

Project risks should be closed when the stakeholders agree a risk is no longer applicable. This ensures that risks are actively managed and only relevant risks are considered throughout the project lifecycle.

According to the PMI Risk Management Professional (PMI-RMP) Reference Materials, project risks are uncertain events or conditions that may have a positive or negative effect on one or more project objectives1. Project risks can be closed when they are no longer applicable to the project or its activities. The process of closing project risks involves verifying that the risk responses have been completed, documenting the outcomes, and evaluating the effectiveness of the risk management process2. The decision to close a project risk should be made by the stakeholders who are responsible for or affected by the risk, as they are the ones who can determine whether the risk is still relevant or not. Therefore, the correct answer is B. When the stakeholders agree a risk is no longer applicable.