PMI-RMP Dumps with Practice Exam Questions Answers

 According to the PMI-RMP Exam Content Outline1, one of the tasks in the domain of risk identification is to “review project documents, assumptions, and constraints, and understand the project environment and organizational factors to identify risks”. The project charter, work breakdown structure (WBS), and scope statement are essential project documents that provide information about the project objectives, deliverables, requirements, assumptions, and constraints. Without these elements, the risk manager will have difficulty identifying and evaluating the risks that may affect the project. Therefore, the best answer is D. References: 1: PMI-RMP Exam Content Outline, page 7.

The Delphi technique is a structured communication process designed to build consensus among a group of experts and stakeholders when opinions differ and a quantitative assessment is needed. It uses rounds of anonymous input and feedback, allowing experts to refine their views based on others' anonymous contributions. This approach is especially useful when stakeholders are in disagreement and objective quantification of risk is required.

PMBOK® Guide Extract:

“The Delphi technique is a way to reach a consensus of experts. Project risk experts participate in this technique anonymously. A facilitator uses a questionnaire to solicit ideas about the important project risks. The responses are summarized and recirculated to the experts for further comment. Consensus may be reached in a few rounds of this process. The Delphi technique helps reduce bias in the data and keeps any one person from having undue influence on the outcome.”

— PMBOK® Guide, 6th Edition, Section 11.2.2.4

ISO 31000 Reference:

“Facilitated workshops and expert elicitation techniques, such as the Delphi method, can help achieve an objective and consensus-based understanding of complex risks.”

— ISO 31000:2018, Section 6.4.2

In this scenario, since the stakeholders are in disagreement and the project involves complex, location-specific disaster recovery requirements, the Delphi technique (Option D) is the officially recommended approach to achieving consensus and quantifying risk.

The project’s contingency allowance is a provision in the project budget that is intended to cover known risks that may affect the project costs. The risk of increased fuel costs was identified and included in the contingency allowance, so the project manager should use it to process the freight invoices at the actual shipping costs. This is the best way to handle the risk without affecting the project scope, schedule, or quality. Requesting a formal change order from the customer (option B) is not necessary, as the project budget already has a provision for this risk. Processing the freight invoices for the budgeted amount and hoping the shipping company will forgive the difference (option C) is unethical and unprofessional, as it violates the terms of the contract and the PMI Code of Ethics and Professional Conduct. Asking the project sponsor to cover the additional shipping costs on the company’s reserves account (option D) is also not appropriate, as the company’s reserves are meant for unknown risks that are beyond the project’s control, not for known risks that are already accounted for in the project budget. References: PMI, The Standard for Risk Management in Portfolios, Programs, and Projects, 2019, p. 72; PMI, A Guide to the Project Management Body of Knowledge (PMBOK® Guide), 6th ed., 2017, p. 252.

The project manager should use the contingency allowance to cover the additional shipping costs, as it was specifically included in the project budget for such risks. This approach avoids requesting unnecessary changes or relying on external sources to cover the cost overrun.

The risk register is a dynamic document that must capture not only planned risk responses but also the actual outcomes of risks and the effectiveness of risk responses implemented. According to the PMBOK® Guide:

“The risk register should be updated with information on the results of risk responses, risk event outcomes, and actual effectiveness of the actions taken. This enables ongoing learning and continuous improvement in risk management.”

— PMBOK® Guide, 6th Edition, Section 11.7.3.2 (Project Document Updates: Risk Register)

This ensures that both the realized outcomes of risks and the success or failure of responses are tracked for future reference and lessons learned.

The risk manager should use the Delphi method in this situation, as this is a technique that can help resolve differences among experts and reach a consensus on the identified risks and their characteristics. The Delphi method is a tool used to make quick decisions with consensus. This technique consists of sending several sets of anonymous questions to each expert. This is followed by a group discussion after every round. The Delphi method can help the risk manager to solicit the opinions of all experts without revealing their identities. This way, the experts can express their views freely and honestly, without being influenced or intimidated by others. The Delphi method can also reduce personal bias, ego, or emotional conflict among the participants. The risk manager can use the results of the Delphi method to create a list of potential risks and their causes, effects, and probabilities. The other options are not appropriate techniques for the risk manager to use in this situation. Brainstorming is a technique that can help generate ideas and identify risks, but it may not be effective in resolving differences among experts, as it involves open and spontaneous discussion. Focus group is a technique that can help collect requirements and opinions from stakeholders, but it may not be suitable for resolving technical disagreements among experts, as it involves a moderated and structured discussion. Checklist analysis is a technique that can help identify risks based on historical information and lessons learned, but it may not be helpful in resolving differences among experts, as it involves a predefined list of potential risks. References: 3, 4, 5