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 project manager is identifying risks on a project and decides to use a risk checklist to gather historical data accumulated from similar projects.
With several different historical project files to choose from, which two pieces of information should the project manager include in their risk checklist? (Choose two.)
- A . Budget variance data from previously completed projects.
- B . Project scope and cost management plans from previous projects.
- C . Lessons learned from similar completed projects.
- D . Previous project risks that may be relevant to this project.
- E . Stakeholder analysis metrics from projects with similar risk profiles.
CD
Explanation:
A risk checklist is a tool for identifying risks based on historical information and knowledge from similar projects. It is a list of potential risk sources or categories that can be used to prompt the project team to consider possible risks that may affect the project. A risk checklist should include information that is relevant and useful for identifying risks, such as lessons learned from similar completed projects and previous project risks that may be relevant to this project. These two pieces of information can help the project manager to learn from past experiences and avoid repeating the same mistakes or overlooking the same threats or opportunities. A risk checklist should not include information that is not directly related to risk identification, such as budget variance data from previously completed projects, project scope and cost management plans from previous projects, or stakeholder analysis metrics from projects with similar risk profiles. These pieces of information may be useful for other aspects of project management, such as planning, monitoring, or controlling, but they are not helpful for identifying risks on a project.
Reference: PMI. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) C Sixth Edition. Chapter 11: Project Risk Management, p. 397. 5
Lessons learned and previous project risks are valuable sources of information for creating a risk checklist. They provide insights into potential risks that may impact the current project and help the project manager develop appropriate risk responses. Budget variance data, project scope and cost management plans, and stakeholder analysis metrics, although useful, are not directly related to risk identification. (Reference: Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK® Guide) C Sixth Edition, Section 1 1. 2)
An organization with a large computer network identified a potential cyber security threat. Although certain measures were implemented to avoid the risk, the cyber security threat occurs. The measures were partially successful and a new unforeseen risk emerges .
What should the risk owner do?
- A . Develop an efficient network protection solution quickly to mitigate the risk.
- B . Escalate the case to the risk manager and wait for their instructions.
- C . Conduct an analysis to determine the root cause of the failed response.
- D . Apply a work around to eliminate or mitigate the impact of the threat.
D
Explanation:
According to the PMBOK Guide, one of the tools and techniques for the implement risk responses process is root cause analysis. Root cause analysis is a technique that focuses on identifying the fundamental reason for the occurrence of a problem or a risk. By conducting a root cause analysis, the risk owner can determine why the implemented measures were only partially successful and what caused the new unforeseen risk to emerge. This can help the risk owner to identify and implement more effective risk responses, as well as to update the risk register and the risk report with the new information1.
Reference: PMBOK Guide, 6th edition, pages 452-453, 474-4751; PMI-RMP Exam Content Outline, 2015, page 8.
When approving the risk contingency budget for a project, the CEO notices each team has a different approach to report risks and their impacts. The CEO decides to create a new centralized risk management function to help resolve the problem.
How does centralizing the risk management function help resolve the problem?
- A . Enhance the process of identification of different Individual project risks.
- B . Allows monitoring the impact against the overall project risk exposure.
- C . Establishes risk sources and ownership for trigger monitoring.
- D . Creates a single repository for all project risk documents.
B
Explanation:
Centralizing the risk management function enables the organization to have a consistent approach to reporting risks and their impacts. This allows for better monitoring of the impact against the overall project risk exposure, which helps in making informed decisions and allocating resources effectively.
According to the PMI-RMP Exam Content Outline1, one of the tasks in the domain of risk governance is to “establish and maintain a centralized risk management function to support the project and organizational objectives”. A centralized risk management function can help resolve the problem of inconsistent risk reporting by providing a common framework, methodology, and standards for risk management across the organization. One of the benefits of centralizing the risk management function is that it allows monitoring the impact of individual project risks against the overall project risk exposure, as well as the organizational risk appetite and tolerance. This can help the CEO and other senior management to make informed decisions and allocate resources accordingly. Therefore, the best answer is B.
Reference: 1: PMI-RMP Exam Content Outline, page 6.