September 7, 2026 · 7 min read
TL;DR: Options that contact the customer appear 32 times in this bank as answers. They are keyed 5 times. The keyed five all go to the customer for something only the customer has. The other 27 go to the customer instead of doing work the project manager should have done.
The customer is the reason the project exists, so an option that involves talking to them carries an air of good practice. That is exactly the problem. On this exam, going to the customer is graded on what you go there for, and most of the time the option is offering you a way to skip a step.
We counted every answer option in this bank's 2,141 questions that calls, tells, asks, informs, or notifies the customer or the client, and split keyed from distractor.
| Options contacting the customer | Count |
|---|---|
| Keyed correct | 5 |
| Offered as a distractor | 27 |
The distractors spread across all three domains, which tells you this is not a People-domain quirk. It shows up in scope questions, in closing questions, in procurement questions, and in change control.
Each one goes to the customer for something the project manager could not obtain any other way.
Notice what none of them is. None asks the customer to make the project manager's decision, and none reacts to the customer before establishing the facts.
Common trap: "The customer is unhappy, so the first move is to contact them." Urgency is not the test. Whether they hold what you need is the test. This bank's most instructive example: a major client leaves an urgent voicemail saying they are deeply unhappy with a deliverable and weighing whether to cancel the contract, and they want an immediate response. Calling right away to apologize and promise a personal fix is a distractor. So is calling the sponsor. The keyed answer reviews the delivered work against the acceptance criteria and gathers details on exactly what disappointed the client before responding.
Because expectation and acceptance criteria are different things, and only one of them was agreed. Two bank questions turn on precisely that gap.
One week into the first iteration of a hybrid project, the customer is unhappy. The keyed answer investigates the cause and verifies the deliverables. Using soft skills to persuade the customer that the specifications are met is called out in the explanation as the trap, because it may be factually correct and still be the wrong response. Asking the customer to raise a change request is also a distractor. So is fixing it next iteration. Dissatisfaction that early is information, and its cause is not yet known: the deliverable may fail the spec, or meet the spec while the spec captured the wrong thing, or the expectation may have been set by something outside the requirements entirely. Those three have completely different remedies.
During closing, a deliverable is found not to meet customer expectations. Keyed: review the deliverable's requirements and the customer's acceptance criteria, then proceed accordingly. Meeting the customer to agree a new scope, asking them to raise a change request, and asking the sponsor to help negotiate are all distractors. Each turns an opinion into project work during closing, before anyone has checked whether the opinion is supported.
Two checks, both fast.
First, ask what the option is going to the customer for. Intent, a decision that is theirs, or information about impact are all legitimate. Reassurance, an apology, a negotiation, or a change request are not, at least not as a first action.
Second, ask whether you could answer the question yourself with something already in the project. If the acceptance criteria, the requirements, the scope baseline, or the contract would settle it, the keyed answer is almost certainly the one that checks them. This bank's wrong answers explain themselves on exactly this point rather than just marking you down, which is what makes the pattern portable to scenarios you have not seen.
When is contacting the customer the keyed answer? When the customer holds information nobody else can supply, most often their own intent. Across this bank, options that contact the customer are keyed 5 times against 27 appearances as distractors, and the keyed cases involve asking what an ambiguous requirement means, telling the client what has been found so they can decide, and explaining a constraint impact before acting on their request.
Why is calling an unhappy customer usually wrong? Because it responds before anything is established. In one bank scenario a major client leaves an urgent voicemail threatening cancellation. Calling right away to apologize and promise a personal fix is the distractor. The keyed answer reviews the delivered work against the acceptance criteria and gathers details on what actually disappointed them first.
What is the difference between customer expectations and acceptance criteria? Only one of them was agreed. A bank question set during closing has a deliverable failing to meet customer expectations. The keyed answer reviews the requirements and the documented acceptance criteria before doing anything, because that establishes whether the deliverable is genuinely deficient or the expectation was never in scope.
Should I ask the customer to raise a change request when they are unhappy? Not as a first move. This bank offers that option twice as a distractor, once during an unhappy first iteration and once during closing. Both times it converts an opinion into project work before anyone has checked whether the deliverable actually falls short of what was agreed.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained, not just marked wrong. Start the free 20-question sample - no card, no signup required to try it.
When is contacting the customer the keyed answer?
When the customer holds information nobody else can supply, most often their own intent. Across this bank, options that contact the customer are keyed 5 times against 27 appearances as distractors, and the keyed cases involve asking what an ambiguous requirement means, telling the client what has been found so they can decide, and explaining a constraint impact before acting on their request.
Why is calling an unhappy customer usually wrong?
Because it responds before anything is established. In one bank scenario a major client leaves an urgent voicemail threatening cancellation. Calling right away to apologize and promise a personal fix is the distractor. The keyed answer reviews the delivered work against the acceptance criteria and gathers details on what actually disappointed them first.
What is the difference between customer expectations and acceptance criteria?
Only one of them was agreed. A bank question set during closing has a deliverable failing to meet customer expectations. The keyed answer reviews the requirements and the documented acceptance criteria before doing anything, because that establishes whether the deliverable is genuinely deficient or the expectation was never in scope.
Should I ask the customer to raise a change request when they are unhappy?
Not as a first move. This bank offers that option twice as a distractor, once during an unhappy first iteration and once during closing. Both times it converts an opinion into project work before anyone has checked whether the deliverable actually falls short of what was agreed.