September 7, 2026 · 7 min read
TL;DR: Options where the project manager enforces, mandates, insists or demands are keyed 7 times against 24 as distractors across this bank. The keyed cases are all inside the project manager's own accountability. The failures try to exercise authority the role does not carry, or use authority as a shortcut past a conversation.
There is a version of the servant-leadership lesson that candidates over-learn: the project manager is never firm about anything. That version loses questions too, because 7 of these options are keyed and some of them are quite direct.
The rule is not about tone. Across the 2,141 questions here, 31 answer options have the project manager enforce, mandate, insist, demand or require. The seven that work and the 24 that fail divide on a boundary, not on a temperament.
Because compliance and buy-in are different things, and the exam wants the one that survives contact with a deadline.
A software team is pushing back hard against a move to trunk-based development, which the project manager considers essential to meeting the release date. Four options:
| Option | Outcome |
|---|---|
| Explain what the change is expected to achieve and how it contributes to the project's success | Keyed. Buy-in follows understanding |
| Mandate the change and require the team to comply from the next iteration | Surface conformance, and objections worth hearing get buried |
| Offer an incentive to the team members who adopt the new way first | Buys behaviour without conviction, splits the team into adopters and holdouts |
| Proceed and let resistance subside once the benefits become visible | Leaves the critical path in the hands of people working against the change |
Read the second and fourth together. One imposes the change, one ignores the resistance, and both end with the same problem: people who do not believe in the approach doing the work that determines the release date. The mandate does not remove the resistance, it just stops you hearing about it.
The incentive option is worth its own note. It fails for a reason that has nothing to do with money being cheap or expensive: it makes adoption a transaction, so the moment the incentive stops, so does the behaviour. It also creates two classes of team member at exactly the moment you needed one team.
When the thing you are insisting on is yours to insist on.
The keyed cases in the bank cluster around the project manager's own accountability. In one, a project manager insists on regular customer feedback sessions and adjusts the sprint schedule to fit the customer's availability, even at some cost to pace. Feedback cadence is the project manager's to protect. In another, the keyed answer insists that team members attend on the scheduled date, where attendance is a commitment already made.
Compare those with the distractors:
The distinction that runs through all of them: the keyed answers enforce a commitment or a practice the project manager owns. The distractors reach for leverage the project manager does not have, or use force where a reason would have worked.
Common trap: reading "the project manager considers this essential" as authorization. The scenario often tells you the PM is technically right, and candidates take that as licence to impose. Being right is not the same as being empowered, and this bank keys against the imposing option even in scenarios where the change genuinely is necessary. The explanation names why the mandate fails rather than just marking it wrong, which matters here, because "I was correct" is the exact reasoning the distractor is built to reward.
There is one more useful edge. In one question the keyed answer checks how much a stakeholder's role and influence genuinely demand of them, before treating their absence as a problem at all. Sometimes the firmest correct move is to establish that no enforcement was needed.
Why is mandating a change usually the wrong answer on the PMP exam? Because it produces surface conformance and buries the objections that might have been worth hearing. A bank question about a team resisting trunk-based development keys explaining what the change is expected to achieve and offers "mandate the change and require compliance" as a distractor.
Is the project manager ever allowed to insist on something? Yes, when the thing being insisted on is inside the project manager's remit and the alternative would compromise the outcome. In this bank, enforce-and-mandate options are keyed 7 times out of 31, and the keyed cases sit squarely within the PM's own accountability.
What should I do when the team resists a technical change I believe is necessary? Explain what the change is expected to achieve and how it contributes to the project's success. Buy-in follows understanding, and a team that can see how a change serves an outcome they already care about adopts it more reliably than one that was told.
Does offering an incentive fix resistance to change? No, and the bank keys against it. An incentive buys behaviour without changing conviction and splits the team into adopters and holdouts, which leaves you with a compliance problem plus a division problem.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 Exam Content Outline, with every wrong answer explained rather than just marked wrong, so an authority distractor tells you whose authority it was actually borrowing. Start the free 20-question sample with no card and no signup.
Related: Servant Leadership vs. Traditional Project Management and Offering a Bonus: Why Money Is the Wrong Answer to a Morale Question. The domain walkthrough is at /study/people.
Why is mandating a change usually the wrong answer on the PMP exam?
Because it produces surface conformance and buries the objections that might have been worth hearing. A bank question about a team resisting trunk-based development keys explaining what the change is expected to achieve and offers 'mandate the change and require compliance' as a distractor.
Is the project manager ever allowed to insist on something?
Yes, when the thing being insisted on is inside the project manager's remit and the alternative would compromise the outcome. In this bank, enforce-and-mandate options are keyed 7 times out of 31, and the keyed cases sit squarely within the PM's own accountability.
What should I do when the team resists a technical change I believe is necessary?
Explain what the change is expected to achieve and how it contributes to the project's success. Buy-in follows understanding, and a team that can see how a change serves an outcome they already care about adopts it more reliably than one that was told.
Does offering an incentive fix resistance to change?
No, and the bank keys against it. An incentive buys behaviour without changing conviction and splits the team into adopters and holdouts, which leaves you with a compliance problem plus a division problem.