September 7, 2026 · 8 min read
TL;DR: Refusal is keyed 9 times and wrong 24 times across 30 bank questions where an option has the project manager decline, reject or refuse something. The nine that work all apply a decision something else already made: the code of ethics, a signed acceptance, the approved plan, an agreed outcome. The 24 that fail either make a decision that belongs to someone else or make it before the impact is known.
Candidates tend to read refusal as strength. On this exam it is usually a shortcut. The bank measures the move at less than a third keyed, and the split is unusually clean once you ask one question of the stem: has anything already decided this, or would the refusal be the decision?
When the project manager is applying a rule rather than inventing one. The nine keyed refusals in the bank fall into four groups.
The code of ethics has settled it. A client presents the team with a gift at the closing party, and the keyed answer declines it because accepting conflicts with the code of ethics. In a region where corruption is common, a team member proposes paying officials to speed up permits, and the keyed answer refuses the bribe outright. The bank adds one nuance worth learning: when a police officer demands a private payment to guarantee the team's safety, the keyed answer is to decline to pay on your own and take the decision up the chain of command, because safety is in play and the call is not the project manager's alone. Refusing is still right. Refusing alone is not.
A signed record has settled it. A week after formal closure, a client sends a list of requirements they say were not met and asks for them fixed within the original budget. The keyed answer points to the signed acceptance record and declines to reopen closed work on that basis alone. At another closing party the client asks for a couple of extra items, each under a week's work, and the keyed answer declines and carries on closing. New work belongs in a contract amendment or a project of its own.
The approved plan has settled it. A director orders the project manager to suspend all quality reviews so the team can hit milestone dates and earn a client bonus. The keyed answer is two words: decline the request. The explanation is precise about why. The instruction asks the project manager to stop doing something the approved quality management plan requires in exchange for money, and the plan plus the code of ethics outrank the director's preference.
An agreed standard has settled it. A head of coaching asks for a talent-identification module on a safeguarding system. It is a good idea, which is what makes it hard to refuse. The keyed answer weighs it against the agreed outcome with the team, declines on that basis in the open, and refers it where it belongs. A lead developer who is the only person with the right skills is asked for a quick promotional microsite, and the keyed answer talks to the developer about capacity and declines on their behalf if it would compromise the committed work. A scheduler proposes recovering a two-week delay by resequencing an activity that has three weeks of float, and the keyed answer rejects it because the activity is not on the critical path. The refusal is arithmetic, not opinion.
Three patterns account for nearly all 24 distractors.
| Pattern | Example from the bank | What is keyed instead |
|---|---|---|
| The decision belongs to someone else | Rework breaches the cost baseline; reject the request unilaterally | Submit it to the change control board with the quantified impact |
| The impact has not been assessed | Late feature request; decline the request outright | Talk to the development team and present feasible options |
| The no is punitive | A stakeholder keeps raising unplanned changes; formally reject her future requests | Update the engagement plan to match her real level of interest |
The first pattern is the one worth memorising. A project manager who finds a change would exceed the approved cost baseline and rejects it alone makes the same error as implementing it alone. The explanation says so in those words. The same rule catches the brewery project manager who declines a new filler technology to avoid scope creep, when the stakeholders whose baselines would pay for it have never been asked whether they want it, and the project manager who rejects an approved change because its budget looks inadequate, when the client who requested it is the one entitled to fund it, shrink it or drop it.
The second pattern is the reflex the exam punishes most often. A stakeholder wants a feature that would improve the user experience but strain the timeline. Declining to protect the timeline is described in the explanation as defensible, and it still loses to negotiating a simplified version, because refusing outright forfeits available value without testing whether a smaller trade exists. A project manager who cannot make sense of a customer's requirements document is offered declining the project as too ambiguous. The keyed answer asks the customer for clarification. Ambiguity is the customer's to resolve and cheap to resolve now.
Common trap: treating a fixed-price contract as a reason to say no. Mid-sprint, a stakeholder asks for several unplanned features, and the product owner flags that scope is bounded by a signed statement of work. Declining outright because the contract was signed is offered and loses. The keyed answer routes the request through the change process so the contractual and cost impact is assessed and agreed before any commitment. The explanation names the error directly: declining treats the contract as immovable rather than as something that can be formally changed through the right process. The bank offers refusal as the wrong answer more than twice as often as the right one, and this is the shape it takes most: a real constraint used as a reason to stop thinking.
Ask who owns the decision and whether it has been made.
If the stem contains a code, a signed record, an approved plan, or an outcome statement that already rules the request out, the keyed answer applies it, and the refusal is often paired with a next step: refer the request elsewhere, continue closing, take it up the chain. If the stem contains a baseline the request would breach, the decision belongs to the body that owns the baseline, and the project manager's job is to carry the assessed impact there. If the stem contains a request nobody has costed, the keyed answer costs it.
There is one more tell. In the 24 distractors, refusal is nearly always a single move with no sequel. In the nine keyed answers, it is nearly always the first half of a sentence. Decline the gift, because. Decline the request, and carry on closing. Decline on that basis, and refer it where it belongs. That is the difference between a decision and a standard being applied, and it is what this bank's explanations spell out rather than just marking the option wrong.
When is declining a request the keyed answer on the PMP exam? When a standard the project manager does not own has already settled it: the code of ethics on a gift or a bribe, a signed acceptance record at closure, an approved quality plan, or an agreed outcome statement. The refusal applies a decision rather than making one.
When is refusing a change request the wrong answer? When the impact has not been assessed, or when the decision belongs to someone else. A change that breaches a baseline goes to the change control board with its quantified impact; the project manager rejecting it alone makes the same mistake as approving it alone.
Should a project manager ever refuse an instruction from a director or sponsor? Yes, when the instruction asks the project manager to abandon something the approved plan or the code of ethics requires. The bank keys declining a director's order to suspend quality reviews for a bonus. It does not key refusing a sponsor's decision the sponsor is entitled to make.
Is refusing a bribe always enough on its own? Refusing is always right. Whether it is enough depends on what else is at stake. Where a payment demand also affects the team's safety, the keyed answer declines to pay unilaterally and escalates for a decision.
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: Change Control on the PMP Exam: Why Saying No Is Almost Never the Answer and They Signed Off: 2 Keyed, 15 Distractors, and the Signature Never Saves You. Change control and governance tasks are mapped on the Business Environment study page.
Sources: PMI Code of Ethics and Professional Conduct and PMI, 2026 PMP Examination Content Outline.
When is declining a request the keyed answer on the PMP exam?
When a standard the project manager does not own has already settled it: the code of ethics on a gift or a bribe, a signed acceptance record at closure, an approved quality plan, or an agreed outcome statement. The refusal applies a decision rather than making one.
When is refusing a change request the wrong answer?
When the impact has not been assessed, or when the decision belongs to someone else. A change that breaches a baseline goes to the change control board with its quantified impact; the project manager rejecting it alone makes the same mistake as approving it alone.
Should a project manager ever refuse an instruction from a director or sponsor?
Yes, when the instruction asks the project manager to abandon something the approved plan or the code of ethics requires. The bank keys declining a director's order to suspend quality reviews for a bonus. It does not key refusing a sponsor's decision the sponsor is entitled to make.