September 7, 2026 · 7 min read
TL;DR: Eighteen questions in this bank put a project manager in a matrix or functional structure, needing people they do not command. The keyed answers are strikingly uniform: negotiate directly with the peer who holds the resource, reconcile with the person who was not in the room, or analyse whose authority is what before taking anyone's direction. The exam treats missing line authority as the ordinary condition of the job, and it does not accept it as a reason to escalate.
There is a version of matrix-organization advice that goes: you have responsibility without authority, so your real skill is knowing when to invoke the sponsor. This bank does not support it.
We measured the slice. Eighteen question stems name a functional manager, a matrix organization or a functional structure, filed 10 Process, 7 People, 1 in the business-environment slice. Across them, the option that reaches for someone more senior is a distractor almost every time, and the reason is consistent enough to be worth taking into the exam.
It makes you go and negotiate anyway, with your peer.
You are nine months into a one-year agile project in a projectized organization, on track for the upcoming releases, when a functional manager tells you the people committed to your project are no longer available. A newly launched project has taken them. You judge that project to be low priority. Its project manager happens to be the CEO's daughter.
That last sentence is the whole trap. It exists to make escalation feel unwise and to make the passive options feel prudent. The four choices are: ask senior management to formally prioritise the two projects, find out when the resources will free up again, negotiate a revised schedule with the other project manager, or tap the budget reserve to hire contractors.
Negotiating with the other project manager is keyed. The others are not absurd; they are premature. Every one of them is a legitimate move after direct negotiation has been tried and has failed, and picking one first reflects a passive management style rather than a political one. The CEO's-daughter detail changes how uncomfortable the conversation is. It does not change who you are supposed to have it with.
| Situation | Keyed move | The tempting escalation |
|---|---|---|
| Another project has taken your people | Negotiate a revised schedule with that project manager | Ask senior management to prioritise the two |
| A manager disputes a plan agreed in their absence | Walk them through the reasoning and reconcile | Escalate to the sponsor without speaking to them |
| Stakeholders across a client's matrix give conflicting direction | Run a stakeholder analysis and act on it | Follow whoever seems most senior |
| You need extra resources from a functional manager | Use interpersonal skills to influence them | Document the requirement more thoroughly |
A project manager and team agreed a fast-tracking plan last week to recover a schedule slip, and everyone present signed off on the revised sequence. A functional manager who was on leave during that meeting has now seen it and is disputing the changed sequence of their team's work.
The options: tell them the decision is final because the team already agreed, revert to the original schedule until they are brought on board, walk them through the reasoning and reconcile any objection before proceeding, or escalate to the sponsor without discussing it with them first.
The keyed answer walks them through the reasoning. The principle underneath it is worth memorising in its own right: an agreement reached without a stakeholder present is only provisional with respect to that stakeholder. Asserting finality does not make it durable. And reverting the entire plan throws away a recovery decision the rest of the team already validated, which punishes everyone for one person's diary.
Common trap: treating the org chart as an answer key. Asked how to deal with key stakeholders drawn from different parts of a client's matrix organization, three of the four options pick a group to obey: take direction from all the key stakeholders because the work is on their premises, follow management and the key stakeholders because every stakeholder matters, or take direction only from your own supervisor and the client's functional managers. The keyed answer performs a stakeholder analysis and acts on what it shows. In a matrix, interests and authority genuinely differ between stakeholders, so treating them as interchangeable guarantees conflicting direction. The distractors each choose whose voice wins before establishing what any of them actually want.
Not the arithmetic, but the framing of the question does.
A project manager mid-execution is asked by his boss to release one team member to another project. All resources have similar capabilities and each works on one activity at a time, and the stem hands you a schedule network. The question is which activity would be affected least if its resource were released.
The answer is float, worked out normally: three paths run to the end, the longest is the critical path and fixes the duration, and the activity to give up is the one on the path with the most total float. Nothing about the matrix changes the calculation. What the matrix supplies is the reason the question exists at all. In a projectized structure nobody asks you this. In a matrix you get asked constantly, and the professional answer is not to refuse but to know precisely which release costs you nothing.
That is the throughline across all 18. Missing authority is not an obstacle the exam wants you to route around. It is the working environment, and competence looks like negotiating, reconciling and knowing your own float well enough to say yes to the right request.
What does the PMP exam expect when you have no authority over your team? That you negotiate with the person who does, directly and first. The keyed answers across these 18 questions consistently go peer to peer before anything reaches senior management. Lacking formal authority is treated as the normal condition of the role.
If a functional manager pulls my resources, should I escalate? Not first. In the CEO's-daughter question, the keyed answer negotiates a revised schedule with the other project manager. Asking senior management to formally prioritise the two projects is a distractor, and the politically charged detail is there to tempt you into it.
What if someone disputes a decision made while they were absent? Walk them through the reasoning. An agreement reached without a stakeholder present is only provisional with respect to that stakeholder, and reverting the whole plan discards a recovery the rest of the team already validated.
Whose direction do you follow when stakeholders come from different parts of a matrix? None of them by default. The keyed answer performs a stakeholder analysis and acts on what it shows, because interests and authority genuinely differ. Every distractor picks a group to obey rather than understanding the groups.
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, including why the politically loaded detail in a stem is almost always there to move you off the right answer. Start the free 20-question sample — no card, no signup required to try it.
What does the PMP exam expect when you have no authority over your team?
That you negotiate with the person who does, directly and first. Eighteen questions in this bank involve a functional manager or a matrix structure, and the keyed answers consistently go peer to peer before anything reaches senior management. Lacking formal authority is treated as the normal condition of the role, not as an obstacle that justifies escalating.
If a functional manager pulls my resources, should I escalate?
Not first. In a bank question where a newly launched project pulls away committed people and its project manager happens to be the CEO's daughter, the keyed answer negotiates a revised schedule with that other project manager. Asking senior management to formally prioritise the two projects is a distractor, and the politically charged detail in the stem is there to tempt you into it.
What if someone disputes a decision made while they were absent?
Walk them through the reasoning. An agreement reached without a stakeholder present is only provisional with respect to that stakeholder. Telling them the decision is final does not make it durable, and reverting the whole plan discards a recovery the rest of the team already validated.
Whose direction do you follow when stakeholders come from different parts of a matrix?
None of them by default. The keyed answer performs a stakeholder analysis and acts on what it shows, because in a matrix the stakeholders' interests and authority genuinely differ. Every distractor in that question picks a group to obey rather than understanding the groups.