PMI PMI-RMP - PMI Risk Management Professional (PMI-RMP) Exam

In this situation, the departure of a key project resource was an anticipated risk, and a transition plan was established as a response. However, implementing this plan has introduced new risks, known as secondary risks, which may impact the completion dates of other project-related tasks. According to PMI ' s risk management framework, it ' s essential to address these secondary risks in alignment with the predefined risk management plan. This involves assessing the new risks ' probabilities and impacts, determining appropriate response strategies, and updating the risk register accordingly. By systematically managing secondary risks as outlined in the risk management plan, the project manager can mitigate potential adverse effects on the project ' s schedule and objectives.

PMI Risk Management Study Guide References:

The PMI-RMP Exam Preparation Study Guide highlights the necessity of managing secondary risks, stating that " secondary risks should be identified, analyzed, and planned for in the same manner as primary risks, ensuring that all potential threats to project objectives are adequately addressed. "

The analysis currently being used is qualitative risk analysis. Qualitative risk analysis involves assessing risks based on their likelihood of occurrence and their potential impact on the project. This type of analysis can help identify biases that may be impacting how team members perceive risks.

Qualitative risk analysis is the process of prioritizing individual project risks for further analysis or action by assessing their probability of occurrence and impact as well as other characteristics. Qualitative risk analysis helps to identify the most significant risks that require attention and response planning. One of the tools and techniques used in qualitative risk analysis is risk data quality assessment, which evaluates the degree to which the data about individual project risks is useful for risk management. Risk data quality assessment considers various aspects of data quality, such as reliability, accuracy, integrity, precision, and bias. Bias is the tendency of human judgment to be influenced by personal or organizational preferences, assumptions, beliefs, or emotions, rather than by objective facts or evidence. Bias can affect how project team members perceive and assess risks, leading to inaccurate or incomplete risk analysis results. Therefore, the risk manager who realizes the project team members have biases impacting how they perceive risks is currently using qualitative risk analysis to prioritize the risks and assess the quality of risk data. References: PMI, Practice Standard for Project Risk Management, 2009, p. 37-38, 41-42.

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.

A contingency plan is pre-planned for specific risk triggers. When the trigger is observed, the contingency plan should be activated as specified. PMBOK® Guide states:

" If a risk trigger occurs, the corresponding contingency plan or fallback plan should be implemented as documented in the risk response plan. "

— PMBOK® Guide, 6th Edition, Section 11.6

According to the PMI Risk Management Professional (PMI-RMP)® Examination Content Outline1, one of the tasks in the domain of Risk Response is to call for a project team meeting to review risk strategies and make required adjustments, as needed, based on risk monitoring and reporting1. In this scenario, the risk manager should do this to address the situation of the availability of experts, which is a key risk for the project. The project team meeting will help the risk manager and the project team to evaluate the effectiveness of the current risk response plan, identify any new risks or changes in existing risks, and develop alternative risk strategies and actions to deal with the staffing issue. The project team meeting will also facilitate the communication and collaboration among the project team members and other stakeholders, and ensure that the project objectives and expectations are aligned. The risk manager should not implement a disciplined tracking method and report to stakeholders accordingly, because that is not a proactive risk response strategy, but rather a passive risk monitoring and reporting technique2. The risk manager should not escalate the staffing topic to the sponsor and request more budget for contingencies, because that is not a feasible or appropriate risk response strategy, as it does not address the root cause of the risk or provide a solution to the problem3. The risk manager should not revisit the project charter for scope adjustments and sign them off with the customer, because that is not a risk response strategy, but rather a scope management process that may have negative impacts on the project quality, cost, and schedule, and may violate the contractual agreement with the customer4. References: 1: PMI Risk Management Professional (PMI-RMP)® Examination Content Outline, page 102: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 4563: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 4364: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 133.

The correct answer is C. Collaborate with the project manager to define and apply appropriate risk analysis processes and tools.

The question emphasizes consistent identification and analysis of threats and opportunities during planning. The strongest action is for the risk manager and project manager to work together to establish and apply the appropriate methods, criteria, and tools for assessing environmental factors affecting the project.

Why the other options are incorrect:

A. Coach the project manager on evaluating environmental factors using standard risk assessment techniques. Coaching may help, but the better answer is active collaboration to define and apply the processes and tools.

B. Assign a specialized environmental expert to independently analyze external project factors separately. Expert input can be valuable, but independent separate analysis is not the best primary answer when the need is integrated and consistent project risk assessment.

D. Recommend updating organizational process assets before completing the environmental risk assessment. Organizational assets may be updated later, but that is not the immediate best action.

Reference-aligned basis:

This answer aligns with risk planning practice that risk processes and tools should be defined and applied collaboratively to support consistent analysis.

The project manager should assess and record associated secondary risks and proceed to treat them as any other risks. This involves identifying and evaluating the potential negative health effects of using pesticides and developing a plan to mitigate these risks. While it is important to consider the concerns of residents, the health authorities have determined that not moving forward with the plan will have more serious consequences on public health.

 Secondary risks are those that arise as a direct outcome of implementing a risk response. In this case, the use of pesticides is a risk response to limit the risks of harmful insects, but it may also cause negative health effects to some residents. This is a secondary risk that needs to be assessed and recorded in the risk register, along with its probability, impact, and response plan. The project manager should not suspend the project, as this would ignore the primary risk of harmful insects. The project manager should not consult with health experts to provide a risk trigger, as this is not a valid risk management technique. A risk trigger is an indication that a risk event is about to occur or has occurred, not a condition that prevents a risk response from being implemented. The project manager should not proceed with the project as normal, as this would neglect the secondary risk and its potential consequences. The project manager should follow the risk management process and treat the secondary risk as any other risk in the project. References: PMI. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Chapter 11: Project Risk Management, p. 408. 5

 

When a risk manager notices that the risk register is missing key data, the most critical information they will require first includes the risk description, risk probability, and risk impact. These elements are fundamental to understanding each risk and planning appropriate responses. The risk description provides a clear understanding of what the risk is, while the probability and impact help in assessing the severity and likelihood of the risk occurring, which are essential for prioritizing and managing risks effectively.

PMI’s risk management guidelines emphasize the importance of having these core data points to effectively manage risks throughout the project lifecycle​​.

 

 

 

By hiring a licensed contractor to complete the complex activity, the project manager is transferring the risk associated with that activity to the contractor. This is an example of risk transfer, as the responsibility for managing the risk is shifted from the project manager to the contractor.

According to the PMI Risk Management Professional (PMI-RMP)® Handbook1, one of the domains of the PMI-RMP exam is Risk Response Planning, which involves developing options and actions to enhance opportunities and reduce threats to project objectives1. One of the strategies for negative risks or threats is risk transfer, which involves shifting the impact of a threat to a third party, such as a contractor, a vendor, or an insurer2. In this situation, the project manager is performing risk transfer by hiring a licensed contractor to complete the work that is too complex to complete internally. By doing so, the project manager is transferring the responsibility and liability of the activity to the contractor, who is expected to have the expertise and resources to handle the complexity. The project manager is not performing risk mitigation, which involves reducing the probability and/or impact of a threat2. The project manager is not performing risk acceptance, which involves acknowledging the existence of a threat and making a conscious decision to accept it without taking any action2. The project manager is not performing risk avoidance, which involves changing the project plan to eliminate the threat or protect the project objectives from its impact2. References: 1: PMI Risk Management Professional (PMI-RMP)® Handbook, page 62: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 436.