September 8, 2026 · 8 min read
TL;DR: The four threat responses appear together constantly in this bank, and avoidance is the one candidates over-pick. It shows up in 55 answer options and is keyed 8 times. The separator is not severity. Ask whether the risk can still happen to your project after the response is in place: if it cannot, that is avoidance; if it can but is less likely or less painful, that is mitigation; if it can and someone outside the project now carries the consequence, that is transfer; if it can and you carry it, that is acceptance.
Candidates learn the four responses as a list and lose marks on the boundaries between them. The exam rarely asks you to recite the list. It gives you a scenario and asks which one just happened, and the plausible wrong answer is nearly always the neighbouring strategy.
Whether the threat can still reach your project afterwards.
The bank states the test in an explanation about a bridge project on a flood-prone river. The project manager agrees with an expert to halt all bridge construction during hurricane season. Keyed is avoidance, and the reasoning is precise: with no construction under way during the flood-prone month, there is nothing on the river for a flood to damage, so the probability of the threat affecting the project drops to zero rather than merely getting smaller. The explanation then names mitigation as the near miss and describes what it would have looked like: continuing to build with flood defences, protected materials, or a shortened exposure window. The work still happens in the flood season, so the flood can still hit it.
That is the whole discrimination, and it is stated as a rule you can carry into any risk question: the risk cannot occur to this project any more, usually because the project changed what it does or when it does it.
A second record confirms it from the other side. Spotting technical risks in a new wheelchair design, a project manager builds a working prototype first. Avoidance is offered. Keyed is mitigation, and the explanation is one sentence long: building a prototype reduces, but does not eliminate, the probability or impact of the technical risk. The prototype makes the design failure less likely. It does not make it impossible.
The bank's clearest examples map one to one onto the four strategies, and the distractors are always the other three.
| Scenario in the bank | Keyed response | Why not the neighbour |
|---|---|---|
| Product owner removes five uncertain stories from the backlog | Avoid | The exposure is gone with the stories, not reduced |
| Halt bridge construction through hurricane season | Avoid | Nothing is on the river for the flood to damage |
| Build a prototype to test a risky design | Mitigate | The technical risk still exists, just smaller |
| Cross-train a second crane operator | Mitigate | Still depends on a person; probability drops, ownership does not move |
| Contract a standby crane operator for lift day | Transfer | A third party is now obligated to perform the lift |
| Buy insurance against overnight site burglaries | Transfer | The burglary is just as likely; someone else carries the loss |
| Hire a specialist firm to remove hazardous chemicals | Transfer | The work goes to the party equipped to carry it |
The standby-operator record is the sharpest of these, because it puts transfer and mitigation side by side in the same stem and asks which one was chosen over the other. Two options are described: contract a backup operator on standby, or cross-train a second in-house person. Keyed is transfer, because the obligation shifts to a third party who is paid to carry it. The explanation then does the thing that makes this bank useful: it names why mitigation is tempting. Both options share the same goal, keeping the lift from stalling, and confusing the two strategies by their shared goal is exactly the mistake. Cross-training keeps the response inside the project team, so ownership never moves.
The insurance record makes the same point with a cleaner surface. A site prone to overnight burglaries, a risk that cannot be eliminated, a policy bought and nothing else done. Keyed is transference. The explanation rules out avoidance in six words: it would mean changing the plan so the exposure disappears, which the scenario says is not possible.
Common trap: treating avoidance as the responsible answer because it sounds decisive. Across the bank, avoidance-shaped options are keyed 8 times and offered as distractors 47 times, and the wrong ones share a pattern. Avoid the risk by working only in the areas without chemicals loses to hiring a firm that can remove them. Change the design immediately so that any infringement is avoided loses to consulting legal counsel first. Avoid, because contracting a backup removes the single point of failure loses because it misnames a transfer. Each of these gives up something real, and in each case nobody has yet established that the exposure warrants it. The bank flags this pattern by name rather than just marking the option wrong, which is the difference between learning the answer and learning the rule.
When nobody has established what the risk actually is yet.
Two compliance records in the bank make this explicit, and both put a decisive-sounding avoidance in the distractor slot. A gripper design may read on another manufacturer's patent. Change the design immediately so that any infringement is avoided is offered. Keyed is consulting legal experts to understand the implications and explore the alternatives, and the explanation says why: whether a design infringes a patent is a specialist judgement the project manager is not qualified to make, and counsel is also the source of the workable alternatives, from a design change to a licence. Redesigning on a suspicion acts before anyone has established there is an infringement at all.
The second one is further along. A product is 65% complete when legal confirms a patent covers one of its innovations. Keyed is running a cost-benefit analysis and identifying the minimum releasable features that avoid the patented component. Note the shape: this is still an avoidance response in substance, but the keyed answer is the analysis that establishes whether a viable product remains, not the removal itself. Terminating the project immediately is offered and loses because it skips the analysis entirely.
The pattern holds across the risk slice. Naming a strategy is the answer when the stem has already told you what the exposure is. When the stem is still describing a suspicion, the answer is whatever establishes the facts.
What is the difference between avoiding and mitigating a risk on the PMP exam? Avoidance removes the exposure so the risk can no longer happen to your project, usually by changing what the project does or when it does it. Mitigation leaves the exposure in place and reduces its probability or its impact. The test is whether the risk could still occur afterwards. If it could, however unlikely, the response is mitigation.
Is buying insurance risk avoidance or risk transfer? Transfer. Insurance does nothing to stop the event happening; it moves who carries the financial impact to a third party. The bank keys transference for exactly this scenario and offers avoidance as the distractor next to it.
Why is avoidance keyed so rarely compared with how often it appears? Because avoidance is written into distractors as a plausible-sounding overreaction. Removing scope, refusing to work in an area, or redesigning on suspicion all read as decisive, but each one gives up something the project was there to deliver, and the stem usually has not established that the exposure justifies it.
Does cross-training a second person count as avoidance? No. It is mitigation. Cross-training removes a single point of failure, which lowers the probability that the threat occurs, but the work still depends on a person showing up. The bank tests this pairing directly against a standby contract, which is transfer.
PMP Practice's 2,141 questions are certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained rather than just marked wrong. Start the free 20-question sample — no card, no signup required to try it.
Related reading: Risk Responses on the PMP Exam: Check Whether You Already Wrote the Plan and Risk Management: Probability and Impact, Not Just the Matrix. Risk now sits in Business Environment, mapped on the Business Environment study page.
What is the difference between avoiding and mitigating a risk on the PMP exam?
Avoidance removes the exposure so the risk can no longer happen to your project, usually by changing what the project does or when it does it. Mitigation leaves the exposure in place and reduces its probability or its impact. The test is whether the risk could still occur afterwards. If it could, however unlikely, the response is mitigation.
Is buying insurance risk avoidance or risk transfer?
Transfer. Insurance does nothing to stop the event happening; it moves who carries the financial impact to a third party. The bank keys transference for exactly this scenario and offers avoidance as the distractor next to it.
Why is avoidance keyed so rarely compared with how often it appears?
Because avoidance is written into distractors as a plausible-sounding overreaction. Removing scope, refusing to work in an area, or redesigning on suspicion all read as decisive, but each one gives up something the project was there to deliver, and the stem usually has not established that the exposure justifies it.
Does cross-training a second person count as avoidance?
No. It is mitigation. Cross-training removes a single point of failure, which lowers the probability that the threat occurs, but the work still depends on a person showing up. The bank tests this pairing directly against a standby contract, which is transfer.