Pass the PMI PMI Certification PMI-RMP Questions and answers with CertsForce

 A decision tree analysis is a tool that helps to evaluate and select the best option among different alternatives based on costs and probabilities. A decision tree analysis uses a graphical representation of a decision problem, where each node represents a decision point, a chance event, or an outcome. The branches of the tree show the possible choices, events, or consequences that can occur at each node. The end nodes of the tree show the expected value or payoff of each option, which is calculated by multiplying the probability and the cost or benefit of each outcome. A decision tree analysis can help to compare the expected values of different options and choose the one that maximizes the benefit or minimizes the cost1. A decision tree analysis can also help to incorporate uncertainty and risk into the decision making process, as it shows the range of possible outcomes and their likelihoods2. Therefore, the project manager should perform a decision tree analysis to evaluate and select the best option based on costs and probabilities for a mega facility development project. Performing a FMECA fault tree analysis, conducting a sensitivity analysis, or conducting an analytic hierarchy process are not the best options to evaluate and select the best option based on costs and probabilities. A FMECA fault tree analysis is a tool that helps to identify and analyze the potential causes and effects of failures in a system or process. It uses a graphical representation of a failure event, where each node represents a basic or intermediate event that contributes to the failure. The branches of the tree show the logical relationships between the events, using AND or OR gates. A FMECA fault tree analysis can help to calculate the probability and severity of failures, as well as to prioritize and mitigate the risks3. However, a FMECA fault tree analysis does not help to compare different options or alternatives, as it focuses on a single failure scenario. Conducting a sensitivity analysis is a tool that helps to measure how the uncertainty in the input variables of a model affects the output or outcome of the model. It uses a graphical or numerical representation of the relationship between the input and output variables, showing how the output changes when the input changes. A sensitivity analysis can help to identify the most critical or influential variables, as well as to test the robustness or reliability of the model4. However, a sensitivity analysis does not help to compare different options or alternatives, as it focuses on a single model or option. Conducting an analytic hierarchy process is a tool that helps to evaluate and select the best option among different alternatives based on multiple criteria. It uses a mathematical method of pairwise comparison, where each alternative is compared to each other in terms of each criterion. The results of the comparisons are then aggregated into a matrix, which shows the relative importance or preference of each alternative. An analytic hierarchy process can help to rank the alternatives and choose the one that best satisfies the criteria5. However, an analytic hierarchy process does not help to incorporate costs and probabilities into the decision making process, as it relies on subjective judgments and preferences. References: 1, 2, 3, 4, 5.

A decision tree analysis is a quantitative risk analysis technique that helps evaluate and select the best option based on costs and probabilities. It visually represents different decision paths and their associated probabilities, allowing the project manager to compare and select the most appropriate option for the project.

The correct answer is C. The risk owner should have communicated with the project manager so that a designated stakeholder could have been assigned to accept accountability for implementing risk responses.

The core problem in this scenario is not simply that the hardware failed. The real failure is that no one was available and accountable to respond when the risk event occurred . In sound risk management practice, each significant risk should have a clearly assigned risk owner responsible for monitoring the risk and ensuring that the agreed response is implemented. If that individual becomes unavailable, responsibility should not be left unattended. A backup or delegated stakeholder should be assigned so that accountability continues without interruption.

This makes option C the best answer because it addresses the actual governance gap: lack of continuity in risk ownership and response accountability. Proper planning for risk response execution includes ensuring coverage when the assigned owner is absent.

Why the other options are incorrect:

A. The project manager should have requested and mandated that no vacations be taken during critical implementation activities or until all implementation had been completed for the project. This is unrealistic and not a proper risk management control. Projects should be structured so that important responsibilities continue even when people are unavailable. Preventing vacations is not an appropriate or sustainable risk response strategy.

B. The risk manager should have anticipated this situation and planned for schedule buffers in the project schedule to accommodate the likelihood of failed hardware. Schedule buffers may help absorb delays, but they do not solve the real issue described in the question, which is the absence of anyone responsible for responding to the incident. The key deficiency is accountability, not just schedule flexibility.

D. The risk manager should have taken the responsibility of responding to this risk instead of relying on and waiting for the risk owner to return from vacation. The risk manager facilitates and oversees the risk management process, but does not automatically become the response owner for every risk. The correct approach is assignment of the appropriate risk owner or delegate, not centralizing all response responsibility in the risk manager.

Best-practice reasoning:

Risk ownership must be explicit, continuous, and supported by delegation when needed. For critical risks, organizations should ensure backup accountability and escalation paths so that risk responses can be executed immediately when triggers occur.

Reference-aligned basis:

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

assigning a risk owner to each significant risk,

ensuring responsibility for implementing agreed responses,

maintaining continuity of risk response accountability during project execution.

A contingency response plan helps the project manager to be prepared for unexpected situations, such as delays in equipment mobilization. This plan should outline alternative actions to take in case of such delays, minimizing the impact on the project.

According to the PMBOK® Guide, a contingency response plan is a predefined action that the project team will take if an identified risk event occurs. It is part of the risk response plan, which is the output of the Plan Risk Responses process. The contingency response plan helps the project team to reduce the impact of the risk event on the project objectives, such as scope, schedule, cost, and quality. The contingency response plan should be documented in the risk register, along with the risk triggers, the assigned risk owners, and the allocated contingency reserves.

The project manager for project X should prepare a contingency response plan to avoid the situation of being dependent on the availability of critical equipment from another project, project Y. This is because the equipment mobilization is an external dependency, which is a type of inter-project dependency that occurs when a project relies on another project for a deliverable or resource. Inter-project dependencies are a source of risk for the project, as they may cause delays, conflicts, or changes in the project scope or quality. The project manager should identify, analyze, and monitor the inter-project dependencies, and plan appropriate risk responses to deal with them.

The contingency response plan for the equipment mobilization could include alternative sources of equipment, such as renting, purchasing, or borrowing from other projects or vendors. The contingency response plan could also include schedule adjustments, such as fast-tracking, crashing, or re-sequencing the activities that require the equipment. The contingency response plan should be implemented when the risk trigger occurs, such as the notification of the delay from the other project manager. The project manager should also communicate the contingency response plan to the relevant stakeholders, such as the project sponsor, customer, team members, and other project managers.

The other options are not valid for avoiding the situation in the future:

Ask the other project manager to officially confirm the new date in writing: This is not a valid option because it does not address the root cause of the problem, which is the dependency on the equipment from another project. Asking for a confirmation in writing may help to document the issue and track the progress, but it does not prevent the situation from happening again. The project manager should plan for the possibility of delays or changes in the equipment availability, and not rely on the other project manager’s promises or commitments.

Request that the other project manager be added to relevant reports: This is not a valid option because it does not address the root cause of the problem, which is the dependency on the equipment from another project. Adding the other project manager to the relevant reports may help to improve the communication and coordination between the projects, but it does not prevent the situation from happening again. The project manager should plan for the possibility of delays or changes in the equipment availability, and not rely on the other project manager’s information or updates.

Request that the other project manager inform if any additional delays are expected: This is not a valid option because it does not address the root cause of the problem, which is the dependency on the equipment from another project. Requesting the other project manager to inform if any additional delays are expected may help to anticipate and prepare for the impact, but it does not prevent the situation from happening again. The project manager should plan for the possibility of delays or changes in the equipment availability, and not rely on the other project manager’s forecasts or estimates.

PMBOK® Guide1, Project interdependency management2, Interdependencies among projects in project portfolio management3, Mastering PMI-RMP Domains, Tasks, and Enablers for Effective Risk4

Any change to project scope, regardless of perceived size, should trigger a risk analysis to determine potential impact . The PMBOK® Guide states:

" When a change request is submitted, it should be evaluated for potential impact on project objectives, including risk. Analysis of impact is a best practice before implementing any change. "

— PMBOK® Guide, 6th Edition, Section 4.6.2 (Perform Integrated Change Control)

This ensures that the team does not overlook risks associated with even “minimal” changes.

Effective communication with sponsors and stakeholders about both primary and secondary risks is crucial. PMBOK® Guide states:

" Secondary risks... should be communicated to stakeholders and sponsors to ensure transparency and allow for appropriate responses. "

— PMBOK® Guide, 6th Edition, Section 11.5

When a project is delayed, and all contingency reserves have been exhausted, the next step is to escalate the situation to upper management. This escalation allows for additional resources or support to be considered and for strategic decisions to be made at a higher level. According to PMI’s risk management practices, escalation is a key strategy when risks exceed the project ' s control, requiring input or intervention from senior management to resolve​.

Top of Form

Bottom of Form

The risk manager should first update the risk register with the new risk identified by the vendor. This will help in keeping track of all the risks associated with the project and facilitate the subsequent planning and management of the risks.

 The risk manager should update the new risk in the risk register, which is a project document that records the details of all identified risks, including their description, category, cause, probability, impact, and response strategy. Updating the risk register is the first step to acknowledge the existence of the new risk and to document its characteristics and potential effects on the project objectives. The risk register can then be used as an input for the Plan Risk Responses process, where the risk manager can develop appropriate actions to address the new risk. References: PMI, A Guide to the Project Management Body of Knowledge (PMBOK® Guide), Sixth Edition, 2017, p. 397, 441.

The correct answer is B. Develop a contingency plan to cover additional logistics expenses.

This question describes a secondary risk , meaning a new risk created by the implementation of a prior risk response. The original response to supply chain disruption may have been appropriate, but it introduced an additional uncertainty: increased logistics costs. Once a secondary risk is identified, the risk manager should treat it as a normal project risk by analyzing it and determining an appropriate response. In this case, the most suitable response among the options is to develop a contingency plan for the potential added cost exposure.

A contingency plan is appropriate because the project may now face additional expenses that are uncertain in timing or magnitude. Planning for those costs provides a structured and proactive method of managing the new exposure without assuming it must automatically be accepted.

Why the other options are incorrect:

A. Accept the increased costs as part of the project ' s risk threshold. Acceptance may be appropriate in some situations, but the scenario does not indicate that the increased costs are within approved thresholds or that active planning is unnecessary. Immediate acceptance is weaker than preparing a specific response.

C. Switch suppliers to potentially reduce logistics expenses. This may create further disruption or additional risks and is not necessarily the most appropriate first response. The question asks how to address the newly identified risk, and contingency planning is the stronger risk-management action.

D. Incorporate a cost-sharing arrangement with the suppliers. This is a possible contractual tactic, but it is narrower and assumes supplier agreement. It may be part of a response strategy, but it is not the best general answer compared with a formal contingency plan.

Best-practice reasoning:

Secondary risks should be documented, analyzed, assigned, and responded to. When the new risk affects project cost, one practical response is to establish a contingency approach to manage the financial uncertainty if the risk materializes.

Reference-aligned basis:

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

risk responses can generate secondary risks,

secondary risks should be assessed and managed like any other identified risk,

contingency planning is a recognized way to address uncertain future cost impacts.

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​​.

The risk manager should work with the project team to identify and assign a suitable owner for the opportunity.

An opportunity is an uncertain event or condition that may have a positive effect on project objectives. Once an opportunity has been identified and the stakeholders have expressed an intention to capitalize on it, a responsible risk owner should be assigned. The risk owner is accountable for monitoring the opportunity, evaluating appropriate response strategies, coordinating response actions, and ensuring that the agreed response is implemented.

Assigning a risk owner establishes clear accountability. The selected owner should have sufficient authority, knowledge, experience, and access to resources to manage the opportunity effectively.

Option A is incorrect because “mitigate” is generally a response strategy used for threats. Appropriate opportunity response strategies include exploit, enhance, share, escalate, and accept.

Option B may be considered later because enhancing an opportunity can increase its probability or positive impact. However, before developing or implementing the response, responsibility for the opportunity should be assigned to an appropriate owner.

Option D is incorrect because merely monitoring and documenting the opportunity is too passive when stakeholders have specifically indicated that they want to capitalize on it.