PMI PMI-RMP Practice Test - Questions Answers, Page 4

List of questions
Question 31

When processing freight invoices for a project, the project manager notices the shipping costs exceeded the budget due to increased fuel costs. The risk manager included this risk in the project's contingency allowance. When reviewing the project budget execution reports, the project manager notices unused budget remaining in other closed tasks of the project that could cover the additional shipping costs.
What should the project manager do?
Process the freight invoices at higher shipping costs against the project's contingency allowance.
Request a formal change order from the customer to increase the project's total budget.
Process the freight invoices for the budgeted amount and hope the shipping company will forgive the difference.
Ask the project sponsor to cover the additional shipping costs on the company's reserves account.
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.Reference: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.
.
Question 32

A new risk manager has been hired on a project and meets with the project director. The project director supplies the project's risk register and asks the risk manager for an analysis of its effectiveness.
What two actions should the risk manager do next? (Choose two.)
Check to ensure that the risk is supported by a Monte Carlo simulation.
Check to ensure that the risks are gathered using Delphi technique.
Check for risk classification and that probability and impact are identified.
Check to ensure that risk origin, triggering event, and ownership is identified.
Check to ensure the risk meeting agenda and supporting documents are distributed.
The risk manager should first check the risk register for proper risk classification, probability, and impact (C), as these are essential components of an effective risk management process. Next, the risk manager should ensure that the risk origin, triggering events, and ownership are identified (D), as this information helps in assigning responsibilities and taking appropriate actions for each risk. Reference to these steps can be found in the Project Management Institute's (PMI) A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition.
The risk manager should check for risk classification and that probability and impact are identified, as these are essential elements of a risk register. Risk classification helps to group risks into categories based on their sources, types, or impacts, which can facilitate risk analysis and response planning. Probability and impact are the two dimensions of risk assessment, which help to measure the likelihood and severity of a risk event, and to prioritize risks based on their significance. The risk manager should also check to ensure that risk origin, triggering event, and ownership is identified, as these are also important components of a risk register. Risk origin refers to the root cause or source of a risk, which can help to understand the nature and characteristics of a risk, and to devise effective risk responses. Triggering event is a specific occurrence or condition that indicates that a risk event has occurred or is about to occur, which can help to monitor and control risks. Ownership is the assignment of a risk to a person or a group who is responsible for managing the risk, which can help to ensure accountability and communication. The risk manager should not check to ensure that the risk is supported by a Monte Carlo simulation, as this is not a mandatory or universal requirement for a risk register. Monte Carlo simulation is a quantitative risk analysis technique that uses computer-generated random scenarios to model the possible outcomes of a project, based on the probability distributions of the input variables. While this technique can provide useful information about the overall project risk exposure and the probability of achieving project objectives, it is not a necessary or sufficient condition for an effective risk register. The risk manager should not check to ensure that the risks are gathered using Delphi technique, as this is also not a compulsory or exclusive requirement for a risk register. Delphi technique is a qualitative risk identification technique that uses a panel of experts to anonymously provide their opinions on potential risks, which are then aggregated and refined through a series of rounds until a consensus is reached. While this technique can help to elicit expert judgment and reduce bias, it is not the only or the best way to identify risks. The risk manager should not check to ensure the risk meeting agenda and supporting documents are distributed, as this is not a relevant or appropriate action for analyzing the effectiveness of a risk register. The risk meeting agenda and supporting documents are part of the risk management plan, which describes how the project team will conduct risk management activities, such as identifying, analyzing, responding, and monitoring risks. The risk meeting agenda and supporting documents are useful for planning and conducting risk meetings, but they are not part of the risk register, which is the output of the risk identification process and the input for the risk analysis and response processes.Reference:PMI. (2017). A Guide to the Project Management Body of Knowledge (PMBOK Guide) -- Sixth Edition. Chapter 11: Project Risk Management, pp. 395-454. 5
Question 33

A project manager works on a long-term and high visibility project at an organization that has a low risk appetite towards this project due to its impact on the company's business. The project sponsors follow up weekly with the project manager, who was just informed by one of the risk owners that the exposure from two high-impact risks are hitting the risk thresholds.
What should the project manager do next?
Update the project management plan to add contingency.
Perform an assumptions and constraints analysis.
Complete an assessment and confirm the response with the sponsors.
Implement mitigation measures for those risks.
According to the PMBOK Guide, 6th edition, Section 11.4.3.1, Risk Thresholds, risk thresholds are the level of risk exposure above which risks are addressed and below which risks may be accepted. Risk thresholds are determined by the organization's risk appetite, which is the degree of uncertainty that an organization is willing to accept in pursuit of its goals. Therefore, when the project manager is informed by the risk owner that the exposure from two high-impact risks are hitting the risk thresholds, the project manager should complete an assessment and confirm the response with the sponsors, who are the key stakeholders for the project and have a low risk appetite.The project manager should not update the project management plan, perform an assumptions and constraints analysis, or implement mitigation measures without first consulting with the sponsors and obtaining their approval.Reference: PMBOK Guide, 6th edition, Section 11.4.3.1, Risk Thresholds
Question 34

The project team recorded a risk in the risk register indicating that weather-related delays may impact equipment delivery during project execution. When it is time to request the equipment shipment there is bad weather, but the client wants the equipment delivered anyway.
What should the project manager do?
Wait until the weather improves before sending the equipment.
Ask the project sponsor to approve shipping the equipment.
Proceed with the planned risk response to move the equipment.
Request the shipment of the equipment to satisfy the client.
The project manager should proceed with the planned risk response to move the equipment, as this is the best way to deal with the weather-related risk that was identified and recorded in the risk register.A risk register is a document that lists all the identified risks, their causes, impacts, probabilities, and responses for a project1.A risk response is a strategy or action that is taken to reduce the negative effects or enhance the positive effects of a risk event2.A risk response should be planned and executed according to the risk management plan, which is a document that describes how risk management activities will be structured and performed on a project3.The risk management plan should also define the roles and responsibilities, risk categories, risk appetite and thresholds, risk identification and analysis methods, risk response strategies, risk monitoring and reporting mechanisms, and risk governance mechanisms3. Therefore, the project manager should follow the risk management plan and the risk register to implement the planned risk response to move the equipment, as this is the most effective and efficient way to manage the risk and meet the project objectives. Waiting until the weather improves before sending the equipment, asking the project sponsor to approve shipping the equipment, or requesting the shipment of the equipment to satisfy the client are not the best options to deal with the weather-related risk. Waiting until the weather improves may cause further delays and increase the cost and scope of the project, as well as damage the relationship with the client. Asking the project sponsor to approve shipping the equipment may not be necessary or feasible, as the project sponsor may not have the authority or the availability to make such a decision. Requesting the shipment of the equipment to satisfy the client may not be realistic or safe, as the bad weather may pose a threat to the quality and integrity of the equipment, as well as the health and safety of the people involved in the transportation.These options may also deviate from the risk management plan and the risk register, which may create confusion and inconsistency in the risk management process.Reference:1,2,3.
Question 35

A project manager has been assigned to a project that is just starting. The organization has a very low risk appetite towards this project due to constraints on budget and schedule. The project stakeholders are very engaged on the project and want to ensure that there is clear visibility on the project risks and progress.
How should the project manager handle stakeholder expectations?
Add buffers to the schedule to accommodate risk.
Ensure the risk register includes all identified risks.
Discuss the risk response strategies with the stakeholders.
Develop a communication plan to share updates on risks.
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.Reference: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.
Question 36

A company in the mining industry accommodates a lot of innovation and changing work conditions. Because of this, the company experiences difficulty in predicting long term business plans.
How should a professional risk manager manage the risks in such situations?
Adopt a predictive approach to manage the risks.
Adopt agile approaches to manage the risks.
Utilize proper documentation to help manage the risks.
Conduct weekly risk management meetings with all stakeholders.
In a company with rapidly changing work conditions and difficulty in predicting long-term business plans, a professional risk manager should adopt agile approaches to manage the risks (B). Agile approaches allow for flexibility, adaptability, and quick response to changes, making them suitable for managing risks in such situations. This is supported by the PMI's PMBOK Guide, Sixth Edition, and the Agile Practice Guide.
A professional risk manager should adopt agile approaches to manage the risks in situations where the company accommodates a lot of innovation and changing work conditions, and experiences difficulty in predicting long term business plans. Agile approaches are adaptive, iterative, and collaborative methods that focus on delivering value and reducing uncertainty in a dynamic and complex environment. Agile approaches can help the risk manager to identify, analyze, respond, and monitor risks in a flexible and timely manner, by using tools and techniques such as risk-adjusted backlog, risk burndown charts, risk-based spike, and risk-based testing. Agile approaches can also help the risk manager to engage the stakeholders and the project team in risk management activities, by using practices such as daily stand-up meetings, sprint planning, sprint review, and sprint retrospective. Agile approaches can enable the risk manager to manage the risks effectively and efficiently, by aligning the risk management strategy with the project goals and the customer needs. Adopting a predictive approach to manage the risks is not the best option, as it may not be suitable or feasible for situations where the project scope, schedule, and budget are uncertain or variable. A predictive approach is a plan-driven and sequential method that relies on upfront planning and detailed documentation to manage the risks. A predictive approach may not be able to cope with the frequent changes and emerging risks that may occur in an innovative and dynamic environment. Utilizing proper documentation to help manage the risks is not the best option, as it may not be sufficient or effective for situations where the project requirements and deliverables are evolving or changing. Proper documentation is a useful and necessary component of risk management, but it is not a substitute for agile risk management practices. Proper documentation may not be able to capture and communicate the current and relevant information about the risks and their impacts in a timely and accurate manner. Conducting weekly risk management meetings with all stakeholders is not the best option, as it may not be optimal or efficient for situations where the project risks and opportunities are changing rapidly or frequently. Weekly risk management meetings are a common and beneficial practice for risk management, but they may not be enough or appropriate for agile risk management. Weekly risk management meetings may not be able to address the risks and their responses as soon as they arise or occur, and they may not be able to involve all the relevant and available stakeholders and project team members.Reference:3,4,5
Question 37

While implementing the risk response plan for a previously identified risk, some secondary risks were identified but not captured on the risk register. The project manager decided to review the risk management plan to ensure this does not happen for future, similar situations.
What should the project manager do next?
Identify secondary or residual risks for associated risk plans.
Develop risk response plans for all identified risks.
Update the communications management plan to avoid future issues
Monitor and control secondary and residual risks in the risk register.
The project manager should monitor and control secondary and residual risks in the risk register. This will ensure that any new risks identified during the implementation of the risk response plan are captured and managed effectively. Monitoring and controlling risks is a continuous process that helps in identifying, analyzing, and planning for new risks as well as updating the risk register as needed.
According to the PMI Risk Management Professional (PMI-RMP) Examination Content Outline, one of the tasks under the domain of Risk Response Planning is to ''identify and assess the effectiveness of alternative strategies to reduce threats or enhance opportunities, such as mitigation, transference, avoidance, and acceptance''1. This implies that the project manager should also consider the potential secondary or residual risks that may arise from implementing the chosen risk response strategy.Secondary risks are new risks that are created as a direct result of implementing a risk response, while residual risks are those that remain after the risk response has been executed2. Both types of risks should be identified and assessed for their impact and probability, and added to the risk register for further monitoring and control. Therefore, the correct answer is A.
Question 38

A project manager is working on a high priority and high profile project. The project team had identified three opportunities, and after analysis, risk responses were recorded. Although risk responses were adequate for the identified opportunities, two of those opportunities were not acted upon. During the risk audit, the project manager found out that several of the planned risk responses were not implemented.
What should the project manager have done to avoid this?
Provided regular training to the risk owners for plan implementation
Determined risk triggers and thresholds in the risk response plan
Increased communications to influence stakeholder risk responses
Updated the project schedule, adding risk owner implementation tasks.
The project manager should have updated the project schedule by adding risk owner implementation tasks. This would have ensured that the planned risk responses were implemented in a timely manner and tracked as part of the project schedule. This would also have allowed the project manager to monitor the progress of risk response implementation and take corrective action if necessary.
According to the PMI-RMP Exam Content Outline and Specifications1, one of the tasks under Domain 4: Risk Monitoring and Reporting is to ''update project schedule, budget, and risk register with risk response outcomes''. This implies that the project manager should have added the risk owner implementation tasks to the project schedule, so that they can be tracked and monitored. By doing so, the project manager could have ensured that the planned risk responses were executed as intended, and that the opportunities were not missed.Reference:PMI-RMP Exam Content Outline and Specifications, page 10.
Question 39

A project manager is working on a complex construction project. During the risk identification process, hundreds of risks were identified. The team seems to be confused regarding on which risks to focus. The project manager advises the team to go ahead and start assessing the likelihood and impact of each risk.
What process is this part of?
Plan Risk Management
Perform Qualitative Risk Analysis
Perform Quantitative Risk Analysis
Monitor and Control Risk
The process of assessing the likelihood and impact of each identified risk is part of the Perform Qualitative Risk Analysis process. This process helps prioritize risks based on their probability and impact, allowing the project team to focus on the most significant risks. By doing so, the project manager and team can allocate resources and effort to address the risks that pose the greatest threat or opportunity to the project.
The process of assessing the likelihood and impact of each risk is part of the Perform Qualitative Risk Analysis process, which 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. This process helps the project manager and the team to focus on the high-priority risks that have the most influence on achieving the project objectives. The other processes are not relevant to the question scenario. Plan Risk Management is the process of defining how to conduct risk management activities for a project. Perform Quantitative Risk Analysis is the process of numerically analyzing the effect of identified risks on overall project objectives.Monitor and Control Risk is the process of implementing risk response plans, tracking identified risks, monitoring residual risks, identifying new risks, and evaluating risk process effectiveness throughout the project.Reference:PMI Risk Management Professional (PMI-RMP) Examination Content Outline and Specifications, page 71.A Guide to the Project Management Body of Knowledge (PMBOK Guide) -- Sixth Edition, pages 397-3982.
.
Question 40

A home solar panel project has many internal and external stakeholders including households, businesses, community groups, electric utility companies, local government officials, landlords, and investors. What should the project manager do when engaging stakeholders?
Include all stakeholders in the project's governance.
Communicate response strategies to all stakeholders.
Ignore any risks beyond stakeholders' tolerance.
Consider stakeholders' positions and opinions regarding the project's output.
The project manager should consider stakeholders' positions and opinions regarding the project's output when engaging stakeholders. This approach helps to address stakeholders' concerns, expectations, and potential objections, and it can lead to better decision-making and more successful project outcomes. It is important for the project manager to maintain open communication with stakeholders and to be responsive to their needs and perspectives.
According to the PMI Risk Management Professional (PMI-RMP) Examination Content Outline, one of the tasks under the domain of stakeholder engagement is to ''engage stakeholders by communicating with them to understand their positions and opinions regarding the project's output, and to ensure that their interests are considered in the risk management process'' (Task 1.3). This implies that the project manager should consider stakeholders' perspectives and expectations when engaging them, and not ignore, exclude, or impose on them. Therefore, option D is the correct answer.
Option A is incorrect because not all stakeholders need to be involved in the project's governance, which is the set of policies, processes, and procedures that define how the project is managed and controlled. The project's governance should be determined by the project sponsor and the project management office (PMO), and only include those stakeholders who have authority and responsibility for the project's success.
Option B is incorrect because communicating response strategies to all stakeholders is not a stakeholder engagement activity, but a risk communication activity. The project manager should communicate response strategies to the relevant stakeholders who are assigned to implement or monitor them, and not to all stakeholders indiscriminately.
Option C is incorrect because ignoring any risks beyond stakeholders' tolerance is not a stakeholder engagement activity, but a risk attitude activity. The project manager should identify and assess all risks that may affect the project's objectives, regardless of stakeholders' tolerance levels. The project manager should also consult with stakeholders to determine their risk appetite, threshold, and attitude, and use this information to prioritize and respond to risks accordingly.
Question