PMI-RMP Sample Questions Answers

In this scenario, the risk manager is considering a response that could lead to a significant residual risk—excessive additional costs due to overtime. Before proceeding, it is crucial to confirm that the project sponsor is comfortable with the risk appetite for this potential outcome. This step is essential to ensure that the decision to allow overtime aligns with the sponsor ' s tolerance for additional costs and the overall project risk management strategy. According to the Risk Management Procedure, understanding and aligning with the sponsor ' s risk appetite is a critical step before implementing risk responses that could impact the project ' s financials​. This approach ensures that all stakeholders are aware of and agree to the potential consequences of the chosen risk response strategy.

When a risk manager realizes that a project has unrealistic funding and low resources, the appropriate document to review is the Project Management Plan. The Project Management Plan includes detailed information about the project’s budget, resources, and overall strategy. By reviewing this plan, the risk manager can identify any discrepancies between the planned and actual resources and funding, allowing them to assess the associated risks and take necessary corrective actions.

PMI’s standards indicate that the Project Management Plan is the primary document that outlines how the project will be executed, monitored, and controlled, including how resources and budgets are allocated​​.

To mitigate the chance of the same issues reoccurring, the risk manager should document the known risk triggers as identified cost and schedule risks in the risk register. By doing so, these risks are formally recognized, and appropriate responses can be planned and monitored. This approach ensures that the lessons learned from the previous project are incorporated into the risk management plan for the upcoming project, reducing the likelihood of similar issues occurring.

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 executed 2. 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.

After verifying the effectiveness of the risk responses, the next step is to close out the risk response actions and communicate the results to relevant stakeholders. This ensures that the project team and stakeholders are aware of how risks have been managed and that any lessons learned can be applied to future projects. This aligns with PMI ' s emphasis on communication and documentation in risk management to ensure transparency and continuous improvement​.

In this scenario, a low-probability risk has occurred, leading to a significant project delay. To demonstrate to stakeholders that the project can still be concluded successfully, it ' s essential to identify the root cause of this unexpected event. An Ishikawa diagram, also known as a fishbone diagram or cause-and-effect diagram, is a tool that helps in identifying the various potential causes of a specific problem or effect. By systematically exploring all possible causes, the project team can pinpoint the underlying issues that led to the risk event. Understanding these root causes enables the team to implement corrective actions and preventive measures, thereby assuring stakeholders of the project ' s viability and the team ' s commitment to addressing unforeseen challenges effectively.

PMI Risk Management Study Guide References:

The PMI-RMP Exam Preparation Study Guide emphasizes the importance of root cause analysis in risk management, stating that tools like the Ishikawa diagram are instrumental in uncovering the fundamental reasons behind unexpected risk events, which is crucial for developing effective mitigation strategies.

When a potential change request arises that could impact the project, the first step should be to document it as a risk in the risk register. This ensures that the risk is formally recognized and tracked. Gathering information about the probability and impact allows the project team to assess the risk thoroughly and develop an appropriate response. This approach follows PMI’s risk management process, which emphasizes the importance of systematically identifying, documenting, and analyzing risks​.

Top of Form

Bottom of Form

When a project lacks predefined organizational process assets (OPAs) related to risk categories, the risk manager can utilize the Work Breakdown Structure (WBS) to identify potential project risk categories. The WBS decomposes the project scope into manageable components, providing a hierarchical representation of all deliverables and work packages. By analyzing each element of the WBS, the risk manager can systematically identify areas where risks may arise, effectively categorizing them based on project activities and deliverables. This approach ensures a comprehensive assessment of potential risks across all aspects of the project, facilitating targeted risk management efforts.

PMI Risk Management Study Guide References:

The PMI-RMP Exam Preparation Study Guide notes that " the WBS serves as a foundational tool for risk identification, enabling project teams to systematically examine each component for potential risks and categorize them appropriately. "

According to the PMI-RMP Exam Content Outline1, one of the domains of the PMI-RMP certification is risk monitoring and reporting. This domain includes tasks such as “monitor and report on risk metrics and trends”, “monitor the status of risk response activities and update risk register and risk report accordingly”, and “monitor and control project contingency and management reserves”. These tasks imply that the risk manager should regularly check and report on the status of risks identified according to their prioritization (B), monitor the status and oversee execution of the risk response plan for each identified risk ©, and ensure management reserves are sufficient to cover the mitigation plans for all identified risks (D). These actions will help the risk manager to ensure the risk management plan remains effective during the project timeframe. Therefore, the best answers are B, C, and D.

rences: 1: PMI-RMP Exam Content Outline, pages 9-10.

The correct answer is D. Advise the team to prioritize risks using severity, occurrence, and detection ratings.

In Failure Modes and Effects Analysis (FMEA) , risks are commonly evaluated using three core factors:

Severity : how serious the effect would be if the failure occurs,

Occurrence : how likely the failure is to happen,

Detection : how likely it is that the failure will be detected before causing impact.

These three ratings are used together to determine the relative priority of potential failure modes. That is the recognized logic of FMEA and is exactly what the risk manager should reinforce.

Why the other options are incorrect:

A. Direct the team to prioritize risks based solely on their likelihood to streamline the analysis. FMEA does not rely only on likelihood. A low-likelihood failure may still deserve high attention if the impact is severe or difficult to detect.

B. Encourage the team to focus on documenting the most severe FMEA risks and disregard others. This is incomplete and poor practice. Risks should not be disregarded simply because they are less severe; occurrence and detection also matter.

C. Emphasize technical faults within the system as the highest priority for risk response planning. FMEA is broader than technical faults alone and should evaluate all relevant failure modes systematically.

Reference-aligned basis:

This answer is consistent with standard FMEA methodology and general risk analysis practice.

The correct answer is B. Organize a stakeholder workshop to discuss the effectiveness of the new security measures.

The response has already been implemented and tested, but executives are concerned about its operational impact. This is now both a stakeholder engagement and risk monitoring issue. A workshop is the best option because it allows the risk manager to present test results, gather executive concerns, discuss trade-offs between security and operational efficiency, and determine whether further adjustments are needed.

Why the other options are incorrect:

A. Facilitate a risk identification session on security measures with the company executives. This is too narrow and steps backward. The issue is not only identification, but discussion of effectiveness and operational impact after implementation.

C. Implement additional security measures to address the concerns expressed by the executives. Adding controls immediately without analysis may worsen the operational burden.

D. Acknowledge the concerns and focus on monitoring the effectiveness of the new security measures. Monitoring is important, but this response is too passive given active executive concern. Engagement and discussion are needed.

Reference-aligned basis:

This answer is consistent with risk and stakeholder management practice that implemented responses should be reviewed with affected stakeholders to confirm effectiveness and unintended impacts.

To determine whether to purchase the new component, we can perform an Expected Monetary Value (EMV) analysis for both scenarios: purchasing the component and not purchasing it.

1. Purchasing the New Component:

Probability of Success: 70% (0.7)

Profit if Successful: US$500,000

EMV of Success: 0.7 * $500,000 = $350,000

Probability of Failure: 30% (0.3)

Additional Cost if Failed: US$50,000

EMV of Failure: 0.3 * (-$50,000) = -$15,000

Cost of Component: -$100,000

Total EMV: $350,000 (success) - $15,000 (failure) - $100,000 (cost) = $235,000

2. Not Purchasing the New Component:

Probability of Failure: 80% (0.8)

Cost if Failed: US$250,000

EMV of Failure: 0.8 * (-$250,000) = -$200,000

Probability of Success: 20% (0.2)

Profit if Successful: US$0 (assuming no additional profit without the component)

EMV of Success: 0.2 * $0 = $0

Total EMV: $0 (success) - $200,000 (failure) = -$200,000

Comparing the two scenarios, purchasing the new component yields a positive EMV of $235,000, whereas not purchasing it results in a negative EMV of -$200,000. Therefore, from a risk management perspective, it is advisable to purchase the new component.

PMI Risk Management Study Guide References:

The PMI-RMP Exam Preparation Study Guide discusses the application of Expected Monetary Value (EMV) analysis in decision-making under uncertainty, providing a structured approach to evaluate potential financial outcomes.

A risk management plan is the foundational document for risk management. It defines processes, ownership, strategies, and baselines, and must be developed first before other detailed risk actions. PMBOK® Guide specifies:

" The risk management plan is the key document that outlines the approach, processes, roles, responsibilities, and documentation requirements for risk management. "

— PMBOK® Guide, 6th Edition, Section 11.1

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 correct answer is B. Perform sensitivity analysis.

Sensitivity analysis is used to determine which individual risks or uncertainties have the greatest effect on overall project outcomes . It helps the risk manager understand which variables or risks matter most and therefore where response efforts are most critical. In this question, the risk manager wants to know which risk will have an impact on the project outcome and to assess the effectiveness of response planning by understanding impact drivers. Sensitivity analysis is the best fit for that purpose.

This technique is commonly used in quantitative risk analysis to identify which uncertainties most influence objectives such as cost, schedule, or performance. It often supports prioritization of risk responses by showing where management attention will produce the greatest benefit.

Why the other options are incorrect:

A. Perform Pareto analysis. Pareto analysis helps identify the most significant contributors among a group of causes or issues, but it is not the primary risk analysis technique used to determine which uncertainties most affect project outcomes in a structured risk context.

C. Perform contingency analysis. Contingency analysis is not the standard technique for identifying which risks most influence project outcomes. Contingency reserves may be determined from risk analysis results, but this option does not directly answer the question.

D. Perform qualitative analysis. Qualitative analysis assesses probability, impact, urgency, and other relative characteristics, but it does not specifically show how much each risk affects the final project outcome compared with others. Sensitivity analysis provides that deeper insight.

Best-practice reasoning:

When a project team needs to identify the risks with the greatest influence on outcomes, sensitivity analysis is the preferred method because it isolates the variables that drive uncertainty and highlights where response plans matter most.

Reference-aligned basis:

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

sensitivity analysis as a method to determine which risks have the greatest potential effect on project results,

use of analysis outputs to focus response planning and management attention,

support for quantitative understanding of outcome drivers.

The risk manager should have their team review the scope of work and requirements to ensure they understand the project ' s objectives and deliverables. Additionally, reviewing the risk management plan will help the team understand the risk management process, roles, and responsibilities, and prepare for the risk identification workshop.

According to the PMBOK® Guide – Sixth Edition1, the scope of work and requirements are key inputs for the risk identification process, as they define the project boundaries, deliverables, assumptions, and constraints. The risk management plan is also an essential input, as it provides the guidelines and framework for how risk management will be performed throughout the project. The other options are not relevant for risk identification, as they are either related to other processes (such as Monte Carlo analysis for quantitative risk analysis) or not directly related to the project risks (such as the list of pre-approved contractors or the organization chart for city permit department). References: PMBOK® Guide – Sixth Edition, pages 397-398.

The risk registry is a document that records the identified risks, their characteristics, their status, and their responses. It is a key input for risk management and a source of information for project stakeholders. The risk manager should review the risk registry first to understand the current state of the project risks, especially the ones related to the client’s vendor, and to evaluate the effectiveness of the risk responses implemented so far. Enhancing risk identification, reviewing the contingency reserves, and creating a risk response plan are possible actions that the risk manager may take after reviewing the risk registry, but they are not the first thing to do. References: PMI Risk Management Professional (PMI-RMP)® Exam Content Outline1, PMI Practice Standard for Project Risk Management2, Risk Management Professional (PMI-RMP)® Cert Guide3

In this scenario, the program manager is using the " Exploit " risk response strategy, which is aimed at ensuring that an opportunity is realized. By transferring all resources to the project and arranging for overtime pay, the program manager is taking proactive steps to ensure the project is completed early, thereby securing the large bonus. According to PMI, the " Exploit " strategy is used when the objective is to ensure that the opportunity is realized, typically involving actions that maximize the chances of achieving the desired outcome​.

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.

Risk handling strategies should be reviewed and revised periodically to ensure they remain effective and relevant as the project progresses. This allows the project manager to adapt to changing circumstances and minimize the impact of risks on the project.

According to the PMBOK® Guide, risk handling strategies are the specific actions that are taken to implement the risk response plan. The risk response plan is the output of the Plan Risk Responses process, which describes how the project team intends to address the identified risks. The risk handling strategies should be aligned with the risk response strategies, which are the general approaches to deal with the risks, such as avoid, transfer, mitigate, accept, exploit, share, enhance, or accept.

The project manager should work with the risk handling strategies by reviewing and revising them periodically. This is because the project risks are not static, but dynamic and uncertain. They may change over time due to various factors, such as changes in the project scope, schedule, cost, quality, resources, stakeholder expectations, assumptions, constraints, etc. Therefore, the project manager should monitor and control the risk handling strategies to ensure that they are still effective and appropriate for the current risk situation. The project manager should also update the risk register and the risk report with the results of the risk handling strategies, such as the residual risks, secondary risks, and risk triggers.

The other options are not valid for how the project manager should work with the risk handling strategies:

Implement the strategies after completing the risk analysis: This is not a valid option because the risk analysis is not the final step in the risk management process. The risk analysis is part of the Perform Qualitative Risk Analysis and Perform Quantitative Risk Analysis processes, which come after the Identify Risks process and before the Plan Risk Responses process. The risk analysis helps the project manager to prioritize and evaluate the risks, but it does not provide the specific actions to address them. The risk handling strategies are developed in the Plan Risk Responses process, which comes after the risk analysis.

Implement the strategies immediately: This is not a valid option because the risk handling strategies should not be implemented without proper planning and approval. The risk handling strategies should be documented in the risk response plan, which should be communicated and approved by the project sponsor, customer, and other relevant stakeholders. The risk handling strategies should also be integrated with the other project management plans, such as the scope, schedule, cost, quality, resource, communication, procurement, and stakeholder management plans. The risk handling strategies should be implemented only when the risk triggers or conditions occur, or when the project manager decides to do so based on the risk analysis and evaluation.

Ensure the strategies are approved by the stakeholders: This is not a valid option because the approval of the risk handling strategies is not the only thing that the project manager should do with them. The approval of the risk handling strategies is part of the Plan Risk Responses process, which comes before the Implement Risk Responses and Monitor Risks processes. The project manager should also implement, monitor, and control the risk handling strategies to ensure that they are effective and appropriate for the current risk situation.

PMBOK® Guide1, Risk Management Professional (PMI-RMP)® Cert Guide1

With 25 identified risks, and considering the constraints and resources available, the appropriate next step is to perform a qualitative risk analysis. This process helps prioritize the risks based on their probability and impact, as well as other relevant factors like urgency, proximity, and detectability. By doing so, the team can focus on the most significant risks that require immediate attention and develop response plans accordingly, optimizing the use of available resources. PMI recommends this approach to ensure that risk management efforts are both efficient and effective in addressing the most critical risks first​.

 According to the PMBOK Guide, one of the tools and techniques for the plan risk management process is ground rules. Ground rules are the rules of conduct or behavior that are established by the project team and other stakeholders to ensure a productive and respectful environment for risk management activities. Ground rules can cover various aspects of risk management, such as roles and responsibilities, communication protocols, decision-making processes, meeting agendas, and conflict resolution methods1. By referring to the team’s ground rules on how to resolve conflicts, the risk manager can handle the situation where two key external stakeholders are overemphasizing the impact of a few project risks. This can help the risk manager to maintain a constructive and collaborative atmosphere in the risk reassessment workshop, as well as to ensure that the risk analysis and prioritization are based on objective and consistent criteria.

Some of the other options are not relevant or appropriate for the question scenario:

Requesting for a skilled facilitator to help resolve conflicts that have arisen is not a feasible or effective option, as it would interrupt the flow of the risk reassessment workshop and delay the risk management process. The risk manager should be able to facilitate the workshop and handle conflicts by themselves, using the tools and techniques that they have planned and agreed upon with the project team and stakeholders.

Running a sensitivity analysis to check which risks have the most impact is a technique for the perform quantitative risk analysis process, which is not applicable in the context of a risk reassessment workshop. A sensitivity analysis is a quantitative method that examines the effect of varying one risk parameter at a time on the project objectives, such as cost or schedule. It is not a tool for resolving conflicts or validating the impact of risks, as it does not consider the interrelationships and dependencies among risks or the probability of risk occurrence1.

Using the assumption analysis technique to validate the assumptions is a technique for the identify risks process, which is not suitable for the situation where conflicts have already arisen in the risk reassessment workshop. An assumption analysis is a technique that explores the validity of the assumptions that are made during the project planning and risk management processes. It is not a tool for resolving conflicts or verifying the impact of risks, as it does not address the root causes or the consequences of the disagreements among the stakeholders1.

PMBOK Guide, 6th edition, pages 407-408, 431-432, 437-438, 441-4421; PMI-RMP Exam Content Outline, 2015, pages 7-8.

When the project team is unsure if a potential change in regulations will affect the project positively or negatively, a SWOT analysis is an appropriate tool to use. SWOT analysis helps the team assess the internal and external factors that might influence the project ' s outcome. It allows the team to evaluate the strengths, weaknesses, opportunities, and threats associated with the regulatory changes, helping them determine whether the impact will be beneficial or detrimental to the project.

An Ishikawa diagram (also known as a fishbone or cause-and-effect diagram) is a tool used to identify and analyze the root causes and sources of a risk. It helps the risk manager gain a deeper understanding of the risk source and likelihood. (Reference: PMBOK Guide, 6th Edition, p. 139)

 An Ishikawa diagram, also known as a fishbone diagram or a cause-and-effect diagram, is a tool that can help the risk manager to analyze the root causes of a risk and to identify the factors that influence its occurrence and impact. An Ishikawa diagram can also help to visualize the relationships among different causes and to prioritize the most significant ones. By developing and employing an Ishikawa diagram, the risk manager can gain a deeper understanding of the source and likelihood of the risk and plan appropriate responses accordingly. References: The Standard for Risk Management in Portfolios, Programs, and Projects, page 72; PMBOK Guide, 6th edition, page 398.

 According to the PMBOK Guide, 6th edition, Section 11.2.1.2, Assumptions Log, an assumption is a factor that is considered to be true, real, or certain without proof or demonstration. Assumptions can affect the project planning and execution, and should be identified, documented, validated, and updated throughout the project life cycle. The assumptions log is an output of the Identify Risks process, and it records the project assumptions and their potential impact, validity, and priority. If the assumptions are found to be invalid or inaccurate, they may introduce new risks or change the existing risk exposure. Therefore, the project manager should update the assumptions log and assess the risk associated with the conflicting infrastructure pieces, and plan appropriate risk responses if needed. References: PMBOK Guide, 6th edition, Section 11.2.1.2, Assumptions Log

When conflicting infrastructure pieces are identified, the project manager should update the assumptions log to reflect the new information and assess the risks associated with the conflicting pieces. This allows the project manager to make informed decisions about how to address potential issues and avoid future problems. (Reference: Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Section 11.3)

The risk manager should work with the project team to reassess the external environment and identify any new or emerging risks created by the regulatory changes.

Risk monitoring is a continuous activity. It includes tracking identified risks, reviewing existing risk exposure, identifying new risks, detecting changes in the internal or external environment, evaluating the effectiveness of risk responses, and updating project risk information.

A significant regulatory change may create new compliance, legal, technical, cost, schedule, operational, or reputational risks. Before selecting a response, adding resources, or changing the project schedule, the project team should identify and analyze the new risks.

The reassessment should consider:

• The nature and effective date of the regulatory change.

• Whether the new requirement applies to the project.

• The probability and impact of noncompliance.

• Potential effects on scope, schedule, cost, quality, security, and operations.

• Required legal, regulatory, or technical expertise.

• Whether the risk exceeds established project thresholds.

• Whether the risk should be escalated to program, portfolio, or organizational management.

Option A is not the best answer because the regulatory change may affect the entire project rather than only the operational environment. The operations team may provide input, but the reassessment should involve the project team and relevant subject-matter experts.

Option B is incorrect because requesting additional resources before completing risk identification and analysis is premature.

Option C is incorrect because accelerating project completion without understanding the regulatory requirements may increase cost, quality, safety, security, or compliance exposure.

Option D is correct because reassessing the environment for new risks is the appropriate next step in continuous risk monitoring.

When there is confusion among risk action owners about when to initiate risk responses, it suggests that the risk thresholds and triggers may not be well-defined or understood. Revisiting and clarifying these thresholds and triggers can help ensure that everyone involved understands the specific conditions under which a risk response should be initiated. This will reduce confusion and ensure that risk responses are executed consistently and appropriately.

PMI’s risk management practices emphasize the importance of clearly defined risk thresholds and triggers to guide the timely and effective implementation of risk responses​​.

The project manager should apply an iterative approach to risk identification, which involves continuous risk identification throughout the project lifecycle. This will help to identify and address new risks that may arise during the project.

According to the PMBOK® Guide, risk identification is the process of determining which risks may affect the project and documenting their characteristics. It is an iterative process because new risks may evolve or become known only as the project progresses through its life cycle. There are many techniques available for risk identification and assessment, such as brainstorming, interviews, checklists, SWOT analysis, cause and effect diagrams, etc. The project manager should apply an iterative approach to risk identification to ensure that all relevant risks are captured and updated throughout the project. The project manager should also involve the project team and other stakeholders in the risk identification process to obtain their input and perspectives.

The other options are not valid for the next step after explaining the importance of risk management to the team:

Review assumptions and constraints around risks: This is a technique for risk identification, but it is not the only one. The project manager should use a combination of techniques to identify risks, not just focus on one aspect. Also, reviewing assumptions and constraints is not the same as applying an iterative approach, which implies repeating the risk identification process at regular intervals or when changes occur.

Develop the risk response plans for identified risks: This is a step in the Plan Risk Responses process, which comes after the Perform Qualitative Risk Analysis and Perform Quantitative Risk Analysis processes. The project manager should not develop the risk response plans before identifying and analyzing the risks.

Determine the likelihood and impact of the risks: This is a step in the Perform Qualitative Risk Analysis process, which comes after the Identify Risks process. The project manager should not determine the likelihood and impact of the risks before identifying them.

PMBOK® Guide1, Risk Management Professional (PMI-RMP)® Cert Guide

The expected outcome of developing the risk management plan is to define how risk management activities will be executed throughout the project. This includes the processes, tools, and techniques that will be used to identify, assess, and manage risks.

 The risk management plan is a document that describes how risk management activities will be structured and performed throughout the project. It provides guidance on how to identify, analyze, respond, monitor, and control risks, as well as how to communicate, document, and report them. The risk management plan also defines the roles and responsibilities of the project team and stakeholders in risk management, the risk categories and breakdown structure, the risk thresholds and appetite, the risk management tools and techniques, and the risk management budget and schedule. The risk management plan is an output of the plan risk management process, which is the first process in the project risk management knowledge area. Developing the risk management plan is essential for ensuring that the project risks are closely managed and aligned with the project objectives and stakeholder expectations. References: PMI, Project Risk Management, 2nd edition, 2019, p. 67-681

The risk manager is performing a qualitative risk analysis by prioritizing risks based on their probability of occurrence. Qualitative risk analysis involves evaluating and prioritizing risks based on their likelihood and impact using a predefined scale. This approach helps in determining which risks require more attention and should be subjected to further analysis or immediate action.

PMI defines qualitative risk analysis as a process that uses a relative scale to assess the probability and impact of risks, which is what is being done in this scenario​​.

The project manager should first gather more information about the previous project ' s issues by interviewing the other project manager. This will help in understanding the root causes of the delay and how to prevent similar issues in the current project before taking further action.

 The project manager should first include the risk of delay in delivery of the GTG in the risk register and communicate with the stakeholders about the potential impact and response strategies. This is part of the risk identification process, which is the first step in risk management. The risk register is a document that records the identified risks, their causes, effects, probabilities, impacts, and response plans. The project manager should communicate with the stakeholders to ensure that they are aware of the risk and its implications, and to obtain their feedback and support. The project manager should also update the risk register as new information becomes available or as the risk status changes. The other options are not the first actions that the project manager should take. Communicating with the client to provide the previous shutdown plan is part of the risk response process, which comes after the risk identification and analysis processes. Reviewing and updating the project schedule is part of the schedule management process, which is not directly related to risk management. Interviewing the other project manager to learn more details is a technique that can be used to identify risks, but it is not the first action that the project manager should take. The project manager should first document the risk in the risk register and communicate with the stakeholders before seeking more information from other sources. References: 3, 4, 5

According to the PMBOK Guide, the risk owner is the person assigned the responsibility of monitoring the risk and implementing the risk response plan. The risk owner should be involved in the risk response execution and evaluation, and should communicate the results and outcomes to the relevant stakeholders. In the case of a data breach, the risk owner should coordinate a response with the risk manager and other parties involved, such as the security team, the legal team, the customer service team, and the senior management. The risk owner should also report the status of the risk and the effectiveness of the response plan to the risk manager. The risk manager should oversee the risk response process and ensure that the risk is handled appropriately and in alignment with the project objectives and stakeholder expectations. References: = PMBOK Guide, 6th edition, pages 452-453; The Standard for Risk Management in Portfolios, Programs, and Projects, page 79.

The best practice is to log the risk and the associated response strategies in the risk register to ensure it is monitored, analyzed, and managed throughout the project. The PMBOK® Guide states:

" All identified risks and their planned responses should be recorded in the risk register to facilitate ongoing monitoring and management. "

— PMBOK® Guide, 6th Edition, Section 11.2.3.1

Ignoring or treating these as mere assumptions could result in unmanaged risks and potential project failure.

Comprehensive and Detailed In-Depth Explanation:

When there is confusion among stakeholders regarding agile concepts, the best course of action is to provide training to ensure all stakeholders have a common understanding of agile principles and terminology.

Option A: Organize training sessions to create awareness around the agile values for stakeholders (Correct Answer).

Training sessions help bridge knowledge gaps by ensuring that stakeholders understand agile principles, frameworks (Scrum, Kanban, XP), and terminology.

The PMI-RMP Guide highlights that effective stakeholder engagement requires education and alignment on risk management strategies, which applies here as well (PMI Risk Management in Portfolios, Programs, and Projects – A Practice Guide, 2022, p. 78).

Educating stakeholders reduces resistance to change and promotes informed decision-making.

PMI’s Agile Practice Guide emphasizes that “a shared understanding of agile principles across all levels of an organization increases agility and reduces friction during decision-making” (PMI & Agile Alliance, 2017, p. 44).

Option B: Facilitate a face-to-face discussion and have stakeholders agree to shift to agile for future projects (Incorrect).

Forcing a decision before stakeholders fully understand agile methodologies could lead to resistance and ineffective implementation.

The decision should be based on business needs rather than prematurely committing to agile.

Option C: Recommend an external facilitator as no one in the organization is able to eliminate this roadblock (Incorrect).

While an external facilitator can help in some situations, the Scrum Master is already responsible for coaching the organization on Scrum and Agile methodologies (Scrum Guide, 2020).

The Scrum Master should take the lead in educating stakeholders before escalating the issue externally.

Option D: Allow stakeholders to discuss without the Scrum Master’s intervention (Incorrect).

Without proper guidance, discussions could lead to further misinterpretations and delays.

The Scrum Master is responsible for educating and guiding stakeholders in understanding agile (Scrum Guide, 2020).

Final Verdict:

The correct answer is A (Organize training sessions to create awareness around agile values for stakeholders) because training ensures a common understanding, reduces resistance, and promotes effective decision-making.

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

According to the PMI Risk Management Professional (PMI-RMP)® Examination Content Outline1, a secondary risk is a risk that arises as a direct result of implementing a risk response to a specific risk. In this case, the risk response is to contract an external vendor to provide additional capacity and expertise to the project team. The secondary risk is the confidentiality risk that the contracts department has identified. The risk manager should assess the secondary risk to determine its probability, impact, and priority, and to plan appropriate responses. This is part of the Perform Qualitative Risk Analysis and Plan Risk Responses processes in the PMBOK® Guide2. References: 1: PMI Risk Management Professional (PMI-RMP)® Examination Content Outline 2: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition

The risk manager should review the agreed-upon risk tolerance to determine the correct limit for continuing construction based on the chance of rain. Risk tolerance is the level of risk an organization is willing to accept and should be established during the risk management planning process.

 Risk tolerance is the degree of uncertainty that a stakeholder is willing to accept in respect to a negative outcome on a project objective. Risk tolerance can be expressed as a percentage, a range, a value, or a qualitative statement. Risk tolerance should be agreed upon by the project team and the stakeholders at the beginning of the project, and documented in the risk management plan. The risk manager should review the agreed-upon risk tolerance to find out the correct limit for the rain probability that would affect the construction activity. This would help to resolve the conflicting opinions of the stakeholders and ensure that the risk management decisions are aligned with the project objectives and expectations. Reviewing the agreed-upon risk tolerance is the best option among the choices given, as it is the most relevant and reliable source of information for the risk manager. Performing a sensitivity analysis, finding out the stakeholders’ risk appetite, or using industry standard risk thresholds are not as effective or appropriate ways of finding out the correct limit, as they do not reflect the specific agreement and context of the project. References: PMI-RMP® Certification Handbook1, page 9; PMBOK® Guide, pages 414-415.

 Enterprise environmental factors (EEFs) are conditions or circumstances that are not under the control of the project team, but may influence, constrain, or direct the project. EEFs include internal and external factors, such as organizational culture, market conditions, industry standards, government regulations, and academic research. In this case, the project manager should find the information about the new material from the research journal published by the local university, which is an example of an external EEF. This information may help the project manager to identify and analyze the risks associated with the new material and plan appropriate risk responses. Industrial studies, commercial risk databases, and organizational process assets (OPAs) are not the correct choices, as they are not relevant to the question. Industrial studies are systematic investigations of a specific industry or sector, which may provide general information about the market trends, opportunities, and challenges, but not specific information about the new material. Commercial risk databases are sources of information about historical or potential risks that may affect projects in different domains or regions, which may help the project manager to identify common or emerging risks, but not the risks related to the new material. OPAs are the plans, processes, policies, procedures, and knowledge bases specific to and used by the performing organization, which may help the project manager to follow the established guidelines and practices for risk management, but not to obtain new information about the new material. References: PMI. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Chapter 2: The Environment in Which Projects Operate, pp. 38-39. 5

Enterprise environmental factors (EEFs) include information from external sources, such as academic research, industry studies, and market conditions. this case, the project manager should refer to the research journal published by the local university as an EEF to gather information about the new material and its associated risks.

The correct answer is D. Update the project stakeholders and seek their input on the resulting secondary risk.

This question describes a secondary risk , which is a new risk that arises as a direct result of implementing a risk response. The original equipment-failure risk was successfully mitigated, but the use of alternative machinery introduced another issue. In standard risk management practice, once a secondary risk is identified, it must be documented, assessed, communicated, and managed through the normal risk process. Because this new risk can affect project objectives and may require additional response planning, relevant stakeholders should be informed and involved in determining the best course of action.

Option D is the best answer because secondary risks should not be ignored or delayed unnecessarily. Stakeholder input is important to evaluate the impact of the new issue, determine acceptable response options, and align decisions with project priorities and risk thresholds.

Why the other options are incorrect:

A. Assign a risk owner and develop the risk mitigations at the next scheduled risk meeting. Assigning an owner and planning mitigation are valid activities, but waiting until the next scheduled meeting may delay needed action. The question asks what the risk manager should do now after identifying the secondary risk. Immediate stakeholder communication is more appropriate.

B. Continue with the project as the risk identified is inconsequential. The scenario does not support the conclusion that the secondary risk is insignificant. Assuming it is inconsequential without analysis would be poor risk practice.

C. Assign risk responsibility to the project manager to determine how to proceed. Risk responsibility should be assigned to the most appropriate owner, not automatically to the project manager. Also, the correct first step is broader communication and engagement around the newly emerged secondary risk.

Best-practice reasoning:

Secondary risks are a recognized output of risk response actions. They should be captured and processed like any other identified risk. Transparent stakeholder communication is especially important when a response action creates new uncertainty.

Reference-aligned basis:

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

risk responses can generate secondary risks,

newly identified risks should be communicated and assessed,

stakeholders should be engaged when new risks emerge from implemented responses.

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.

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

The correct answer is C. Highlight to the stakeholders the agreed predetermined frequency of risk reports.

The problem in this scenario is excessive and disruptive stakeholder requests for information. The major investor is bypassing the normal reporting structure, causing the team to spend a large portion of its time preparing repeated reports. In sound stakeholder and risk communication management, reporting expectations should be defined in advance, including what will be reported, how often, in what format, and to whom . The risk manager should reinforce the agreed reporting cadence and communication approach so that stakeholder information needs are met without creating unnecessary disruption to project execution.

Option C is the best answer because it directly addresses the root issue: the reporting process is either not being followed or not being reinforced. By reminding stakeholders of the agreed frequency and structure of risk reports, the risk manager helps restore efficient communication and protect team productivity.

Why the other options are incorrect:

A. Talk to the project team and ensure they avoid direct communication with this stakeholder. This is too extreme and could damage stakeholder relationships. Stakeholders should not be blocked from communication; communication should be managed appropriately.

B. Engage with the team to enhance the project risk reports sent to the stakeholders. Improving reports may help somewhat, but it does not directly solve the issue of repeated ad hoc requests consuming team time. The more important action is to enforce the agreed communication process.

D. Work with the project sponsor to ensure stakeholders avoid directly influencing the project team. Sponsor support may be helpful in some cases, but this option is broader and more confrontational than necessary. The first and most appropriate step is to use the agreed reporting framework.

Best-practice reasoning:

Stakeholder engagement requires balancing transparency with controlled communication channels. A predefined reporting frequency helps ensure that stakeholders receive needed information while preventing reporting overload and operational inefficiency.

Reference-aligned basis:

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

planned communication and reporting frequencies,

managing stakeholder expectations through agreed information channels,

reducing disruption by using structured communication plans.

In qualitative risk analysis, in addition to probability and impact, other factors can be used to refine the risk prioritization. Three valid factors to consider are:

1. Urgency: This refers to the timeframe within which a risk is likely to occur or the speed at which it might impact the project. High urgency risks require quicker responses, making them more critical in prioritization.

2. Proximity: This factor considers the time until the risk might affect the project. Risks that are likely to occur sooner may be given higher priority because they may require immediate attention.

3. Detectability: This assesses how easily the presence or impact of a risk can be identified. Risks that are hard to detect might be more dangerous and may require more resources to monitor and manage.

These factors are mentioned in PMI ' s guidelines for qualitative risk analysis as they provide a more nuanced view of risks beyond just probability and impact, allowing for more targeted and effective risk management strategies​.

Risk urgency refers to the timeframe within which a risk might occur and necessitates prioritization based on how soon a response is required. When team members express concerns about a lack of time prioritization for an identified risk, they are highlighting the need to assess and address the risk ' s urgency. Evaluating risk urgency involves determining the proximity of the risk event and ensuring that timely actions are planned to mitigate or respond to the risk appropriately. Incorporating urgency assessments into the risk management process helps in allocating resources and attention to risks that require immediate action, thereby enhancing the project ' s resilience against potential threats.

PMI Risk Management Study Guide References:

The PMI-RMP Exam Preparation Study Guide discusses the concept of risk urgency, noting that " understanding the timing of potential risk events is crucial for effective prioritization and response planning. "

In this instance, the project manager should use quantitative analysis to simulate the overall risk outcome. Quantitative analysis techniques, such as Monte Carlo simul-ation or decision tree analysis, can be used to model the combined effect of individual risks on project objectives. By leveraging historical data, the project manager can generate more accurate and reliable risk assessments, which can help inform risk response strategies and improve project decision-making.

Quantitative analysis is a type of risk analysis that numerically analyzes the effect of identified risks on overall project objectives 1. It involves using historical data and other information to estimate the probability and impact of risks, and then applying mathematical techniques such as simul-ation, sensitivity analysis, decision tree analysis, or expected monetary value analysis to quantify the overall risk exposure of the project 2. Quantitative analysis can provide more accurate and objective results than qualitative analysis, which relies on subjective judgments and ratings. Quantitative analysis can also help the project manager prioritize risks, determine the optimal risk response strategy, and allocate contingency reserves 3. Therefore, the correct answer is D.

The risk manager should choose to exploit opportunities, as this response aims to maximize the positive effects of opportunities, which can help recover the project ' s contingency reserve and profit margin.

Exploit is a positive risk response strategy that aims to ensure that the opportunity is realized 1. It involves eliminating the uncertainty associated with a particular upside risk and making it happen 2. For example, if there is an opportunity to reduce the project cost by using a cheaper supplier, the project manager can exploit it by signing a contract with the supplier and securing the savings. Exploit is the opposite of avoid, which is a negative risk response strategy that seeks to eliminate the threat or protect the project from its impact 2.

The other options are not appropriate for taking full advantage of opportunities. Mitigate is a negative risk response strategy that reduces the probability and/or impact of a threat 2. It is the opposite of enhance, which is a positive risk response strategy that increases the probability and/or impact of an opportunity 1. Accept is a risk response strategy that involves acknowledging the risk and not taking any action unless the risk occurs 2. It can be applied to both threats and opportunities, but it does not actively pursue them. Transfer is a negative risk response strategy that shifts the impact of a threat to a third party, along with ownership of the response 2. It is the opposite of share, which is a positive risk response strategy that allocates ownership of an opportunity to a third party who is best able to capture it for the benefit of the project 1.

The team is documenting all the checkpoints along the way that might indicate delays on critical deliverables, which is an example of risk triggers. Risk triggers are events or conditions that indicate a risk may be about to occur or has already occurred, helping the project team to monitor and respond to risks effectively.

 Risk triggers are indicators or warning signs that a risk event is about to occur or has occurred. They help to monitor the status of risks and initiate risk responses when needed. Documenting risk triggers is part of the Plan Risk Responses process, which aims to develop options and actions to enhance opportunities and reduce threats to project objectives. References: The Standard for Risk Management in Portfolios, Programs, and Projects, page 78; PMBOK Guide, 6th edition, page 402.

When a project experiences consistent deviations in cost performance index (CPI) and schedule performance index (SPI), it indicates underlying issues with the project ' s assumptions regarding schedule and resources. Analyzing these assumptions helps identify discrepancies between planned and actual performance, such as underestimated task durations or insufficient resource allocation. By revisiting and adjusting these assumptions, the risk manager can develop strategies to mitigate further overruns and align the project with its objectives.

PMI Risk Management Study Guide References:

The PMI-RMP Exam Content Outline emphasizes the importance of examining assumption and constraint analyses to identify risks arising from inaccurate or incomplete project assumptions, which can lead to performance issues.

When closing risks as part of the closing process, it is important to update the lessons learned document. This document captures the knowledge and experience gained during the project and can be valuable for future projects.

 Lessons learned is a document that captures the knowledge gained from the project and can help improve the performance of future projects. It is one of the outputs of the project closure process and should include information on the project risks, issues, and responses. Lessons learned can help identify the best practices and lessons to be applied or avoided in similar projects. Updating the lessons learned document is an important part of closing the risks as it can provide valuable insights for risk management. References: PMI, Project Risk Management, 2nd edition, 2019, p. 97-981

A risk trigger is a specific event or condition that signals that a risk is about to occur or has occurred. PMBOK® Guide clarifies:

" Risk triggers (sometimes called warning signs) are indicators or symptoms that a risk event is about to occur. The risk register should include identified triggers for each risk. "

— PMBOK® Guide, 6th Edition, Section 11.2.3.1

Thus, documenting the specific event or condition (such as the supplier missing a delivery deadline) is the correct approach.

Risk identification should be an ongoing process throughout the project lifecycle. Encouraging project team members to proactively identify risks allows for continuous risk management and the development of appropriate response strategies as new risks emerge.

According to the PMI Risk Management Professional (PMI-RMP)® Examination Content Outline1, one of the tasks in the domain of Risk Identification is to ensure that project team members proactively identify risks throughout the project life cycle, using various tools and techniques, to enable planning for possible risk response strategies1. Risk identification is an iterative process that should be performed regularly and frequently throughout the project, as new risks may emerge or existing risks may change due to internal or external factors2. The project manager should involve the project team members and other relevant stakeholders in the risk identification process, as they may have different perspectives, expertise, and insights on the project risks3. The project manager should not identify risks only at the project’s midpoint for the stakeholders to review them, because that would be too late and ineffective to manage the risks that may have already occurred or escalated4. The project manager should not identify risks at the beginning of the project because the risk posture will not change, because that would be unrealistic and imprudent to assume that the project environment and conditions will remain static and predictable5. The project manager should not delegate risk identification to each team member and have them record the risks on separate risk registers for their areas, because that would create inconsistency, duplication, and fragmentation of the risk information, and prevent a holistic and integrated view of the project risks. References: 1: PMI Risk Management Professional (PMI-RMP)® Examination Content Outline, page 82: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 3983: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 3994: Risk Identification: When and How Often to Do It During the Project Life Cycle5: Risk Management: Why Is It Important?. : Risk Register in Project Management - Project Management Academy.

If a risk still leaves substantial residual risk after implementing the mitigation strategy, the risk manager should revisit the risk register and redefine the mitigation strategy to reduce the residual risk to an acceptable level.

According to the PMBOK Guide, 6th edition, Chapter 11: Project Risk Management1, an effect of adding the correlation to the Monte Carlo schedule risk analysis model is that it increases the standard deviation of the model. This is because:

Correlation is the statistical relationship between two or more variables. In a schedule risk analysis, correlation can be used to model the dependency between the durations of different activities. For example, if two activities are positively correlated, it means that if one activity takes longer than expected, the other activity is also likely to take longer than expected. Conversely, if two activities are negatively correlated, it means that if one activity takes longer than expected, the other activity is likely to take shorter than expected.

A Monte Carlo schedule risk analysis is a simul-ation technique that uses random values for uncertain variables, such as activity durations, to generate possible outcomes for the project schedule. The simul-ation is repeated many times to produce a probability distribution of the project completion date and duration. The standard deviation is a measure of the variability or dispersion of the distribution. A higher standard deviation means that the distribution is more spread out and less predictable.

Adding correlation to the Monte Carlo schedule risk analysis model increases the standard deviation of the model because it introduces more variability and uncertainty to the simul-ation. Correlated activities can have a cumulative effect on the project schedule, either positively or negatively, depending on the direction and strength of the correlation. This can result in more extreme outcomes for the project completion date and duration, which increase the spread of the distribution and the standard deviation.

PMBOK Guide, 6th edition, Chapter 11: Project Risk Management1

Risk Management Professional (PMI-RMP)® Exam Cert Guide2

A risk owner is the person assigned to manage, monitor, and report on a specific risk. When the IT manager has unique insight or control over risks associated with IT infrastructure, they should be formally assigned as a risk owner for those risks. The PMBOK® Guide emphasizes:

“Risk owners are identified during the risk management planning process and should be engaged in relevant meetings and risk discussions. Assigning the IT manager as a risk owner ensures proper accountability for IT-related risks.”

— PMBOK® Guide, 6th Edition, Section 11.3.2.1 (Risk Register: Risk Owner)

This promotes ownership, accountability, and effective risk management.

The risk manager should perform a quantitative risk analysis to determine the potential impact of risks on the project ' s completion date. This will help in providing a more accurate project completion date to the customer, considering the risks and their potential effects on the project schedule.

 According to the PMI Risk Management Professional (PMI-RMP)® Examination Content Outline1, one of the tasks in the domain of Risk Analysis is to perform quantitative risk analysis using techniques such as Monte Carlo simul-ation, decision tree analysis, sensitivity analysis, etc., to quantify the possible outcomes for the project and their probabilities, and to evaluate the cost and schedule impacts of risks1. In this scenario, the risk manager should perform a quantitative risk analysis and update the results, because the project costs have increased significantly and the customer has imposed a strict deadline for the project completion. A quantitative risk analysis will help the risk manager to estimate the probability of meeting the project objectives, such as cost and schedule, and to determine the appropriate contingency reserves for the project. A quantitative risk analysis will also provide more accurate and reliable information for the customer and the project team, and will support the risk response planning process2. References: 1: PMI Risk Management Professional (PMI-RMP)® Examination Content Outline, page 92: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, pages 431-432.

According to the PMBOK Guide, risk prioritization is the process of assigning a level of importance to each identified risk based on its probability and impact, as well as other factors such as urgency, stakeholder tolerance, and project objectives. Risk prioritization helps the project team to focus on the most significant risks and allocate resources accordingly. One of the tools and techniques for risk prioritization is stakeholder engagement, which involves involving the key stakeholders in the risk analysis and decision making process. Stakeholder engagement helps to ensure that the risk prioritization reflects the expectations and preferences of the stakeholders, and that they are aware of and agree with the results. By engaging the key stakeholders during the prioritization process, the risk manager could have avoided the board’s request to sort the risks differently, as the board would have been part of the process and would have accepted the outcome. References: = PMBOK Guide, 6th edition, pages 406-407; The Standard for Risk Management in Portfolios, Programs, and Projects, page 67.

A company manages confidential customer information, and a data breach exposing sensitive information was discovered. What should the risk manager do?

A. Execute the security risks contingency plan.

B. Get a report of customers affected by the risk.

C. Identify residual and secondary risks.

D. Coordinate a response with the risk owner.

Answer: D

According to the PMBOK Guide, the risk owner is the person assigned the responsibility of monitoring the risk and implementing the risk response plan. The risk owner should be involved in the risk response execution and evaluation, and should communicate the results and outcomes to the relevant stakeholders. In the case of a data breach, the risk owner should coordinate a response with the risk manager and other parties involved, such as the security team, the legal team, the customer service team, and the senior management. The risk owner should also report the status of the risk and the effectiveness of the response plan to the risk manager. The risk manager should oversee the risk response process and ensure that the risk is handled appropriately and in alignment with the project objectives and stakeholder expectations. References: = PMBOK Guide, 6th edition, pages 452-453; The Standard for Risk Management in Portfolios, Programs, and Projects, page 79.

The stakeholders should prepare a risk-adjusted backlog when making decisions on how to respond to known and new risks. A risk-adjusted backlog helps prioritize work items based on their risk level and potential impact on the project.

 A risk-adjusted backlog is an artifact that reflects the prioritization of the product backlog items based on their risk exposure. It is used to plan for the execution phase of an agile project, where the stakeholders can decide how to respond to known and new risks by selecting the most valuable and least risky items to deliver. A risk-adjusted backlog can help the stakeholders to optimize the value delivery and reduce the uncertainty of the project outcomes. References: PMI, The Standard for Risk Management in Portfolios, Programs, and Projects, 2019, p. 113; PMI, Agile Practice Guide, 2017, p. 54.

Since the project manager cannot avoid, transfer, or mitigate the risk, the only remaining option is to accept the risk and develop a contingency plan to handle it if it occurs.

According to the PMI-RMP Exam Content Outline1, one of the tools and techniques for risk response planning is risk response strategies. These are the actions that the project manager and the project team take to address the identified risks, either positive or negative. For negative risks or threats, the PMI-RMP Exam Content Outline1 lists four possible strategies: avoid, transfer, mitigate, and accept.

Avoid risk means changing the project plan to eliminate the threat or its impact2. For example, changing the scope, schedule, or budget to avoid a risk.

Transfer risk means shifting the impact of a threat to a third party, such as a contractor, vendor, or insurer2. For example, buying insurance, outsourcing, or using performance bonds to transfer a risk.

Mitigate risk means reducing the probability and/or impact of a threat2. For example, conducting more tests, adopting best practices, or providing training to mitigate a risk.

Accept risk means acknowledging the existence of a threat and being willing to deal with its consequences2. For example, doing nothing, establishing a contingency reserve, or developing a contingency plan to accept a risk.

In this question, the project manager has determined that they cannot outsource work (transfer) nor eliminate the scope (avoid). They also discover that they cannot buy insurance (transfer) or mitigate the risk. Therefore, the only remaining option is to accept the risk. Accepting the risk does not mean ignoring the risk, but rather recognizing it and preparing for its potential occurrence and impact. Therefore, the best answer is D.

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

According to the PMBOK® Guide1, the risk management plan is a component of the project management plan that describes how risk management activities will be structured and performed. It provides guidance on how the project team will identify, analyze, respond, monitor, and control risks throughout the project life cycle. The risk management plan should be reviewed and updated whenever there are changes in the project scope, schedule, budget, or objectives, as these changes may introduce new risks or affect the existing ones. In this case, the organization’s decision to accelerate a key project is a significant change that may alter the risk profile of the project. Therefore, the first action for the project risk manager to take is to revise the risk management plan to reflect the new situation and ensure that the risk management processes are aligned with the project objectives and constraints. This is part of the Plan Risk Management process in the PMBOK® Guide1. References: 1: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition

When managing risks in a project that spans multiple regions with varying degrees of risk appetite, it is essential to align the project ' s risk thresholds with the organization ' s overall risk appetite. This approach ensures consistency across all regions and projects, particularly in multinational organizations where varying regional practices and risk appetites could create discrepancies. By aligning with the organizational risk appetite, the project team ensures that the risk management process adheres to the strategic objectives and governance framework set by the organization. This alignment also helps in managing stakeholder expectations and ensuring that the project remains within acceptable risk parameters set by the organization as a whole, as emphasized in the Risk Management Policy​.

If client ' s experts express discomfort with some activities at a critical stage, the first step for the risk manager is to conduct a risk assessment process for that stage. This assessment will help identify the specific risks associated with the activities in question, evaluate their potential impact, and develop appropriate mitigation strategies. This ensures that the project plan is robust and that all stakeholders are confident in its execution​.

The correct answer is D. Use a qualitative or quantitative analysis to analyze identified risks.

An influence diagram is useful for showing relationships among decisions, uncertainties, and outcomes, but it is not usually sufficient by itself for a complete risk analysis on a critical and complex project. Once risks are identified and their relationships are understood, the risk manager should perform qualitative and, where needed, quantitative analysis to assess probability, impact, priority, and potential effect on project objectives.

This makes option D the best answer because it directly strengthens the depth and rigor of the project’s risk analysis. Qualitative analysis helps prioritize risks based on relative importance, while quantitative analysis can estimate numeric effects on cost, schedule, or performance for the most significant risks.

Why the other options are incorrect:

A. Use brainstorming to identify more possible risks. Brainstorming is mainly a risk identification technique, not the best answer for improving the quality of analysis after risks and relationships are already being examined.

B. Use a Monte Carlo simulation to identify risks. Monte Carlo simulation is not used to identify risks. It is a quantitative analysis technique used after risks and uncertainty inputs have already been identified.

C. Use a work breakdown structure (WBS) to help analyze risks. A WBS can help organize project work and may support identification by revealing areas of uncertainty, but it is not the strongest answer for enhancing the actual quality of risk analysis.

Best-practice reasoning:

For important and complex projects, risk analysis should move beyond simple diagramming techniques and include formal qualitative and quantitative methods. This creates a more reliable basis for prioritization, response planning, and decision-making.

Reference-aligned basis:

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

qualitative and quantitative techniques for deeper risk assessment,

the use of analytical methods after risk identification,

improved decision quality through structured analysis of uncertainty.

An affinity diagram is a tool used to visually organize and group risks or ideas based on their similarities and categories. It helps in structuring the risks for further analysis and discussion. (Reference: PMBOK Guide, 6th Edition, p. 138)

 According to the PMBOK Guide, an affinity diagram is a tool and technique for the identify risks process that allows large numbers of ideas to be sorted into groups for review and analysis. An affinity diagram can help the risk manager to visually organize the risks identified in the pre-workshop survey by grouping them into categories based on their similarities or common characteristics. This can help the risk manager to facilitate the risk analysis and prioritization in the workshop, as well as to stimulate new patterns of thinking and generate additional risks.

Some of the other options are not relevant or appropriate for the question scenario:

The analytical hierarchy process is a technique for the plan risk management process that provides a method for comparing and ranking alternatives based on multiple criteria. It is not a tool for visually organizing risks.

A SWOT analysis is a technique for the identify risks process that examines the project from the perspective of its strengths, weaknesses, opportunities, and threats. It is not a tool for visually organizing risks, but rather for generating them.

Assigning probability and impact is a technique for the perform qualitative risk analysis process that assesses the likelihood and the potential effect of each individual risk on the project objectives. It is not a tool for visually organizing risks, but rather for evaluating them.

PMBOK Guide, 6th edition, pages 397-399, 414-415, 431-432, 441-442; PMI-RMP Exam Content Outline, 2015, page 7.

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. References: 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.

When a project requires detailed and exhaustive planning to ensure the product ' s characteristics and quality, a predictive approach (also known as a waterfall approach) is the most appropriate. This approach involves planning out the project in detail upfront, including the scope, schedule, and costs, which aligns with the need for thorough planning mentioned in the scenario. The predictive approach is best suited for projects where requirements are well-understood and unlikely to change, allowing for careful management of risks through detailed plans​.

The correct answer is C. Revise the risk register to reflect changes in risk status and include new mitigation actions.

The question asks which document should be updated to reflect the current status of risks after a regular project risk review meeting. In standard project risk practice, the risk register is the primary document used to record identified risks, their current condition, ownership, probability, impact, triggers, response actions, and status updates. When risks are reviewed during recurring meetings, the risk manager should update the risk register so it accurately reflects the latest information.

This includes:

changes in probability or impact,

status of existing response actions,

newly identified mitigation activities,

newly identified risks,

closed risks,

secondary or residual risks where relevant.

Why the other options are incorrect:

A. Maintain the risk response plan and continuously monitor actions taken to mitigate risks. This describes an activity, not the main document that captures the current status of each risk. The question asks specifically which document should be updated.

B. Ensure that the risk management plan is reviewed to incorporate adjustments in risk strategies. The risk management plan defines the overall approach, methodology, roles, thresholds, and reporting processes for risk management. It is not the document typically updated during routine monthly reviews to show current risk status.

D. Update the project schedule to reflect the impacts of risks and adjustments to timelines. The schedule may need updates if risks affect timelines, but it is not the core risk tracking document. The direct and primary document for risk status is the risk register.

Best-practice reasoning:

Routine risk monitoring requires accurate and current risk documentation. The risk register is the operational tool used to track ongoing changes in the project’s risk profile and response progress.

Reference-aligned basis:

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

the risk register as the central repository for identified risks and their status,

updating the register during monitoring and review activities,

recording response actions and changes in exposure over time.

According to the PMI Risk Management Professional (PMI-RMP)® Examination Content Outline1, one of the tasks in the domain of Risk Response is to recommend risk response strategies based on the risk appetite and tolerance of the organization and stakeholders1. One of the strategies for negative risks or threats is risk acceptance, which involves acknowledging the existence of a threat and making a conscious decision to accept it without taking any action2. In this scenario, the risk manager should recommend risk acceptance for the risk items that would be detrimental to project success, but the associated triggers cannot be managed by the organization and are unlikely to occur. Risk acceptance is appropriate when the risk exposure is low, the cost of other responses is high, or the risk response is outside the scope or influence of the project3. The risk manager should not recommend risk mitigation, which involves reducing the probability and/or impact of a threat2. The risk manager should not recommend risk enhancement, which is a strategy for positive risks or opportunities, not negative risks or threats2. The risk manager should not recommend risk exploitation, which is also a strategy for positive risks or opportunities, not negative risks or threats2. 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 4363: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 437.

In a company undergoing significant cultural and organizational change, it ' s essential for the risk manager to engage with the appropriate stakeholders when planning risk management activities. Leveraging the project manager ' s stakeholder analysis provides a comprehensive understanding of individuals and groups affected by or capable of influencing the project. This analysis identifies stakeholders ' interests, influence, and potential impact on project success, enabling the risk manager to tailor risk management activities effectively. Collaborating with the project manager ensures alignment in stakeholder engagement strategies, fostering a cohesive approach to managing risks associated with organizational changes.

PMI Risk Management Study Guide References:

The PMI-RMP Exam Preparation Study Guide emphasizes the importance of stakeholder analysis in risk management, highlighting how understanding stakeholder interests and influences is crucial for effective risk planning and response.

Reviewing published operational experience reports from similar projects or industries can help the risk manager objectively identify risks for the chemical laboratory project. These reports provide valuable insights into potential risks and lessons learned from other projects.

According to the PMBOK Guide, one of the tools and techniques for the identify risks process is data gathering. Data gathering is the process of collecting information from various sources to identify potential risks that may affect the project objectives. One of the data gathering techniques is document analysis, which involves reviewing and analyzing available project documents and other information sources to identify potential risks. Some of the documents that can be analyzed are project charter, project management plan, stakeholder register, assumptions log, agreements, and lessons learned1.

One of the information sources that can be useful for identifying risks in a project constructing a chemical laboratory is published operational experience reports. These are reports that document the experiences, lessons learned, best practices, and recommendations from other organizations or projects that have constructed or operated chemical laboratories. These reports can provide valuable insights into the common risks, challenges, and opportunities that are associated with chemical laboratory projects, such as safety hazards, environmental regulations, equipment failures, design specifications, quality standards, and stakeholder expectations. By reviewing published operational experience reports, the risk manager can objectively identify risks that are relevant and applicable to their project, as well as learn from the successes and failures of others23.

Some of the other options are not relevant or appropriate for the question scenario:

Importing a risk register from other industry chemical laboratories is not a valid option, as it would not allow the risk manager to objectively identify risks that are specific and unique to their project. A risk register is a document that records the identified risks, their causes, impacts, responses, owners, and other information related to the risk management process. A risk register is a project-specific document that reflects the characteristics, objectives, and context of a particular project. Importing a risk register from other industry chemical laboratories would not ensure that the risks are relevant, accurate, or comprehensive for the risk manager’s project. Moreover, it would violate the intellectual property rights and confidentiality agreements of the other projects1.

Defining chemical laboratory safety risk thresholds is not a tool or technique for identifying risks, but rather for performing qualitative risk analysis. Risk thresholds are the measures of the level of uncertainty or the level of impact at which a stakeholder may have a specific interest. Risk thresholds are used to determine the significance of each risk and to prioritize them for further analysis or action. Defining chemical laboratory safety risk thresholds would not help the risk manager to objectively identify risks, but rather to evaluate them1.

Drafting threat and opportunity risks that come to mind is not an objective or systematic way of identifying risks, but rather a subjective and intuitive one. This option would rely on the risk manager’s personal judgment, experience, or creativity, which may not be sufficient or reliable for identifying risks in a project constructing a chemical laboratory. This option would also not ensure that the risks are based on factual and verifiable information sources, such as project documents or published reports. Drafting threat and opportunity risks that come to mind would not help the risk manager to objectively identify risks, but rather to generate them1.

PMBOK Guide, 6th edition, pages 397-399, 414-415, 431-432, 441-4421; Risk Management Professional (PMI-RMP)® Cert Guide, pages 63-642; Risk Management Professional Exam Outline, page 73.

Whenever new organizational directives or changes in risk thresholds are communi cated, the risk manager is required to assess the impact and update the risk management plan to reflect these changes. The PMBOK® Guide states:

“When organizational risk thresholds or tolerances are changed, the risk management plan and associated processes must be updated to ensure alignment with current requirements.”

— PMBOK® Guide, 6th Edition, Section 11.1.3.1 (Risk Management Plan: Updates)

This ensures that risk responses, monitoring, and reporting are in accordance with the most current strategic direction and tolerances.

Legal and regulatory requirements and constraints when assessing a project environment for threats and opportunities may include ensuring the confidentiality of project information, as this is often governed by laws and regulations.

Legal and regulatory requirements and/or constraints are external factors that can affect the project environment and influence the risk management process. They may include laws, regulations, standards, codes, permits, licenses, contracts, or agreements that the project must comply with or adhere to. Confidentiality of project information is an example of such a requirement or constraint, as it may limit the disclosure, sharing, or access of project data, documents, or reports to authorized parties only. Violating confidentiality may result in legal actions, penalties, or reputational damage for the project and the organization. Therefore, the project manager and the risk management team must identify and comply with the confidentiality requirements and/or constraints when assessing the project environment for threats and opportunities. References: PMI, 2019. Practice Standard for Project Risk Management. Newtown Square, PA: Project Management Institute, Inc., p. 181

The risk manager is responsible for ensuring that all risks, including secondary risks, are identified and addressed during the risk response planning process. If key secondary risks were missed, the risk manager should be held accountable. (Reference: Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Section 11.5)

The risk manager is responsible for identifying and analyzing risks, as well as planning and implementing risk responses. Secondary risks are those risks that arise as a direct result of implementing a risk response to a specific risk. The risk manager should have considered the potential secondary risks during the risk response planning and updated the risk register accordingly. The project manager should hold the risk manager accountable for missing the secondary risks and ensure that they are properly addressed12

 1: PMI Risk Management Professional (PMI-RMP)® Handbook, page 10 2: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, page 11.2.2.1

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.

The risk manager should consult the risks that have materialized and the overall risk profile to analyze the performance of managing the risks, as well as the risks due to the number of claims submitted to the client. These options provide insights into how well risks are being managed and the potential impact on the project.

 The risk manager should consult the risks that have materialized and the overall risk profile, as these are indicators of how well the risk management process is working and how the project is affected by the risks. The risk manager should also consult the risks due to the number of claims submitted to the client, as these are potential sources of conflict, litigation, and reputation damage that may impact the project objectives and stakeholder satisfaction. References: The Standard for Risk Management in Portfolios, Programs, and Projects, page 83; PMBOK Guide, 6th edition, page 414.

Scenario analysis is a useful tool for assessing the risk involved in testing by exploring different possible outcomes. In the context of deciding between laboratory testing, simul-ation methods, and field trials, scenario analysis allows the risk manager to evaluate the potential risks and benefits of each testing approach under different scenarios. This method helps in understanding how various uncertainties can impact the testing process and its outcomes, which is critical when selecting the most appropriate testing strategy​.

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. References: PMI-RMP Exam Content Outline and Specifications, page 10.

The main output of the stakeholder meeting in the initiation phase is to identify threats and opportunities that may impact the project in a positive or negative way. This information will be used to develop the risk management plan.

The meeting that the project stakeholders are invited to in the initiation phase is part of the Identify Risks process. The purpose of this process is to identify the risks that may affect the project objectives in a positive or negative way, and to document their characteristics. The main output of this process is the risk register, which is a document that contains the list of identified risks, their causes, potential responses, and other relevant information. The risk register is an essential input for the subsequent risk management processes, such as Perform Qualitative Risk Analysis, Perform Quantitative Risk Analysis, Plan Risk Responses, and Monitor Risks. Therefore, the correct answer is B. Identifying threats and opportunities. References: PMI, The Standard for Risk Management in Portfolios, Programs, and Projects, 2019, p. 79-80, 86-87.

A low CPI value (0.53) indicates that the project is over budget. This may be due to an inaccurate cost baseline, which means the initial budget estimation was not correct. This would not necessarily mean that cost control processes are ineffective, actual reported costs are inaccurate, or cost-related risks are effectively managed.

The CPI value is calculated by dividing the earned value (EV) by the actual cost (AC). A CPI value of less than 1 indicates that the project is over budget, meaning that the actual cost is higher than the planned cost. A low CPI value can have several possible causes, such as poor estimation, scope creep, change requests, or inaccurate reporting. However, in this case, the SPI value is greater than 1, which indicates that the project is ahead of schedule, meaning that the earned value is higher than the planned value. This suggests that the cost baseline, which is derived from the planned value, is inaccurate and does not reflect the true cost of the work. Therefore, the risk manager should interpret such a low CPI value as a sign of an inaccurate cost baseline, and not as a result of ineffective cost control processes, inaccurate actual costs, or effective cost related risk management. References: PMI-RMP® Certification Handbook1, page 9; PMBOK® Guide, page 267.

Decision tree analysis is a technique that uses a graphical representation of various possible outcomes and consequences of different courses of action, based on their probabilities of occurrence and associated payoffs or costs. It can help the project team to compare and evaluate the alternatives and choose the optimal one. In this case, the risk manager should use decision tree analysis to help the team members predict the outcomes of their potential choices following their probability of occurrence. Political, economic, social, technological, legal, and environmental (PESTLE) analysis, strengths, weaknesses, opportunities, and threats (SWOT) analysis, and cost-benefit analysis are not techniques that can directly help the team members to predict the outcomes of their potential choices following their probability of occurrence, and are therefore not the best answer. References: PMI Risk Management Professional (PMI-RMP)® Exam Content Outline1, PMI Practice Standard for Project Risk Management2, Risk Management Professional (PMI-RMP)® Cert Guide3

 According to the PMI Risk Management Professional (PMI-RMP)® Examination Content Outline1, one of the tasks in the domain of Risk Identification is to use the information from project documents, lessons learned, and other sources to facilitate the risk identification process1. A risk workshop is a tool and technique for risk identification that involves bringing together the project team, stakeholders, subject matter experts, and risk management experts to identify and analyze the project risks in a structured and collaborative manner2. In this scenario, the risk manager should use the information from the issues and unexpected results found in the first phase of the project for a risk workshop, to avoid the previous issues in the next phase. The risk workshop will help the risk manager and the project team to identify the root causes of the issues, assess their probability and impact, and develop appropriate risk responses. The risk workshop will also enable the risk manager to update the risk register and the risk report with the new information and communicate the risk status to the relevant stakeholders. The risk manager should not improve monitoring and controlling of activities, because that is not a specific action to avoid the previous issues, but rather a general practice that should be done throughout the project life cycle3. The risk manager should not document the issues in the lessons learned, because that is not enough to avoid the previous issues, but rather a way to capture and share the knowledge gained from the project for future reference4. The risk manager should not create an issue log to share with the team, because that is not a proactive risk management technique, but rather a reactive way to track and resolve the issues that have already occurred5. References: 1: PMI Risk Management Professional (PMI-RMP)® Examination Content Outline, page 82: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 4003: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 4564: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 1005: What Is an Issue Log? Templates & Tips6.