Sign in
Home/PMI/PMI Risk Management Professional (PMI-RMP)/Free questions

PMI Risk Management Professional (PMI-RMP) — Free Practice Questions

10 free sample questions from a bank of 173, with the correct answers and explanations. No signup required — start practising right now.

1What are common examples used to communicate risk probability and impact?
  • Risk checklist, risk assessment, regression analysis, and assumption and constraint analysis
  • Monitor Risks process, multi-dimensional risk assessment, control chart, and Monte Carlo simulation
  • Probability distributions, sensitivity analysis, modeling and simulation, and probability and impact matrix
  • Monitor Risks process, assumption and constraint analysis, modeling and simulation, and risk register
Answer: C

The short version

C — Probability distributions, sensitivity analysis, modeling. This stem asks about What are common examples used to communicate risk probability and impact?, and only the settled choice fits PMI practice. Signals corroborate C, so this note defends that key.

Key concepts in this question

  • Settled C: Probability distributions, sensitivity analysis, modeling and simulation, and is the response the stem requires.
  • Focus: What are common examples used to communicate risk probability and impact? limits the call to one risk step with distinct inputs and outputs.
  • Framework: PMBOK and the Standard for Risk Management separate identification, analysis, response planning, and monitoring.
  • Trap: distractors reuse a valid tool or reserve at the wrong time, so check timing, ownership, and known versus unknown status.

Why C is correct

Option C states Probability distributions, sensitivity analysis, modeling and simulation, and. It fits What are common examples used to communicate risk probability and impact?, where trigger and timing call for that step. Decisive logic is fit: identified risks use contingency and planned responses with owners, active unidentified issues use workarounds then reassessment, and numeric stems use probability times impact.

Why the others are wrong

  • A. Risk checklist, risk assessment, regression — it suits low priority tracking, not this step.
  • B. Monitor Risks process, multi-dimensional risk — it is valid but answers the wrong process question.
  • D. Monitor Risks process, assumption and constraint — it is valid but answers the wrong process question.

PMI-RMP exam tip

On PMI-RMP, match trigger to tool: registered means contingency and planned response, unregistered active means workaround then review, numbers mean probability times impact, and hold C as Probability distributions, sensitivity analysis, modeling.

2In the country where a project is being executed, customs procedures are complex and change frequently. During the risk identification process, the project team identifies a risk related to delays in customs on substantial equipment that will likely occur. Equipment delays on this project could lead to the project cancellation. How should the probability and impact be characterized for this risk?
  • Low probability/low impact
  • High probability/low impact
  • Low probability/high impact
  • High probability high impact
Answer: D

The short version

D — High probability high impact is the correct characterization. Customs delays are described as likely and cancellation-level, so both dimensions sit at the top end of the scale.

Key concepts in this question

  • Probability assessment: judged likelihood that a specific risk event occurs, informed here by complex procedures that change frequently and a will likely occur statement.
  • Impact assessment: judged severity on project objectives if the risk occurs, informed here by substantial equipment and possible cancellation of the whole project.
  • Probability and impact matrix: tool that combines the two ratings to set priority, where high-high combinations demand urgent response planning and reserves.
  • Risk identification output: a clearly worded risk with cause, uncertain event, and effect, which then flows into qualitative analysis for ranking.
  • High-priority risks: risks that threaten key objectives and therefore justify mitigation, contingency, active monitoring, and senior attention.

Why D is correct

The stem gives both ratings explicitly in plain language. Will likely occur maps directly to high probability under any calibrated scale, because frequency of change plus complexity makes recurrence expected rather than remote. Could lead to project cancellation maps directly to high impact, because cancellation is the most severe schedule, cost, and scope consequence possible. Only the high-high cell captures that combination, so qualitative analysis must place this risk at the top of the register and drive a mitigation plan.

Why the others are wrong

  • A. Low probability low impact contradicts both cues, since neither the frequency warning nor the cancellation consequence supports a low rating.
  • B. High probability low impact keeps the likelihood right but understates impact, because cancellation of the project can never be classed as low impact.
  • C. Low probability high impact keeps the impact right but understates likelihood, because a will likely occur event cannot be scored as low probability.

PMI-RMP exam tip

Link wording to rating: will likely occur means high probability, cancellation or failure to meet objectives means high impact, then pick the matching cell without second-guessing.

3At the completion of a small project, the risk manager performs a risk audit and finds that several identified risks had occurred, and the impact was significantly larger than expected. While the project remained on schedule, the project budget increased by 50%. The project met all risk response milestones and no additional, previously unidentified risks, occurred on the project. Based on this information, what risk management process improvement should the risk manager recommend for future similar projects?
  • Increase frequency of risk management meetings with the project manager.
  • Revise the level of accuracy of probability and impact scores.
  • Document the risk audit report and capture it in the lessons learned database.
  • Expand the use of risk identification techniques.
Answer: B

The short version

Banked answer C is a routine closure step, but it does not fix the diagnosed weakness. Identified risks occurred as expected, yet impact was much larger and budget grew by half, so estimation was inaccurate.

Key concepts in this question

Risk audit reviews effectiveness of risk processes, not just compliance with milestones. Qualitative analysis depends on calibrated probability and impact scales, matrices, and data quality. Lessons learned capture results, but process improvement must target root cause. Here identification worked, response milestones were met, schedule held, yet cost impact was systematically underestimated, which signals analysis accuracy failure.

Why B is correct

B directly addresses the observed gap between assessed impact and realized impact. Revising accuracy means recalibrating impact scales, validating estimation methods, using better historical data, expert judgment, and risk data quality assessment. PMI measures audit success by asking whether impact was as severe as originally thought, and persistent underestimation requires fixing assessment accuracy before the next similar project, not merely filing reports.

Why the others are wrong

A is wrong because more meetings would not correct biased impact estimates when milestones were already met. C is wrong because documenting the audit and filing lessons learned is expected closure work, but it preserves rather than corrects the faulty estimation process. D is wrong because identification was effective, since no unidentified risks occurred, so expanding identification techniques solves a problem that did not occur in this case.

PMI-RMP exam tip

When audit shows known risks happening with larger than expected consequences, choose answers about improving analysis accuracy, scales, and estimation quality. Reserve lessons filing for knowledge capture, not for fixing systematic underestimation.

4The project manager has asked for the P50 estimate for the project schedule. What is the P50 estimate?
PMI Risk Management Professional (PMI-RMP) question 4
  • 75 days
  • 73.5 days
  • 73 days
  • 72.5 days
Answer: C

The short version

C — 73 days is the P50 estimate for the schedule. P50 is the median of the simulated finish distribution, the date with a fifty percent chance of meeting it.

Key concepts in this question

  • P50 and percentiles: P followed by a number denotes the confidence level, so P50 means fifty percent of simulated outcomes finish on or before that date.
  • Monte Carlo schedule simulation: repeated sampling of activity duration ranges produces an S-curve of possible completion dates and cumulative probability.
  • Median versus mean: the median P50 splits the distribution in half and is less pulled by long-tail extremes than the arithmetic mean of 73.5 days.
  • S-curve reading: find fifty percent on the probability axis, move across to the curve, then drop down to the date axis to read the corresponding finish date.
  • Contingency communication: P50, P80, and similar dates help sponsors choose a committed date with explicit risk appetite rather than a single-point guess.

Why C is correct

The settled key selects 73 days as the point where cumulative probability reaches one half on the distribution chart referenced in the question. That matches the definition of P50 exactly, which is the median simulated finish, not the mean and not a higher confidence date such as P75 or P80. Distractors near 73 days test whether the candidate reads the curve precisely instead of averaging values or rounding upward. Choosing 73 days therefore reflects correct percentile interpretation applied to the provided figure.

Why the others are wrong

  • A. 75 days would represent a higher confidence level than fifty percent, adding extra contingency beyond the median and overstating the P50 date.
  • B. 73.5 days looks like a calculated mean or midpoint of inputs, but P50 is read from the cumulative curve as a median, not computed by simple averaging.
  • D. 72.5 days sits below the median and would correspond to less than fifty percent confidence, understating the date needed for an even chance.

PMI-RMP exam tip

When you see Pxx, translate immediately to percent confidence on the S-curve, then read across and down, never average the answer choices.

5A project risk manager is concerned about the low performance of risk management on a mission-critical project. After assessing the situation, the risk manager finds that the communication style may be the main contributor. What could the project risk manager do to adjust the approach to influence team members to improve performance?
  • Use follow-up emails, adopt an open door policy, and ask for feedback.
  • Seek hidden agendas, vent frustrations, and allow others to vent frustrations.
  • Provide continuous support, counseling, build trust, and open communications.
  • Conduct one-on-one meetings, more frequent follow-up meetings, and implement the management by walking around technique.
Answer: D

The short version

D — One-on-one meetings, frequent follow-up, and walking around is the best adjustment. Direct personal engagement rebuilds trust and surfaces communication barriers faster than generic support statements.

Key concepts in this question

  • Communication style and risk performance: how the risk manager interacts shapes whether team members raise risks early, share bad news, and own responses.
  • Management by walking around: informal presence where work happens, observing reality, listening, coaching, and removing obstacles in real time.
  • One-on-one meetings: private conversations that reveal concerns people will not voice in groups, plus hidden constraints and motivation issues.
  • Influence without authority: risk managers rarely control line resources, so frequent follow-up and visibility sustain accountability and momentum.
  • Trust and psychological safety: people report risks only when they believe leaders listen, act fairly, and protect messengers from blame.

Why D is correct

The problem is framed as low risk-management performance driven by communication style on a mission-critical effort, which calls for a change in interaction pattern rather than more policy. One-on-one meetings create a safe channel for honest feedback, frequent follow-ups keep risk actions visible and prevent drift, and walking around shows engaged leadership and catches weak signals early. Together these behaviors directly influence team members to participate, improve ownership, and lift performance, which is why the settled key favors this active, high-touch approach over passive support alone.

Why the others are wrong

  • A. Follow-up emails, open door policy, and asking for feedback are helpful but too passive and inbox-driven to shift behavior on a critical project needing hands-on influence.
  • B. Seeking hidden agendas and venting frustrations models unproductive conflict, erodes trust, and distracts from structured risk ownership and coaching.
  • C. Continuous support, counseling, trust, and open communications sound positive but are vague and generic, lacking the specific cadence and presence that change day-to-day conduct.

PMI-RMP exam tip

For influence and performance issues, choose the most direct and personal intervention, especially one-on-ones plus visible leadership presence.

6A project's risk manager successfully implements the risk management plan and the risk register. Furthermore, the risk analysis and the risk response planning are finalized. All results have been documented, and the project management plan and other project documents have been updated accordingly. What should the risk manager do next?
  • Perform a lessons learned document update with the defined risks.
  • Perform regular reserve analysis to ensure that the assigned risk reserve budgets are sufficient.
  • Perform risk date quality assessments.
  • Perform continuous risk re-evaluation throughout the project life cycle to ensure risk management effectiveness.
Answer: D

The short version

D — Perform continuous risk re-evaluation through the life cycle. Risk management does not end when the first round of analysis and planning is documented.

Key concepts in this question

  • Iterative risk management: risks evolve as work progresses, assumptions are tested, and external conditions shift, so identification and analysis repeat.
  • Monitor Risks process: tracks implemented responses, watches triggers and residual risks, finds new risks, and checks process effectiveness.
  • Risk register as living document: new entries, retired risks, updated probabilities, impacts, owners, and actions keep decisions current.
  • Project management plan updates: approved changes from risk work flow through integrated change control into baselines and subsidiary plans.
  • Effectiveness review: confirming that responses actually reduced exposure and that reserves remain adequate is part of ongoing oversight.

Why D is correct

The stem states that the plan, register, analysis, response planning, documentation, and related updates are all complete, which marks the end of one pass, not the end of the discipline. PMI practice treats risk as continuous because new risks emerge, old risks expire or mutate, and response effectiveness must be verified in execution. Re-evaluation throughout the life cycle ensures the team keeps identifying, reassessing, responding, and communicating rather than filing the register away. That steady cadence is exactly what sustains risk-management effectiveness after the initial setup.

Why the others are wrong

  • A. Lessons learned updates are useful and should be captured, but they are a supporting output, not the primary next discipline that keeps risk control alive.
  • B. Regular reserve analysis is part of monitoring, yet it is narrower than full re-evaluation, covering only budgets while ignoring new risks and response performance.
  • C. Data quality assessment belongs earlier inside qualitative analysis to test understanding of a risk before ranking, not as the overarching next step after planning.

PMI-RMP exam tip

After plan plus register plus analysis plus responses are done, the default next move is monitor and re-evaluate continuously, not close out.

7Very low = 1, Low = 2, Moderate = 3, High = 4, Very High = 5 A project manager must complete a report for a stakeholder who is concerned about the possibility of a funding shortfall. What is the most effective way to explain the risk to this stakeholder?
PMI Risk Management Professional (PMI-RMP) question 7
  • The funding shortage is the lowest ranked/scored risk.
  • The funding shortage is a significant risk.
  • The funding shortage will have a very high impact on the project and is the highest priority.
  • The funding shortage has a very low probability of occurring and is not a concern for the project.
Answer: D

The short version

D — The funding shortage has a very low probability of. This stem asks about Very low = 1, Low = 2, Moderate = 3, High = 4, Very High = 5 A project, and only the settled choice fits PMI practice. Signals corroborate D, so this note defends that key.

Key concepts in this question

  • Settled D: The funding shortage has a very low probability of occurring and is not a concern for is the response the stem requires.
  • Focus: Very low = 1, Low = 2, Moderate = 3, High = 4, Very High = 5 A project limits the call to one risk step with distinct inputs and outputs.
  • Framework: PMBOK and the Standard for Risk Management separate identification, analysis, response planning, and monitoring.
  • Trap: distractors reuse a valid tool or reserve at the wrong time, so check timing, ownership, and known versus unknown status.

Why D is correct

Option D states The funding shortage has a very low probability of occurring and is not a concern for. It fits Very low = 1, Low = 2, Moderate = 3, High = 4, Very High = 5 A project, where trigger and timing call for that step. Decisive logic is fit: identified risks use contingency and planned responses with owners, active unidentified issues use workarounds then reassessment, and numeric stems use probability times impact.

Why the others are wrong

  • A. The funding shortage is the lowest ranked/scored — it confuses a neighboring process with the required one.
  • B. The funding shortage is a significant risk. — it confuses a neighboring process with the required one.
  • C. The funding shortage will have a very high impact — it confuses a neighboring process with the required one.

PMI-RMP exam tip

On PMI-RMP, match trigger to tool: registered means contingency and planned response, unregistered active means workaround then review, numbers mean probability times impact, and hold D as The funding shortage has a very low probability of.

8Which of the following success factors will enhance the Perform Qualitative Risk Analysis process as the risk occurrence gets closer?
  • Agreed-upon definition
  • Iterative analysis
  • High quality information
  • Agreed-upon approach
Answer: D

The short version

D — Agreed-upon approach. This stem asks about Which of the following success factors will enhance the Perform Qualitative, and only the settled choice fits PMI practice. Signals corroborate D, so this note defends that key.

Key concepts in this question

  • Settled D: Agreed-upon approach is the response the stem requires.
  • Focus: Which of the following success factors will enhance the Perform Qualitative limits the call to one risk step with distinct inputs and outputs.
  • Framework: PMBOK and the Standard for Risk Management separate identification, analysis, response planning, and monitoring.
  • Trap: distractors reuse a valid tool or reserve at the wrong time, so check timing, ownership, and known versus unknown status.

Why D is correct

Option D states Agreed-upon approach. It fits Which of the following success factors will enhance the Perform Qualitative, where trigger and timing call for that step. Decisive logic is fit: identified risks use contingency and planned responses with owners, active unidentified issues use workarounds then reassessment, and numeric stems use probability times impact.

Why the others are wrong

  • A. Agreed-upon definition — it confuses a neighboring process with the required one.
  • B. Iterative analysis — it confuses a neighboring process with the required one.
  • C. High quality information — it confuses a neighboring process with the required one.

PMI-RMP exam tip

On PMI-RMP, match trigger to tool: registered means contingency and planned response, unregistered active means workaround then review, numbers mean probability times impact, and hold D as Agreed-upon approach.

9A project team member identifies, but does not document, a risk early in the project, because it is considered to be trivial. This risk occurs later and negatively impacts the project. What could the project manager do to avoid this situation?
  • Conduct team meetings early in the project to ensure team member are familiar with risk identification requirements.
  • Communicate the punishment and rewards policy to the project team during the project kick-off meeting.
  • Provide project team members with access to simulation tools and decision tree diagrams.
  • Provide team members with a risk management prompt list early in the project to ensure risks are not missed.
Answer: A

The short version

A — Hold team meetings early so members understand risk identification requirements. Undocumented trivial risks signal a process and culture gap, not a missing tool.

Key concepts in this question

  • Risk identification discipline: every suspected risk gets recorded regardless of perceived size, because small issues can combine or grow into major impacts.
  • No trivial risk rule: dismissing a risk as trivial at discovery bypasses analysis, so its true probability and impact are never evaluated.
  • Common understanding: the team needs shared expectations on what counts as a risk, how to write it, where to log it, and why early capture matters.
  • Risk culture and accountability: members must feel responsible for raising concerns and safe doing so, with leadership reinforcing the behavior.
  • Preventive enablement: training, ground rules, and kickoff alignment reduce future omissions more durably than adding analytical tools alone.

Why A is correct

The failure was not inability to see the risk but a decision not to document it because it seemed trivial, which later hurt the project when it materialized. Early team meetings that explain identification requirements directly attack that root cause by establishing that all risks are logged, that triviality is decided through analysis rather than gut feel, and that the register is the single home for tracking. That shared understanding prevents silent filtering and builds the habit of capture, which is the precise preventive action the settled key emphasizes for avoiding a repeat.

Why the others are wrong

  • B. Communicating punishment and rewards policy relies on fear or incentives rather than clarity and ownership, and does not teach what or how to document.
  • C. Simulation tools and decision trees support quantitative analysis of known risks but would not have fixed the choice to leave a perceived small risk unrecorded.
  • D. A prompt list helps brainstorm more risks and avoid blind spots, yet the risk was already identified, so the gap was documentation discipline rather than idea generation.

PMI-RMP exam tip

When a known risk was ignored as trivial and not logged, pick the answer that instills document-everything discipline early.

10A project in the execution phase at the customer's site has an issue concerning new parts that do not fit properly into a machine. The site project manager cannot find this high probability risk in the risk register. What action should the site project manager take?
  • Variance analysis
  • Workaround
  • Risk assessment
  • Risk audit
Answer: B

The short version

B — Workaround. This stem asks about A project in the execution phase at the customer's site has an issue, and only the settled choice fits PMI practice. Signals corroborate B, so this note defends that key.

Key concepts in this question

  • Settled B: Workaround is the response the stem requires.
  • Focus: A project in the execution phase at the customer's site has an issue limits the call to one risk step with distinct inputs and outputs.
  • Framework: PMBOK and the Standard for Risk Management separate identification, analysis, response planning, and monitoring.
  • Trap: distractors reuse a valid tool or reserve at the wrong time, so check timing, ownership, and known versus unknown status.

Why B is correct

Option B states Workaround. It fits A project in the execution phase at the customer's site has an issue, where trigger and timing call for that step. Decisive logic is fit: identified risks use contingency and planned responses with owners, active unidentified issues use workarounds then reassessment, and numeric stems use probability times impact.

Why the others are wrong

  • A. Variance analysis — it confuses a neighboring process with the required one.
  • C. Risk assessment — it confuses a neighboring process with the required one.
  • D. Risk audit — it reviews effectiveness, not the immediate trigger.

PMI-RMP exam tip

On PMI-RMP, match trigger to tool: registered means contingency and planned response, unregistered active means workaround then review, numbers mean probability times impact, and hold B as Workaround.

Want the full bank of 173 questions for PMI Risk Management Professional (PMI-RMP)? See all practice exams.