PMI PMI-RMP Practice Exams
Last updated on Oct 22,2026- Exam Code: PMI-RMP
- Exam Name: PMI Risk Management Professional
- Certification Provider: PMI
- Latest update: Oct 22,2026
A risk manager is confident that they have identified and quantified the risks and opportunities for a project.
When presenting their work to management, on what areas should the risk manager focus? (Choose two.)
- A . Risks that are tied to the success of the organization
- B . Risks as they apply to the organization’s overall risk management philosophy and strategic ambition
- C . Huge opportunities that possibly bring an additional 30% return for 10 projects in the next year
- D . Risks related to cost that will impact the major projects that are currently in the execution phase
- E . Risk mitigation actions that will require work from stakeholders
AB
Explanation:
According to the PMBOK Guide, 6th edition, Section 1 1.1. 3.1, Enterprise Environmental Factors, one of the factors that can influence the Plan Risk Management process is the organization’s risk attitude, appetite, tolerance, and thresholds. These terms describe the degree of uncertainty that an organization is willing to accept in pursuit of its goals, and how it approaches, operates, and responds to risk. Therefore, when presenting their work to management, the risk manager should focus on the risks that are tied to the success of the organization, and the risks as they apply to the organization’s overall risk management philosophy and strategic ambition. These aspects can help the management to understand the alignment of the project risks with the organizational objectives and values, and to make informed decisions about risk responses. The other options are less relevant or too specific for a management presentation, and may not reflect the organization’s risk attitude or priorities.
Reference: PMBOK Guide, 6th edition, Section 1 1.1. 3.1, Enterprise Environmental Factors1 The risk manager should focus on risks that are directly tied to the success of the organization and those that align with the organization’s risk management philosophy and strategic ambition. This will ensure that management is informed about the most relevant risks and opportunities for the project.
During a project progress meeting, a project team member is concerned that one of the risks has triggered several other low-level risks. These risks should be responded to quickly or there will be severe consequences for the project deliverables .
What should the risk manager do?
- A . Update the watchlist.
- B . Initiate a risk response when these risks occur.
- C . Address only the high-priority risk.
- D . Perform a risk urgency assessment.
D
16 1. A project manager of an IT company is assigned to a project whose schedule may be delayed due to a lack of resources to conclude the backlog activities. The project manager decides to hire additional developers to reduce the project’s technical debt and meet the project deadline.
What should the risk manager advise the project manager to do to address this situation?
A risk manager administered a pre-workshop risk survey in preparation for the upcoming workshop. The workshop invitees participated in the survey and submitted many risks encompassing all project phases and risk areas. The risk manager sorts risks by similarities and categories for the workshop .
What should the risk manager do next to visually organize the risks?
- A . Develop an affinity diagram
- B . Perform the analytical hierarchy process
- C . Perform a SWOT analysis
- D . Assign probability and impact
A
Explanation:
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.
Reference: PMBOK Guide, 6th edition, pages 397-399, 414-415, 431-432, 441-442; PMI-RMP Exam Content Outline, 2015, page 7.
A risk manager is reviewing documentation for a project following a risk planning workshop with project stakeholders and team members. Several items have been identified on the risk log that would be detrimental to project success, but the associated triggers cannot be managed by the organization and are unlikely to occur.
Which response should the risk manager recommend for these risk items?
- A . Mitigate
- B . Accept
- C . Enhance
- D . Exploit
B
Explanation:
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 stakeholders 1. 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.
Reference: 1: PMI Risk Management Professional (PMI-RMP) ® Examination Content Outline, page 102: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) C Sixth Edition, page 4363: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) C Sixth Edition, page 437.
A risk manager of a complex project has identified a risk and believes a deeper understanding of the source and likelihood is necessary .
How should the risk manager proceed?
- A . Develop and employ an Ishikawa diagram
- B . Analyze the assumptions and constraints
- C . Perform a review of project documents
- D . Create prompt lists for expert interviews
A
Explanation:
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.
Reference: The Standard for Risk Management in Portfolios, Programs, and Projects, page 72; PMBOK Guide, 6th edition, page 398.
The scope of a large mobile network deployment project includes equipment to be furnished by the customer. The risk manager is concerned that the equipment delivery might be delayed, causing additional delays in the project.
What should the risk manager do?
- A . Follow up on the schedule and assess the best course of action if any delays are detected.
- B . Ensure the equipment constraint is well-documented and manage it as a high-impact project risk.
- C . Raise the issue with the project sponsor so it can be handled as a sales or contractual matter.
- D . Obtain a signed commitment from the customer that equipment will be delivered on time.
A project that was in the execution phase for the last six months was put on hold and was eventually cancelled after numerous scope related challenges. It was decided to re-plan the scope and divide the project into multiple projects to have better insight into end objectives. As part of the project start up. the project manager is developing the risk planning for the project.
What three artifacts should the project manager consult or review during this process? (Choose three.)
- A . Project contracts
- B . Lessons learned registers from analogous projects
- C . Risk register
- D . Risk management plan
- E . Code of regulations
ABD
Explanation:
The project manager should consult or review project contracts, lessons learned registers from analogous projects, and the risk management plan to develop an effective risk planning for the project.
According to the PMBOK® Guide, the risk management plan is one of the key inputs for the plan risk management process, which is the first process in the project risk management knowledge area. The risk management plan describes how risk management activities will be structured and performed throughout the project. It includes information such as the methodology, roles and responsibilities, budget, timing, risk categories, definitions of risk probability and impact, probability and impact matrix, revised stakeholders’ risk tolerances, reporting formats, and tracking (page 409). Therefore, option D is the correct answer.
The project contracts are also an important input for the plan risk management process, as they may
contain terms and conditions that can create or affect various project risks. For example, contracts may include clauses related to penalties, incentives, warranties, intellectual property rights, termination, force majeure, arbitration, indemnification, etc. The project manager should review the project contracts to identify any potential sources of risk and plan appropriate responses (page 410). Therefore, option A is the correct answer.
The lessons learned registers from analogous projects are another valuable input for the plan risk management process, as they provide historical information and knowledge that can help the project manager identify and analyze risks, as well as plan risk responses. The lessons learned registers may contain information such as the risks that occurred, the root causes of the risks, the risk triggers, the effectiveness of the risk responses, the residual and secondary risks, the risk owners, the risk ratings, the risk trends, etc. The project manager should consult the lessons learned registers from similar or comparable projects to learn from past experiences and avoid repeating mistakes (page 411). Therefore, option B is the correct answer.
The risk register is not an input for the plan risk management process, but an output. The risk register is a document that contains the list of identified risks, their causes, potential responses, and other relevant information. The risk register is created during the identify risks process, which is the second process in the project risk management knowledge area. The risk register is then updated and refined throughout the project as more information becomes available and new risks emerge (page 414). Therefore, option C is incorrect.
The code of regulations is not an input for the plan risk management process, but a type of enterprise environmental factor. Enterprise environmental factors are the conditions, not under the control of the project team, that influence, constrain, or direct the project. The code of regulations refers to the rules and standards that govern the project’s industry, domain, or sector. The code of regulations may affect the project’s scope, schedule, cost, quality, resources, communications, procurement, and risk management. The project manager should consider the code of regulations when planning risk management activities, but it is not an artifact that needs to be reviewed or consulted (page 38). Therefore, option E is incorrect.
Reference: PMBOK® Guide, pages 38, 409-411, 4141
During project execution, a project manager invites the stakeholders to a risk review meeting. During this meeting, a vendor highlights that the mitigation plan for a schedule risk has generated an additional risk.
What should the risk manager do first?
- A . Update the new risk in the risk register.
- B . Plan responses for the new risk.
- C . Passively accept the new risk.
- D . Add the new risk to the watch list.
A
Explanation:
The risk manager should first update the risk register with the new risk identified by the vendor. This will help in keeping track of all the risks associated with the project and facilitate the subsequent planning and management of the risks.
The risk manager should update the new risk in the risk register, which is a project document that records the details of all identified risks, including their description, category, cause, probability, impact, and response strategy. Updating the risk register is the first step to acknowledge the existence of the new risk and to document its characteristics and potential effects on the project objectives. The risk register can then be used as an input for the Plan Risk Responses process, where the risk manager can develop appropriate actions to address the new risk.
Reference: PMI, A Guide to the Project Management Body of Knowledge (PMBOK® Guide), Sixth Edition, 2017, p. 397, 44 1.
A project team has completed the risk response plan for a newly identified major project risk. Some team members argue the plan does not totally eliminate the risk, considering the effort required to implement it, and feel the planned response should be thrown out altogether .
What should the risk manager do in this situation?
- A . Accept the response because there are no secondary risks were identified.
- B . The response plan should be discontinued and the risk should be accepted and dealt with if it occurs.
- C . Accept the residual risk as it is compatible with the organization’s risk appetite.
- D . All identified risks must be addressed because they might significantly impact the project if they occur.
A risk management professional is currently facilitating the risk planning process with the project team. To increase the breadth of considered risks, the team wants to include high-level and strategic project risks.
What should the risk management professional do next?
- A . Perform a sensitivity analysis to the higher-level aggregate activities
- B . Develop a risk breakdown structure (RBS) identifying the potential risk categories
- C . Conduct a strengths, weaknesses, opportunities, and threats (SWOT) analysis
- D . Perform a base line Monte Carlo simulation to address overall threats to project objectives
C
Explanation:
A SWOT analysis is a risk identification technique that helps to identify high-level and strategic project risks by examining the internal and external factors that may affect the project objectives. A SWOT analysis involves listing the strengths, weaknesses, opportunities, and threats of the project, and then analyzing how they may impact the project positively or negatively. A SWOT analysis can help to uncover potential risks that may not be obvious from other techniques, such as prompt lists, interviews, or brainstorming12
Reference: 1: PMI Risk Management Professional (PMI-RMP) ® Handbook, page 10 2: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) C Seventh Edition, page 1 1. 2.2.1