September 7, 2026 · 6 min read
TL;DR: 17 question stems in the bank describe stakeholders or teams resisting a change. Of the 12 answer options built on the word, exactly one is keyed, and it is the one that goes directly to the resisters and asks. Planning around resistance, escalating it, incentivising past it, and waiting for it to subside are all offered, and all wrong.
Resistance questions look like they are testing empathy. They are testing whether you know that resistance has reasons, and that the reasons live inside the people resisting rather than in your analysis of them.
Take the veterinary practices moving to a shared clinical-records system, with senior vets resisting. Four options:
| Option | Verdict |
|---|---|
| Work out from outside what is behind the resistance, then write a change-management plan around those conclusions | Distractor: reaching conclusions from outside is guesswork |
| Engage the resisting vets directly, set out what the change gives them, correct what they have misunderstood | Keyed |
| Enlist supportive practices to bring pressure on those that do not | Distractor: goes around the resisters rather than to them |
| Add resistance strategies to the stakeholder engagement plan | Distractor: a plan cannot be written before the cause is known |
The same shape holds for a team pushing back against trunk-based development. Keyed: explain what the change is expected to achieve and how it contributes to the project's success. Mandating compliance produces surface conformance and buries objections worth hearing. An incentive buys behaviour without changing conviction and splits the team into adopters and holdouts. Waiting for resistance to fade leaves the critical path in the hands of people working against the change.
And again with department heads quietly telling staff to keep using the old spreadsheets. Keyed: meet them and walk through why the change is happening and what it means for their teams. A power/interest grid is offered and rejected as a planning tool for deciding who to engage, not a response once resistance is visible and the individuals are already named.
Common trap: picking the artefact. Across this vein the bank offers a change-management plan, an engagement plan update, a communications management plan, a power/interest grid, and a documented current-state/future-state workflow. Every one of them is a distractor, and the bank flags each by name for the same reason: they describe how people would be told about a change, which is not the same as having been included in it. If an option produces a document about the resisters instead of a conversation with them, it is the wrong answer.
Two exceptions are worth holding.
The first is a risk that was already identified. In one item, internal resistance to an organisational change programme was identified during planning with an agreed response. When a logistics manager's supervisor formally asks for a delay, the keyed answer is to carry out the planned risk response. Root cause analysis is offered and explicitly rejected as the right move only for a risk nobody had anticipated. The resistance conversation already happened, at planning time.
The second is where the question asks what should have been done at the start rather than what to do now. In a software-adoption item, holding one-on-one sessions to understand individual resistance is described in the explanation as the strongest distractor and exactly right once resistance exists, but the question asks what would have prevented it, so the keyed answer is the demonstration that never happened. Read the tense of the question. "What should the project manager have done initially" changes which correct-shaped answer is correct.
No, and this is the item that proves how far the pattern goes. A pharmaceutical manufacturer must add a batch-traceability step before a regulatory inspection, and the team objects that it will slow production. A regulatory requirement is not negotiable, so you might expect enforcement to be keyed.
It is not. The keyed answer explains why the step is required and what non-compliance would cost the organisation. Escalating outsources a conversation the project manager should be holding. Enforcing without explanation produces exactly the box-ticking that inspections are designed to detect. Even when you have every right to insist, the bank still keys the explanation.
What is the keyed response to stakeholder resistance on the PMP exam? Engage the resisting people directly to find out why, explain what the change gives them, and correct whatever they have misunderstood. The bank keys this shape repeatedly and rejects planning, escalating, incentivising, and waiting.
Why is updating the stakeholder engagement plan wrong? Because a plan cannot be written before the cause is known. The bank offers adding resistance strategies to the engagement plan as a distractor in the same item where engaging the resisters directly is keyed.
Is resistance ever handled by escalation? Only when it was already identified as a risk with a planned response, in which case you execute the plan. Escalating so senior management can enforce the change is offered several times and keyed zero.
Where do resistance questions sit in the 2026 ECO? Split between Business Environment and People, concentrated in supporting organisational change and engaging stakeholders. Business Environment tripled in weight in July 2026, so this vein carries more marks than it used to.
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, which is what makes a 1-keyed, 11-distractor pattern visible at all. Start the free 20-question sample — no card, no signup required to try it.
Related reading: Mandate, Enforce, Insist: 7 Keyed, 24 Distractors on the Authority Reflex and Supporting Organizational Change: What the PM Owns When the Org Shifts Mid-Project. Domain context is on the Business Environment study page.
What is the keyed response to stakeholder resistance on the PMP exam?
Engage the resisting people directly to find out why, explain what the change gives them, and correct whatever they have misunderstood. The bank keys this shape repeatedly and rejects planning, escalating, incentivising, and waiting.
Why is updating the stakeholder engagement plan wrong?
Because a plan cannot be written before the cause is known. The bank offers adding resistance strategies to the engagement plan as a distractor in the same item where engaging the resisters directly is keyed.
Is resistance ever handled by escalation?
Only when it was already identified as a risk with a planned response, in which case you execute the plan. Escalating so senior management can enforce the change is offered several times and keyed zero.