September 8, 2026 · 7 min read
TL;DR: Executive appears in forty-three options in this bank and is keyed five times. The distractors split into two mirror-image errors: handing the executive authority the role does not carry, such as direct backlog access or selecting requirements outright, and trying to have the executive removed, blocked or escalated over. The keyed answers treat the executive as a stakeholder who needs a legitimate route and an accurate picture, which is a harder answer than either.
An executive who reaches past the process is one of the most realistic scenarios on this exam, and it produces one of the most reliable wrong-answer pairs. Half the candidates give the executive what they want. The other half try to get them stopped. The bank keys neither.
Agreeing a route, with both people in the room.
A research and development executive drops into an agile team's area from time to time and tells them which features are urgent. At the sprint review the product owner is dismayed to find the team has been working on those features. Four options:
Keyed is the third, and the explanation rejects the other three individually. Backlog access bypasses the product owner's accountability for what the team builds. Change requests are the predictive mechanism rather than the agile one. Escalation is a later resort once collaboration has been tried.
Note what the keyed answer does not do. It does not tell the executive their priorities are wrong, and it does not tell the product owner to accommodate them. It fixes the missing thing, which is an agreed path by which an executive's priority becomes a decision the product owner has made.
Because deference reads as respect, and the bank knows it.
The pattern shows up across domains. Have the executive team make all the decisions. Give the executive access to add items to the backlog directly. Have the chief executive select the requirements from all the department leaders' lists. Each of these is a distractor, and each one would be perfectly comfortable to defend in a real meeting.
| Distractor | Authority it hands over | Who actually holds it |
|---|---|---|
| Have the executive team make all the decisions | Every project decision | Distributed by role and governance |
| Give the executive backlog access | Ordering of the team's work | The product owner |
| Have the chief executive select the requirements | Requirements prioritisation | The stakeholders, through a defined method |
| Ask the executive to raise a change request per item | The agile intake route | The product owner, via the backlog |
The last row is the subtle one. Asking an executive to raise change requests sounds like process discipline, and in a predictive context it might be. In the agile stem it is wrong because it imports a predictive mechanism into a delivery approach that already has an intake route, and it does so in a way that is likely to feel to the executive like being sent away with a form.
Common trap: treating the executive as an obstacle rather than a stakeholder. Escalate to upper management so that the executive stops interfering with the team is offered by name in this bank and rejected by name, with the explanation placing escalation as a later resort once collaboration has been tried. The framing inside that distractor is the giveaway: an executive with a view about which features matter is not interfering with the team, they are a stakeholder whose input is arriving by the wrong door. The bank's wrong answers regularly encode a hostile framing into an otherwise reasonable action, and its explanations name the framing rather than only marking the action wrong.
Correct it with the evidence, to the person who said it.
A telecoms provider has piloted an AI assistant against its billing-enquiry backlog for a quarter. The assistant handles a set of well-defined enquiry categories, roughly two in five of the volume, and refers everything else to a human agent. The executive who funded it has told the leadership team the backlog problem is solved and agent headcount can come down. The team is two iterations from release.
Keyed is showing the executive, by enquiry type, what the pilot handled and what it referred, and agreeing what the release will change.
The explanation is unusually direct about the stakes: every week that claim stands, more decisions are taken on it, including decisions about people's jobs. The pilot data is the correction, because it says precisely which enquiry types the assistant closes and which it hands on.
The distractors are all recognisable organisational behaviour. Continue to release and let the first quarter of live volume show what the assistant actually does. Extend the model to cover the referred types before release so the executive's claim holds. Add the referral rate to the weekly status report the leadership team already receives.
That last one deserves attention because it is the one most people would actually do. It puts the true number in front of the right audience. It is still wrong, because a sweeping verbal claim to a leadership team is not corrected by a line item in a recurring report, and the decision about headcount will be taken long before anyone reads it.
More often than the distractors suggest, which is why the pattern is not simply avoid executives.
The bank keys delivering a status report to the executive team as the purpose of a particular communication. Secure executive buy-in appears as a legitimate objective. What separates these from the distractors is direction: information flowing to an executive so they can exercise their own authority is normal, while decisions flowing from an executive into places their authority does not reach is the defect.
Two useful checks under exam pressure. First, ask what the executive is being asked to decide, and whether that decision belongs to their role. Second, ask whether the option removes a person from the conversation, because in this bank the answer that removes someone is almost never the keyed one.
What does the PMP exam expect when an executive bypasses the process? That you fix the route rather than the incident. In the bank's clearest record, an executive drops into an agile team's area and tells them which features are urgent. Keyed is bringing the executive and the product owner together to agree how work reaches the team. Giving the executive direct backlog access, routing them through change requests, and escalating to stop them are all distractors.
Is escalating over an executive ever keyed? Rarely, and never as a first move. The bank offers escalate to upper management so that the executive stops interfering with the team and rejects it, with the explanation noting escalation is a later resort once collaboration has been tried. The executive is a stakeholder with a legitimate interest, not an obstacle to be removed.
What happens when an executive states something the evidence does not support? You correct it with the evidence, in front of the person who said it. The bank keys showing the executive, by enquiry type, what an AI pilot handled and what it referred, and agreeing what the release will change. Adding the referral rate to a weekly status report is offered and rejected, because a claim already made to a leadership team is not corrected by a metric buried in a report.
Do executives have authority over the backlog? Not directly. The product owner is accountable for what the team builds, and the bank rejects giving an executive backlog access precisely because it bypasses that accountability. What the executive is entitled to is a route: an agreed way for their priorities to reach the team through the person who owns the ordering.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 Exam Content Outline, with every wrong answer explained, not just marked wrong. Start the free 20-question sample and see how often a wrong answer is the one that removes somebody from the room. No card, no signup required to try it.
What does the PMP exam expect when an executive bypasses the process?
That you fix the route rather than the incident. In the bank's clearest record, an executive drops into an agile team's area and tells them which features are urgent. Keyed is bringing the executive and the product owner together to agree how work reaches the team. Giving the executive direct backlog access, routing them through change requests, and escalating to stop them are all distractors.
Is escalating over an executive ever keyed?
Rarely, and never as a first move. The bank offers escalate to upper management so that the executive stops interfering with the team and rejects it, with the explanation noting escalation is a later resort once collaboration has been tried. The executive is a stakeholder with a legitimate interest, not an obstacle to be removed.
What happens when an executive states something the evidence does not support?
You correct it with the evidence, in front of the person who said it. The bank keys showing the executive, by enquiry type, what an AI pilot handled and what it referred, and agreeing what the release will change. Adding the referral rate to a weekly status report is offered and rejected, because a claim already made to a leadership team is not corrected by a metric buried in a report.
Do executives have authority over the backlog?
Not directly. The product owner is accountable for what the team builds, and the bank rejects giving an executive backlog access precisely because it bypasses that accountability. What the executive is entitled to is a route: an agreed way for their priorities to reach the team through the person who owns the ordering.