When PMI described the updated PMP exam, it listed managing internal and external customer expectations among the People-domain topics the new version adds, alongside developing a common vision, engaging stakeholders, strategic communication planning, and supporting reporting and governance. Most candidates read that list and quietly file customer expectations under stakeholder engagement.
That is the mistake. Stakeholder engagement questions ask how to bring someone into the project. Expectation questions ask what to do when someone already believes something about the project that is not true. The two call for different first moves, and the exam scores them differently.
Where this sits in the updated exam
The updated exam launched on 9 July 2026. The domain weights are People 33%, Process 41%, and Business Environment 26%, the last of these up from 8% in the previous version. People lost a share of the exam on paper, but the content inside it widened: the domain now reaches past team management into vision, communication planning, reporting, and customer expectations.
So the task is not a footnote. It is one of the places where the People domain now overlaps with governance, and overlapping content is where situational questions get written.
Internal and external customers are not the same problem
The outline pairs the two words deliberately. They fail in different directions.
| Internal customer | External customer | |
|---|---|---|
| Who it usually is | A department, a business owner, a sponsoring function | A paying client, a buyer, an end customer under contract |
| What they control | Priority, people, internal approvals | Money, acceptance, the agreement itself |
| How expectations drift | Informal side conversations, verbal promises, assumed priority | Terms read differently by each side, assumed inclusions |
| What usually goes wrong | Work gets added without anyone calling it a change | Acceptance is refused at the end rather than discussed in the middle |
| First move on the exam | Talk to them, then reconcile with the plan | Talk to them, then reconcile with the agreement |
The last row looks like the same answer twice, and that is the point. The conversation comes first in both cases. What differs is the document you reconcile against, and therefore what you do second.
The pattern expectation questions follow
Almost every one of these items can be worked in five steps.
- Identify whose expectation it is. A sponsor, an internal business owner, and a contracted client are not interchangeable.
- Identify what the expectation actually is, as a statement. "Faster" is not an expectation; "live before the trade show" is.
- Compare it against the baseline, the requirements, or the agreement. This is the step candidates skip.
- Decide whether closing the gap changes scope, schedule, cost, or quality. If it does not, it is a communication problem. If it does, it is a change.
- Record the outcome where the project can see it later.
Step 4 is the hinge. Everything about the right answer depends on which side of it the scenario sits.
Expectation gap versus change request
An expectation gap means someone believes the project will deliver something the plan does not contain, and nobody has agreed to add it. The correct response is to meet, show what the plan says, explain the difference, and agree on what happens next. No change request exists yet, because nothing has been requested in a form the project can evaluate.
A change begins when the customer asks for the difference to be delivered. Then the request goes through the project's change process, gets analyzed for impact, and is approved or rejected by whoever holds that authority.
Candidates lose these questions in two opposite ways. Some pick the answer that raises a change request immediately, before anyone has even confirmed what the customer wants. Others pick the answer that accommodates the customer quietly, absorbing the work to keep the relationship warm. Both skip step 3, and the exam treats both as a failure of the project manager's own responsibility, not as helpfulness.
A third wrong answer is worth naming on its own: escalating to the sponsor or to management as the first action. Escalation is sometimes correct, but it is correct after you understand the gap, not instead of understanding it.
What a question looks like
A typical item sets up something like this. A product has been delivered at the end of the life cycle. The customer says it was not built to their specification. The requirements were signed off earlier in the project, and the delivered product matches them.
Read that and the temptation is to defend the project, because the documentation is on your side. The exam is not asking whether you are right. It is asking what a project manager does next, and the answer that scores is the one that establishes the facts against the agreed requirements with the customer present, then handles what the comparison reveals. Being correct and unheard is not a passing response.
Note also what the scenario was really testing: the failure happened earlier, when acceptance criteria were treated as a signature rather than as something to confirm against along the way. Several questions in this task are written backwards like this, where the best answer addresses a gap that opened months before the scenario's first sentence.
Three traps
- Treating satisfaction as the objective. A satisfied customer is an outcome, not an instruction. Answers that promise satisfaction without reconciling against the plan are usually distractors.
- Confusing the internal customer with the sponsor. An internal business owner may be the customer of the deliverable without holding budget authority over the project. Who receives the product and who approves changes can be two different people.
- Assuming the contract settles it. With an external customer, the agreement governs, but quoting it is not a response. The exam still expects a conversation, a documented interpretation, and a route through the proper process.
How to study it
Work the task through artifacts rather than definitions. For each of the requirements documentation, the requirements traceability matrix, the scope baseline, the change log, and the agreement, answer one question: what expectation does this document pin down, and who agreed to it? Candidates who can say that quickly stop guessing on step 3.
Then practice the split. Take any customer scenario and label it before looking at the options: communication gap, or change. If the labels come easily, the four options sort themselves, because the exam almost never offers two correct answers on opposite sides of that line.
Practice questions on this topic
These are free sample questions from the wayexam.com bank, each with the full explanation. No account is needed.
- A customer initiated a minor scope change and expects this to be completed without delays or additional costs
- A state-of-the-art product was delivered, but the customer claims it was not designed to specification
- Product requirements have not been fully met due to uncertainties about customer acceptance
Related reading on this site: Stakeholder Engagement on the PMP Exam, Plan and Manage Communication, and Develop a Common Vision.
Sources: PMI, "PMP Exam Change: What It Means in 2026" and PMI, "Learn what the new PMP exam, launched in July 2026, means for you".