Why is it important to assess and document risk categories against updated risk data?

To ensure proper classification and reporting of risks

To assign a numerical probability to each risk

To calculate the expected monetary value of risks

To determine the risk owner for each risk

What is the primary purpose of documenting risk triggers?

To identify the root cause of every risk

To determine the risk owner for each risk

To enable early detection and response to risks

To assign a probability and impact score to each risk

A project has a risk threshold for 'schedule slippage' set at 'more than 3 days'. The project manager receives updated risk data showing that the project's critical path has a buffer of only 2 days. What should the project manager do?

Review the threshold with stakeholders, considering the updated risk data and the project's buffer.

Escalate the issue to the project sponsor immediately.

Lower the threshold to 2 days to align with the reduced buffer.

Keep the threshold at 3 days because it was originally set.

A risk is identified that could delay the project's critical path by three weeks. What is the most important reason to document this potential delay as a risk consequence?

To quantify the impact on the project schedule and prioritize the risk

To assign a probability score to the risk

A financial services project has a risk threshold for 'fraud losses' set at 'any amount above $10,000'. The compliance officer wants to lower the threshold to '$5,000' because of new regulatory scrutiny. The project manager is concerned that a lower threshold will trigger too many investigations, straining resources. What is the most appropriate action?

Lower the threshold to $5,000 to comply with the new regulatory scrutiny.

Set the threshold to $7,500 as a compromise.

Conduct a structured review of the threshold, involving the compliance officer and project team, to balance regulatory requirements and resource constraints.

Keep the threshold at $10,000 because it was originally approved.

PMIRisk Management Professional

Domain 2Objective 3

Task 3 Document Risk Triggers and Thresholds Based on Context/environment PMI-RMP Practice Questions (Page 4)

Part of the Risk Identification domain, which accounts for 23% of the PMI-RMP exam. PMI does not publish an official question count, but from its 230-minute exam (~90–155 total, ~21–36 in this domain), expect 5–9 from this objective — we provide 27 practice questions to prepare you well beyond it. (estimate)

27questions here

6free pages

5concepts

23%of the exam

Questions 16–20

16foundation · easy
Why is it important to assess and document risk categories against updated risk data?
Select an answer first
17foundation · easy
What is the primary purpose of documenting risk triggers?
Select an answer first
18application · medium
A project has a risk threshold for 'schedule slippage' set at 'more than 3 days'. The project manager receives updated risk data showing that the project's critical path has a buffer of only 2 days. What should the project manager do?
Select an answer first
19foundation · easy
A risk is identified that could delay the project's critical path by three weeks. What is the most important reason to document this potential delay as a risk consequence?
Select an answer first
20expert · hard
A financial services project has a risk threshold for 'fraud losses' set at 'any amount above $10,000'. The compliance officer wants to lower the threshold to '$5,000' because of new regulatory scrutiny. The project manager is concerned that a lower threshold will trigger too many investigations, straining resources. What is the most appropriate action?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to PMI-RMP

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by PMI. “PMI-RMP” is a trademark of its owner, used for identification only.