Free PMI-RMP Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

The risk manager should use the Delphi method in this situation, as this is a technique that can help

resolve differences among experts and reach a consensus on the identified risks and their

characteristics. The Delphi method is a tool used to make quick decisions with consensus. This

technique consists of sending several sets of anonymous questions to each expert. This is followed by

a group discussion after every round. The Delphi method can help the risk manager to solicit the

opinions of all experts without revealing their identities. This way, the experts can express their

views freely and honestly, without being influenced or intimidated by others. The Delphi method can

also reduce personal bias, ego, or emotional conflict among the participants. The risk manager can

use the results of the Delphi method to create a list of potential risks and their causes, effects, and

probabilities. The other options are not appropriate techniques for the risk manager to use in this

situation. Brainstorming is a technique that can help generate ideas and identify risks, but it may not

be effective in resolving differences among experts, as it involves open and spontaneous discussion.

Focus group is a technique that can help collect requirements and opinions from stakeholders, but it

may not be suitable for resolving technical disagreements among experts, as it involves a moderated

and structured discussion. Checklist analysis is a technique that can help identify risks based on

historical information and lessons learned, but it may not be helpful in resolving differences among

experts, as it involves a predefined list of potential risks. Reference: 3, 4, 5

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. Reference: The Standard for Risk

Management in Portfolios, Programs, and Projects, page 83; PMBOK Guide, 6th edition, page 414.

To effectively inform the identification of resource requirements for individual risk responses, the risk

manager should undertake the following actions:

1. Conduct Decision Tree Analysis: Collaborate with the project team to perform decision tree

analysis for each risk or related set of risks. This technique involves mapping out different decision

paths and their possible outcomes, including associated risks, probabilities, and impacts. By

visualizing these scenarios, the team can evaluate the potential consequences of various decisions

and choose the most effective risk response strategies.

2. Calculate Expected Monetary Value (EMV): Determine the EMV for each identified risk by

multiplying the probability of occurrence by the potential financial impact. This quantitative analysis

provides a monetary value representing the average expected loss or gain from a risk. Utilizing EMV

calculations aids in justifying and allocating appropriate project reserves to address potential risks,

ensuring that sufficient resources are available for effective risk management.

3. Prioritize High-Impact Risks: Allocate attention and resources primarily to risks that pose the

highest potential impact on the project. By focusing on high-impact risks, the team ensures that

critical threats are addressed promptly and effectively, optimizing the use of limited resources and

enhancing the likelihood of project success.

PMI Risk Management Study Guide Reference:

The PMI-RMP Exam Content Outline emphasizes the importance of performing quantitative risk

analysis, including techniques such as decision tree analysis and EMV calculations, to inform risk

response planning and resource allocation.

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.

To address the lack of risk management buy-in from the project team, the risk manager should

organize risk engagement activities, such as workshops. These activities can help create awareness of

the importance of risk management and motivate the team to take their risk management

responsibilities seriously.

Risk engagement is the process of involving stakeholders in risk management activities, such as

identifying, analyzing, prioritizing, and responding to risks. Risk engagement activities are designed

to motivate and influence the project team and other stakeholders to take their risk management

responsibilities seriously and to understand the benefits of risk management for the project’s

success. Risk engagement activities can include workshops, games, simul-ations, brainstorming

sessions, surveys, interviews, and other interactive methods. Risk engagement activities can help to

create a positive risk culture, improve communication and collaboration, increase risk awareness and

ownership, and enhance risk management skills and knowledge. Reference: PMI Risk Management

Professional (PMI-RMP) Examination Content Outline and Specifications1, page 9; Mastering PMI-

RMP Domains, Tasks, and Enablers for Effective Risk2

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. Reference: PMI Risk Management Professional (PMI-RMP)® Exam Content Outline1, PMI

Practice Standard for Project Risk Management2, Risk Management Professional (PMI-RMP)® Cert

Guide3

Variance analysis is a technique used to compare actual project performance against planned

performance. In this scenario, the risk manager is comparing planned enablement sessions with

actual sessions to identify discrepancies that could indicate potential risks. This approach allows the

project team to monitor performance closely and take corrective actions as needed to keep the

project on track, which is crucial for projects with strict timelines .

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 full risk description is the first thing that the risk manager should complete before moving

forward with the risk response planning. The full risk description is a detailed statement that

describes the risk, its causes, its effects, and its context. It provides the basis for the risk analysis and

the risk response planning. The risk categorization, the risk simul-ation, and the risk response plan

are possible steps that the risk manager may take after completing the full risk description, but they

are not the first thing to do. Reference: PMI Risk Management Professional (PMI-RMP)® Exam

Content Outline1, PMI Practice Standard for Project Risk Management2, Risk Management

Professional (PMI-RMP)® Cert Guide3

This is a secondary risk because it is a risk that arises as a direct result of implementing a risk

response (in this case, procuring material from a different supplier).

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 procure the material from a different supplier if the first

supplier fails to deliver on time. The secondary risk is that there may be differences in the material

provided by the first and second supplier, which could affect the quality, cost, or schedule of the

project. A secondary risk is different from a residual risk, which is a risk that remains after a risk

response has been implemented. A primary risk is the original risk that triggers a risk response. A

normal risk is not a standard term in risk management, but it could refer to a risk that is expected or

inherent in a project. Reference: PMI Risk Management Professional (PMI-RMP) Examination

Content Outline and Specifications1, page 9; A Guide to the Project Management Body of Knowledge

(PMBOK® Guide) – Sixth Edition, page 397; Secondary vs Residual Risk | Types of Risks on the PMP

Exam.

Categorizing risks by their impact on project objectives ensures that risk response plans are aligned

with project priorities. This helps in focusing on the most critical risks and their potential impact on

the project's success.

Categorizing risks by their impact to the project objectives is a way of aligning the risk management

process with the project goals and stakeholder expectations. By doing so, the risk management

professional can ensure that the risk response plans are focused on the most critical aspects of the

project and that the project priorities are being considered in the decision making. This approach can

also help to communicate the value of risk management to the project team and the stakeholders, as

they can see how the risk management activities are contributing to the project success.

Categorizing risks by their impact to the project objectives does not necessarily help to identify the

specific causes of risks, determine the level of project leadership and organizational involvement, or

assign risks and risk severities to functional disciplines and departments. These are other possible

ways of categorizing risks, but they are not the main purpose of using the impact to the project

objectives approach. Reference: PMI-RMP® Certification Handbook1, page 9; PMBOK® Guide, page

415.

The project manager should have performed risk identification exercises for the full lifecycle of the

project, including the construction phase, to ensure that all potential risks were identified and

addressed in the risk register.

Risk identification is the process of determining the risks that may affect the project and

documenting their characteristics. Risk identification should be performed throughout the project

lifecycle, as new risks may emerge or change over time. Risk identification should also consider all

aspects of the project, such as scope, schedule, cost, quality, resources, stakeholders, and

procurement. By performing risk identification exercises for the full lifecycle of the project, the

project manager could have identified and planned for the potential risks associated with the

construction phase, such as delays, material shortages, quality issues, or safety hazards. This would

have helped to prevent or mitigate the impact of the risk event that occurred, and to ensure that the

risk register is updated and comprehensive. Performing a Monte Carlo sensitivity analysis, adding

generic construction risks, or reviewing the assumptions/exclusions register are not sufficient or

effective ways of identifying the specific risks that may affect the project during the construction

phase. These are either tools for risk analysis, risk response planning, or project initiation, but not

risk identification. Reference: PMI-RMP® Certification Handbook1, page 9; PMBOK® Guide, pages

397-398.

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 .

For a multi-million-dollar project with numerous risks, understanding the stakeholders' risk

thresholds based on their risk appetites is crucial. This helps in defining the boundaries within which

the project can operate and determine acceptable levels of risk. By confirming these thresholds, the

risk management team can ensure that the project remains aligned with stakeholders' expectations

and that appropriate risk responses are developed. This is a key step in the risk management process

as per PMI guidelines, which emphasize the importance of aligning risk management efforts with

stakeholders' risk tolerance and appetite .

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 p

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. Reference: = PMBOK Guide,

6th edition, pages 406-407; The Standard for Risk Management in Portfolios, Programs, and Projects,

page 67.

Regression analysis is a data analysis tool that helps identify variables that impact the schedule and

determine how these factors interact. It is used to forecast future performance based on historical

data and the relationship between variables. (Reference: PMBOK Guide, 6th Edition, p. 248)

According to the PMI Risk Management Professional (PMI-RMP) Reference Materials, regression

analysis is a data analysis tool that examines the relationship between one or more independent

variables and a dependent variable1. Regression analysis can be used to forecast future performance

based on historical data and trends2. In this case, the risk manager wants to identify which variables

will impact the schedule (the dependent variable) and determine how these factors interact (the

independent variables). Therefore, the risk manager should use regression analysis to create a

mathematical model that can predict the schedule performance based on the values of the

variables. Regression analysis can also help the risk manager to assess the significance and strength

of the relationship between the variables and the schedule3.

Reference: 1: PMI, A Guide to the Project Management Body of Knowledge (PMBOK® Guide), Sixth

Edition, 2017, p. 720 2: PMI, Practice Standard for Project Risk Management, 2009, p. 95 3: Tips and

Tricks for Passing the Risk Management Professional (PMI-RMP …

According to the PMI Risk Management Professional (PMI-RMP)® Handbook1, one of the domains of

the PMI-RMP exam is Risk Monitoring and Reporting, which involves tracking identified risks,

monitoring residual risks, identifying new risks, executing risk response plans, and evaluating risk

process effectiveness throughout the project1. The risk manager of the related project should have

reformed the risk monitoring and closing process properly to ensure that the contingency budget is

only used for the intended risks and not for other purposes. The risk manager should have also

communicated the status and outcomes of the risk activities to the relevant stakeholders, such as the

functional manager and the CEO, to avoid any confusion or conflict over the budget

allocation1. Reference: 1: PMI Risk Management Professional (PMI-RMP)® Handbook, page 6.

The risk manager should have ensured a more accurate project work plan and budget to prevent the

functional manager from requesting to use the project's contingency budget. A well-planned budget

would have avoided the shortage in the functional manager's department budget.

When initiating a project to incorporate a cybersecurity team, the risk manager should first analyze

the following documents:

·        Industry's standard procedures: Understanding industry best practices and standards is critical

for setting up a cybersecurity team, as these procedures will guide the development of secure

processes and protocols.

·        IT infrastructure, networks, and data information: Analyzing the current IT infrastructure is

essential to identify vulnerabilities, assess risks, and plan for the necessary security measures that

the cybersecurity team will manage.

·        Government laws and regulations: Cybersecurity is a highly regulated area. Understanding the

relevant laws and regulations ensures that the project complies with all legal requirements and

avoids potential penalties.

These documents provide the necessary foundation to assess the risks and develop a comprehensive

cybersecurity strategy  .

The project manager should reassess risks by conducting a new assumptions and constraints

analysis. This will help identify any previously overlooked risks and ensure that the risk register is

comprehensive and up-to-date.

The first element the risk owner should look for in the response plan is to verify that due dates for

the actions have been identified. This ensures that risk mitigation actions are timely and can be

effectively monitored.

After identifying the risks and assigning risk owners, the next step is to develop risk response plans

that describe how to address each risk. The first element that the risk owner should look for in the

response plan is the due date for the actions that are required to implement the response. The due

date is important because it helps to prioritize the risk response activities, monitor the progress of

the risk response, and ensure that the response is executed in a timely manner. The due date also

helps to align the risk response with the project schedule and avoid any delays or conflicts. The other

elements, such as the probability of a secondary risk, the impact on the quality of the components,

and the relationship with the critical path, are also relevant for the risk response plan, but they are

not the first element that the risk owner should look for. Reference: PMI, 2017. A Guide to the

Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Newtown Square, PA:

Project Management Institute, Inc., pp. 407-4081