Free PMI-RMP Practice Test

The risk management plan is a component of the project management plan that describes how risk management activities will be structured and performed. A key element of this plan is establishing the timing and frequency for all risk management processes. For a project in a fast-paced industry (high business rhythm), the risk management plan would be tailored to mandate more frequent reviews and updates of the risk register to maintain relevance and proactively manage emerging risks in the dynamic environment. This plan sets the cadence for the entire risk management effort throughout the project lifecycle.

B. The risk triggers: Risk triggers are predefined indicators that a specific risk is imminent or has occurred; they prompt action on a risk, not define the regular review schedule for the entire register.
C. The risk prioritization criteria: These criteria, such as a probability and impact matrix, are used to evaluate and rank identified risks, not to determine the frequency of risk management activities.
D. The portfolio management plan: This plan operates at a strategic level, governing a collection of projects. The specific operational cadence for a single project's risk review is detailed in that project's own risk management plan. ---

1. Project Management Institute. (2009). Practice Standard for Project Risk Management. Section 4.1.3.1, Risk Management Plan. The standard explicitly states that the "Timing" section of the risk management plan defines "when and how often the project risk management processes will be performed throughout the project life cycle."

2. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Section 2.4, Planning Performance Domain. This section notes that planning activities establish the approach and cadence for project work, including "the timing and frequency for reviewing and updating project plans" and their components, which includes the risk register.

3. Hillson, D. (2002). The Risk Breakdown Structure (RBS) as an Aid to Effective Risk Management. Proceedings of the 33rd Annual Project Management Institute Seminars & Symposium. This paper discusses the importance of a structured approach to risk, which is defined in the risk management plan, including the establishment of a regular review cycle. The frequency of this cycle is a key planning decision.

The most effective way to address the team member's concern about comprehensive risk coverage is to introduce a structured identification technique. A Risk Breakdown Structure (RBS) is a hierarchical decomposition of potential sources of risk. It provides a systematic framework, organizing risks into categories and subcategories (e.g., Technical, External, Organizational, Project Management). This structured approach acts as a prompt list, guiding the team member to consider all potential areas of the project, thereby ensuring a more thorough and comprehensive risk identification process, which is crucial for a complex project.

B. Develop a risk impact analysis to assess the consequences of possible risks: This is a step in risk analysis, which occurs after risks have been identified. It evaluates the potential effect of a risk, but does not help in discovering them.
C. Develop a probability and impact matrix to analyze possible risks: This tool is used for qualitative risk analysis to prioritize identified risks based on their likelihood and consequence. It is not a risk identification technique.
D. Create a risk register to capture and track possible risks: The risk register is the output document where identified risks are logged. While essential for documentation, creating the register itself does not provide the method to ensure comprehensive identification.

1. Project Management Institute. (2019). The Standard for Risk Management in Portfolios, Programs, and Projects. Newtown Square, PA: Project Management Institute.

Section 4.3.2.2, Tools and Techniques, Risk Breakdown Structure (RBS): "The RBS is a hierarchical representation of potential sources of risk... The RBS can be used as a prompt list to facilitate a comprehensive and systematic process of risk identification." (p. 49)

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Newtown Square, PA: Project Management Institute.

Section 11.2.2.3, Data Analysis, Prompt Lists: "Prompt lists are predetermined lists of risk categories that might give rise to individual project risks and that could also act as sources of overall project risk. The prompt list can be used as a framework to aid the project team in idea generation... The lowest level of the RBS can be used as a prompt list for individual risks." (p. 416)

3. Hillson, D. (2003). Using a risk breakdown structure in project management. Journal of Facilities Management, 2(1), 85-97.

Abstract & Section "The Risk Breakdown Structure": The paper describes the RBS as a tool to "help understand and manage project risk in a structured way" and emphasizes its role in ensuring that "all potential sources of risk to the project have been considered" during the identification phase. (DOI: https://doi.org/10.1108/14725960310807979)

The chart presented is a Tornado Diagram, which is a standard output of sensitivity analysis in quantitative risk analysis. This diagram helps identify which risks or sources of uncertainty have the most significant impact on a specific project objective, in this case, the project's total duration. The activities are ranked vertically, with the one having the greatest impact at the top. The length of the horizontal bar represents the degree of sensitivity or the range of impact. Activity 3.2 has the longest bar, indicating it has the highest potential to affect the project's duration. Therefore, it should receive the most attention for risk response planning.

B. Activity 2.3: While this activity has a notable impact, its corresponding bar in the Tornado Diagram is shorter than that of Activity 3.2, making it a lower priority.
C. Activity 3.5: This activity has a much smaller potential impact on the project's duration compared to Activity 3.2, as shown by its shorter bar.
D. Activity 1.2: This activity has the least impact among the choices provided, making it the lowest priority for immediate risk response planning. ---

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.).

Section 11.4.2.2 Data Analysis: "Sensitivity analysis helps to determine which individual project risks or other sources of uncertainty have the most potential impact on project outcomes. It correlates variations in project outcomes with variations in elements of the quantitative risk analysis model... The results are typically displayed as a tornado diagram, which presents the calculated correlation coefficient for each element of the quantitative risk analysis model that can influence the project outcome." The text further explains that the risks with the greatest impact are listed at the top.

2. Project Management Institute. (2019). The Standard for Risk Management in Portfolios, Programs, and Projects.

Section 6.5.2.1 Sensitivity Analysis: This section describes sensitivity analysis as a technique to determine which risks have the most potential impact. It explicitly mentions the Tornado Diagram as a common output: "The results of sensitivity analysis are often shown on a tornado diagram... The risks are ordered with those having the most impact at the top."

3. Hillson, D. (2009). Managing Risk in Projects. Gower Publishing, Ltd.

Chapter 7, Quantitative Risk Analysis: This chapter discusses sensitivity analysis and explains that Tornado diagrams are used to "compare the relative importance of different variables" and that "the variable with the widest range is the most sensitive and has the highest priority for management attention."

4. Hulett, D. T. (2011). Integrated Cost-Schedule Risk Analysis. Gower Publishing, Ltd.

Chapter 5, Sensitivity Analysis: The Tornado Diagram: "The tornado diagram shows the project’s sensitivity to the risks, ranked from the most sensitive at the top to the least sensitive at the bottom... Management attention should focus on the high-ranked risks." This directly supports prioritizing the activity with the longest bar (Activity 3.2).

The risk marked 'X' on the heat map is positioned at the intersection of the "Medium" probability row and the "High" impact column. According to the scales provided on the matrix axes, "Medium" probability corresponds to a value of 0.5 (or 50%), and "High" impact corresponds to a value of 0.4.
Option B states the risk has a "high impact rating," which correctly matches the risk's position on the matrix. While it lists the probability as 40%, this is the closest numerical value to the actual 50% compared to the other options, which are qualitatively incorrect. This suggests a minor inaccuracy in the question's option, but it remains the best possible choice.

A. This option is incorrect because the impact is high, not medium, and the probability is 50%, not 60%.
C. This option incorrectly describes the probability as high. The matrix clearly places the risk in the medium probability category.
D. This option incorrectly describes the probability as low. The matrix clearly places the risk in the medium probability category. ---

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Project Management Institute, Inc.

Section 4.2.5, Models: This section discusses various models used in project management, including the probability and impact matrix. It explains that such matrices are used to map the probability of a risk and its potential impact, visually representing the risk's priority. The question requires a direct interpretation of such a model.

2. Project Management Institute. (2019). The Standard for Risk Management in Portfolios, Programs, and Projects. Project Management Institute, Inc.

Section 5.4.2.2, Data Analysis: This section details the use of a probability and impact matrix in Qualitative Risk Analysis. It states, "The probability and impact matrix is a grid for mapping the probability of each risk occurrence and its impact... Risks are rated on their probability of occurring and their impact on at least one objective." The provided question is a direct application of this principle, requiring the candidate to read the coordinates of risk 'X'.

3. Hillson, D. (2004). Effective Opportunity Management for Projects: Exploiting Positive Risk. CRC Press.

Chapter 5, Qualitative Risk Analysis: This chapter details the process of assessing risks using qualitative scales. It describes how probability and impact scales (e.g., Very Low to Very High, or numerical scales like 0.1 to 0.9) are defined and used to plot risks on a P-I matrix to determine their significance. The question's matrix, with its defined scales, is a standard representation discussed in such academic texts.

The project's circumstances have changed significantly due to budget overruns, which introduces new constraints and potentially elevates the impact of existing risks. The upcoming stakeholder reviews are a known source of uncertainty that could lead to changes and rework, further straining the constrained budget. Therefore, the most appropriate and proactive step is to conduct a risk reassessment. This involves re-evaluating identified risks and identifying new ones in light of the new financial reality. A reserve analysis is a critical component of this process, used to compare the remaining contingency reserves against the remaining risk exposure to determine if the budget is adequate for future uncertainties.

A. Request a budget relief using the management reserve. Management reserve is for unforeseen risks (unknown-unknowns), not for expected work arising from a planned activity like stakeholder reviews.
C. Review the consequences of potential changes. This action is a component of a risk reassessment but is not as comprehensive as option B, which includes both reassessment and reserve analysis.
D. Coach stakeholders on risk identification practices. While beneficial for project culture, this does not address the immediate and critical issue of managing potential budget impacts from the upcoming reviews.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.).

Section 11.7 Monitor Risks: This process involves "monitoring the implementation of agreed-upon risk response plans, tracking identified risks, identifying and analyzing new risks, and evaluating risk process effectiveness throughout the project."

Section 11.7.2.2 Risk Reassessment: "Project risk reassessments should be regularly scheduled... A risk reassessment may also be required when the project deviates significantly from the baseline, or when a major risk has occurred." The budget overrun constitutes a significant deviation.

Section 11.7.2.3 Reserve Analysis: "Reserve analysis compares the amount of contingency reserves remaining to the amount of risk remaining at any time in the project in order to determine if the remaining reserve is adequate."

2. Project Management Institute. (2019). The Standard for Risk Management in Portfolios, Programs, and Projects.

Section 5.8 Monitor Risk: This section emphasizes that risk monitoring is an ongoing process. It states, "As the project progresses, the overall project risk may change from its initial state. It is therefore important to repeat the Perform Qualitative Risk Analysis and Perform Quantitative Risk Analysis processes..." This directly supports the need for reassessment.

Figure 5-15. Monitor Risk: Tools and Techniques: Lists "Risk Reassessment" and "Reserve Analysis" as key tools for this process.

3. Hillson, D. (2009). Managing Risk in Projects. Gower Publishing, Ltd.

Chapter 10, Risk Review & Reporting: This chapter explains that the risk process is iterative and that regular reviews are essential to maintain relevance. It notes that triggers for a risk review include "significant change in project context or scope," which applies to the scenario of serious budget constraints. The review process described includes re-evaluating existing risks and checking the adequacy of responses, including contingency. (Specific reference to iterative review process and triggers for it).

The identified issues of declining morale, mistrust, and isolation are indicators of a dysfunctional team culture and a breakdown in collaboration. In an agile environment, the project manager acts as a servant leader, responsible for fostering a cohesive and high-performing team. Promoting cross-training and mentoring directly addresses the root causes by encouraging team members to interact, share knowledge, and rely on one another. This builds interpersonal trust, breaks down silos, and fosters a sense of collective ownership and shared purpose. These activities are fundamental to creating the psychological safety and collaborative spirit necessary for a productive and cohesive agile team.

A. Introducing performance standards and evaluation methods can increase individual pressure and competition, potentially worsening mistrust and isolation in an already struggling team.
B. Clarifying project goals and contract constraints addresses project direction, not the underlying interpersonal and cultural issues causing low morale and mistrust.
D. A reward system based on position and experience promotes hierarchy and individual status, which is contrary to the collaborative, team-oriented ethos of agile methodologies.

1. Project Management Institute. (2017). Agile Practice Guide.

Section 5.2.2, T-shaped Skills, p. 43: The guide states, "Cross-functional team members seek to be T-skilled... Cross-training, pair work, and swarming facilitate better collaboration." This directly supports cross-training as a method to improve collaboration, which is at the heart of solving the team's issues.

Section 5.3, Servant Leadership, p. 49: Servant leadership emphasizes "facilitating collaboration" and "building a culture of trust." The actions in option C are prime examples of a servant leader facilitating collaboration and trust-building within the team.

2. Project Management Institute. (2019). The Practice Standard for Project Risk Management.

Section 3.2.2, Sources of Overall Project Risk, p. 19: This section notes that project complexity arising from "human behavior" is a source of risk. The declining morale and mistrust represent a significant human-behavior risk. Implementing a response like cross-training mitigates the risk of team failure.

3. Moe, N. B., Dingsøyr, T., & Dybå, T. (2010). A teamwork model for understanding an agile team: A case study of a Scrum project. Information and Software Technology, 52(5), 480-491. https://doi.org/10.1016/j.infsof.2009.11.004

This study emphasizes that shared knowledge and mutual support are critical for agile team effectiveness. The paper's findings support that practices like mentoring and knowledge sharing (inherent in cross-training) are essential for building the coordination and cohesion needed for high performance, directly addressing the problems of mistrust and isolation.

The fundamental issue described is a misalignment between the risk presentation format and the expectations of a key stakeholder group (the board). This indicates a failure to properly define and agree upon the risk management approach during the planning phase. Engaging key stakeholders, including the board or their representatives, during the process of defining risk categories, probability and impact scales, and prioritization rules is a critical step in the Plan Risk Management process. This collaborative approach ensures that the methodology for sorting and presenting risks is understood and accepted by those who will use the information for decision-making, thereby preventing such costly rework and delays.

B. Prioritizing based solely on the sponsor's risk appetite is insufficient, as it neglects the potentially different perspectives and requirements of other key stakeholders, such as the board.
C. While engaging the sponsor is a good practice, it does not guarantee alignment with the board, which is a distinct and powerful stakeholder group with its own requirements.
D. Using an industry standard does not guarantee acceptance. The risk management approach must be tailored to the specific project context and its unique stakeholder needs and preferences.

1. Project Management Institute. (2019). The Standard for Risk Management in Portfolios, Programs, and Projects.

Section 4.2.3.1, Risk Management Strategy: States that the risk management strategy should be "appropriate for the project and agreed to by key stakeholders." The prioritization method is a core component of this strategy.

Section 4.2.3.2, Stakeholder Risk Attitudes: Emphasizes that the risk management plan should document the risk attitudes of key stakeholders, as these attitudes "influence how risk management will be performed." This directly supports engaging stakeholders to understand their preferences for how risks are categorized and prioritized.

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition.

Section 11.1, Plan Risk Management: This process is about defining how to conduct risk management activities. The inputs include the Stakeholder Register and Stakeholder Engagement Plan, highlighting the necessity of involving stakeholders from the outset to define the framework, including prioritization rules, which are documented in the resulting Risk Management Plan.

3. Hillson, D. (2002). Extending the risk process to manage opportunities. International Journal of Project Management, 20(3), 235-240.

This paper discusses the importance of tailoring the risk process, including the definition of scales and thresholds, to be meaningful and useful for the organization and its stakeholders. This supports the idea that a pre-defined or standard approach (Option D) may not be sufficient without stakeholder consultation and agreement. (https://doi.org/10.1016/S0263-7863(01)00074-6)

An early risk trigger is a warning sign or condition indicating that a risk is likely to occur. In this context, the risk is the "lack of space to install air conditioners." The "potential need to share the space with other machinery" is a condition that would be identified during the planning or early design phase. It serves as an early warning that the allocated space may become insufficient, allowing the project team to proactively develop a response before the installation work begins and the risk materializes.

B. Receiving different equipment is a trigger that occurs immediately before installation, not an early warning sign from the planning stage.
C. A time delay is a potential consequence or impact of the risk occurring, not a trigger that warns of the impending lack of space.
D. A quality nonconformance issue is identified during inspection after installation, making it a lagging indicator, not an early trigger.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.).

Section 11.7.2.1, Project Documents Updates: This section discusses updating the risk register with information including "triggers." It defines triggers (or warning signs) as indicators that a risk has occurred or is about to occur. Option A is a classic example of a condition that signals a risk is about to occur.

2. Project Management Institute. (2009). Practice Standard for Project Risk Management (1st ed.).

Section 4.2.2.3, Risk Triggers (p. 31): "Risk triggers, sometimes known as risk symptoms or warning signs, are events or conditions that indicate that a risk is about to occur or has occurred... Identifying potential risk triggers during the risk identification process can improve the ability of the project team to monitor risks." This directly supports identifying a condition like "potential need to share space" as a trigger.

3. Hillson, D. (2002). The Risk Breakdown Structure (RBS) as an Aid to Effective Risk Management. Project Management Institute - 2002 Seminars & Symposium.

This paper discusses identifying risks from various sources. An early warning sign, such as a constraint on a physical resource (space), is a key input to the risk management process. The potential conflict over space (Option A) is an identifiable condition that acts as such a warning.

The scenario describes an emergent opportunity for one project (Project B) that arises from a risk response action in another (Project A). The most appropriate and immediate action for Project A's risk manager is to communicate this finding to the relevant stakeholder, which is the risk manager for Project B. This facilitates integrated risk management across projects, ensuring that organizational benefits are maximized. Consulting allows for the validation of the opportunity and the exploration of synergies, where both projects might coordinate their plans for mutual benefit. This proactive communication is a core responsibility of a risk manager operating within a multi-project environment.

A. This action is premature as Project A is still in execution, not closure. It also escalates an immediate tactical opportunity into a long-term strategic process change.
C. Combining entire risk registers is an inefficient and overly bureaucratic response to a single, specific cross-project opportunity. Direct communication is more effective.
D. This option demonstrates a siloed approach by focusing only on Project A and completely ignoring the identified opportunity that could benefit Project B and the organization.

1. Project Management Institute. (2019). The Standard for Risk Management in Portfolios, Programs, and Projects.

Section 4.5, Program Risk Management (p. 63): This section emphasizes that program risk management involves managing risks at a level above individual projects, including "the processes of identifying, analyzing, and planning responses to risks... and aggregating and managing component-level risks." This principle directly supports the need for communication and coordination between projects (components) like A and B to manage cross-cutting issues.

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition.

Section 11.6, Implement Risk Responses (p. 453): This process notes that implementing risk responses can result in secondary risks (or opportunities). The outputs include updates to the risk register and other project documents. The implicit next step for a risk affecting another project is communication, a fundamental theme of Project Integration Management (Chapter 4).

3. Hillson, D. (2002). Extending the risk process to manage opportunities. International Journal of Project Management, 20(3), 235-240.

DOI: https://doi.org/10.1016/S0263-7863(01)00074-600074-6)

This paper argues for a proactive approach to managing opportunities with the same rigor as threats. It states, "The aim of the opportunity management process is to... maximize their probability and/or impact." In the given scenario, ignoring the opportunity for Project B (Option D) or delaying action (Option A) would violate this principle. The first step to maximizing the opportunity is to engage the project that can exploit it (Option B).

The scenario occurs during the Identify Risks process. According to standard project risk management methodology, any potential risk identified during brainstorming must first be documented in the risk register. This action ensures the risk is formally captured. The subsequent processes, Perform Qualitative and Quantitative Risk Analysis, will use the risk register to objectively assess the probability and impact of this and all other identified risks. This data-driven analysis will determine its priority and the appropriate response, resolving the stakeholder disagreement based on a formal assessment rather than subjective opinions. Acting on a response strategy like acceptance, mitigation, or escalation before analysis is premature and procedurally incorrect.

A. Accepting a risk is a response strategy determined only after a thorough analysis of its probability and impact, not during the identification phase.
B. Mitigating a risk is a response strategy. The decision to mitigate is made after the risk has been analyzed and prioritized, not based on a single stakeholder's opinion.
C. Escalating a risk is a specific response strategy for risks outside the project manager's authority; this is not indicated and is premature before analysis.

1. Project Management Institute. (2019). The Standard for Risk Management in Portfolios, Programs, and Projects. Newtown Square, PA: Project Management Institute. See Section 4.3, "Identify Risks," which states that a key output is the initial entry of risks into the risk register (p. 49), which then serves as an input to the analysis processes (p. 57).

2. Hillson, D. (2002). The Risk Breakdown Structure (RBS) as an Aid to Effective Risk Management. Project Management Institute Annual Seminars & Symposium. DOI: 10.14802/pmi.v3i1.368. The paper emphasizes a structured approach where identification precedes analysis, with all identified risks being captured for subsequent review.

3. Chapman, C., & Ward, S. (2003). Project Risk Management: Processes, Techniques and Insights (2nd ed.). Wiley. Chapter 6, "The risk management process: a framework," outlines the sequence of risk management, where risk identification and structuring (including logging in a register) must precede analysis and response planning.