September 7, 2026 · 7 min read
TL;DR: The functional manager appears as an answer option in 49 questions in this bank. They are keyed 7 times and offered as a distractor 47 times. Narrow it to options that hand them the problem, phrased as notify, tell, escalate to, or ask the functional manager to resolve it, and the count is 0 keyed against 7 distractors. They are keyed when you need something they control. They are a distractor when you need something you control.
The functional manager is a genuinely useful character for an item writer. They exist in most real organisations, they outrank the project manager in a lot of them, and involving them always sounds like the mature, non-territorial thing to do. That combination makes them one of the most reliably wrong options in the bank.
We swept the bank for lopsided keyed-versus-distractor splits and this one came back near the top: 7 keyed against 47 distractors across 49 records, spread over People, Process and Business Environment. The interesting part is not the ratio. It is that the keyed appearances and the distractor appearances are asking two different questions.
Because in almost every scenario that offers them, the thing that is broken belongs to the project manager, and passing it along is a way of not handling it.
A long-serving team member is deliberately avoiding a newly hired developer from another country. The options are to speak with the senior member privately while making clear that discrimination will not be tolerated, notify the functional manager, look the other way, or reprimand the whole team in the next meeting. It keys the private conversation. Notifying the functional manager is not cruel or reckless, which is exactly why it works as a distractor; it simply moves a team-leadership problem to someone whose job it is not.
A designer hands over a finished document and the project manager notices it is shorter than expected. One option calls the team member's functional manager to confirm the document is correct. The keyed answer checks the deliverable against the scope baseline, and the explanation is worth reading closely: nothing yet establishes that anything is missing, because "shorter than expected" is the project manager's own impression rather than a documented requirement. The functional manager option skips the document that would settle it.
A functional manager who was on leave objects to a fast-tracking plan the rest of the team agreed and signed off. Two of the options push them away, by declaring the decision final or escalating to the sponsor without talking to them first. One capitulates entirely and reverts the schedule. The keyed answer walks them through the reasoning and reconciles the objection before proceeding, because an agreement reached without a stakeholder present is only provisional with respect to that stakeholder.
That last one matters, because it shows the pattern is not "avoid the functional manager." It is about who owns the next action.
Sort the bank's questions by what the option actually asks the functional manager to do, and the split is clean.
| The option asks them to... | Example from the bank | Keyed? |
|---|---|---|
| Resolve a team behaviour problem | Notify the functional manager about avoidance between two members | No |
| Confirm work is correct | Call them to check a deliverable looks right | No |
| Absorb a schedule disagreement | Escalate to the sponsor rather than talk to them | No |
| Supply people you cannot supply | Persuade them to release extra resources | Yes, via influence |
| Lend staff before authorisation exists | Informally lend staff until the charter is signed | No |
| Take over the project manager's own duty | Arrange training for new project staff | No |
Everything in the "no" rows is work the project manager already owns. The one "yes" row is a resource the project manager genuinely does not control, which is the functional manager's actual domain in a matrix organisation.
Even there, the bank tends to key the skill rather than the act. Asked what a project manager needs most to persuade a functional manager to provide extra resources for complex activities, the options offer planning skills, interpersonal skills to influence, interviewing skills, and technical skills. It keys interpersonal skills, because persuading another manager to release people is influence and negotiation, not planning.
Common trap: "The functional manager has authority over that person, so they should handle it." True about the reporting line, wrong about the problem. Authority over somebody's employment is not authority over how project work gets done, and the bank keys the project manager acting inside their own remit in every one of the behaviour, quality and schedule scenarios above. This bank offers the functional manager as a distractor 47 times against 7 keys, which is a strong enough signal that seeing their name in an option is worth a second look before selecting it.
Sometimes, and when it does the question usually says so explicitly rather than leaving you to infer it.
One bank question frames it as a career decision: you are weighing a job at a company with a project-oriented structure, and you have to name a drawback. The options include team members reporting to several bosses, the functional manager holding more authority than the project manager, the team feeling little loyalty to the project, and the team having no functional home to return to. It keys the last one. The middle two are drawbacks of a functional or matrix structure, offered here to catch candidates who recognise the phrases without tracking which structure they belong to.
Another puts a project manager on a client's premises, working alongside stakeholders from different parts of the client's matrix organisation. One option takes direction only from the project manager's own supervisor and the client's functional managers. The keyed answer performs a stakeholder analysis and acts on what it shows, because in a matrix the stakeholders' interests and authority genuinely differ and treating them as interchangeable guarantees conflicting direction.
So the structure changes who holds authority over people. It does not change who is accountable for the project meeting its requirements, and that is the axis most of these questions actually turn on.
Resources are where the functional manager is most legitimately involved, so this is where candidates over-correct and pick them when something else is keyed.
A project manager is choosing three integration engineers and has listed the criteria that matter: availability, cost, relevant experience, and how well each candidate would work alongside the existing team. The options include negotiation with the functional managers, source selection criteria, a responsibility assignment matrix, and multicriteria decision analysis. It keys multicriteria decision analysis, because the question is about the technique for weighing candidates against several criteria at once, not about who to talk to afterwards.
Another describes a team spread across five time zones with the resource management plan still being drafted. One option works with the functional managers to re-source the team from a single location. The keyed answer plans for a virtual team and updates the plan on that basis, because the team is distributed and will stay distributed.
And a sponsor who verbally says to start pulling people in before the charter is signed produces an option asking functional managers to informally lend staff until the paperwork catches up. The keyed answer waits for the signed charter, since that is what grants the project manager authority to draw on organizational resources in the first place.
Working through a run of these, with each wrong option explained rather than just marked wrong, is what makes the distinction automatic: the functional manager is a person you negotiate with for what they control, not a place to put a problem.
When is going to the functional manager the correct answer? When you need something only they control and the ask is a negotiation rather than a handoff, most often resources. Even then the bank usually keys the skill rather than the act: one question asks what a project manager needs most to persuade a functional manager to release extra people, and keys interpersonal skills to influence them.
Why is notifying the functional manager almost always wrong? Because it moves a problem the project manager owns onto someone who does not own it. Narrowed to options phrased as telling, notifying, or asking the functional manager to resolve something, this bank keys them zero times out of seven. Team behaviour, deliverable quality and schedule disagreements are all the project manager's to handle first.
Who arranges training for people assigned to a project? The project manager. One bank question offers HR, the training department, and the functional managers alongside the project manager, and keys the project manager, because the training exists for this project's requirements. The project manager identifies the gap, arranges the training, and funds it from the project's budget.
Does the functional manager have more authority than the project manager? It depends entirely on the organizational structure, and that is often what the question is testing. In a functional or weak matrix organization the functional manager holds more authority over the people. In a project-oriented organization the project manager does, and the recognised drawback there is that the team has no functional home to return to when the project ends.
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, which is how a pattern like this one shows up as a number rather than a hunch. Start the free 20-question sample, no card and no signup required to try it.
When is going to the functional manager the correct answer?
When you need something only they control and the ask is a negotiation rather than a handoff, most often resources. Even then the bank usually keys the skill rather than the act: one question asks what a project manager needs most to persuade a functional manager to release extra people, and keys interpersonal skills to influence them.
Why is notifying the functional manager almost always wrong?
Because it moves a problem the project manager owns onto someone who does not own it. Narrowed to options phrased as telling, notifying, or asking the functional manager to resolve something, this bank keys them zero times out of seven. Team behaviour, deliverable quality and schedule disagreements are all the project manager's to handle first.
Who arranges training for people assigned to a project?
The project manager. One bank question offers HR, the training department, and the functional managers alongside the project manager, and keys the project manager, because the training exists for this project's requirements. The project manager identifies the gap, arranges the training, and funds it from the project's budget.
Does the functional manager have more authority than the project manager?
It depends entirely on the organizational structure, and that is often what the question is testing. In a functional or weak matrix organization the functional manager holds more authority over the people. In a project-oriented organization the project manager does, and the recognised drawback there is that the team has no functional home to return to when the project ends.