The PMO: 6 Keyed, 23 Distractors, and It Never Does Your Job For You

TL;DR: The PMO appears in 29 of the bank's answer options: 6 keyed, 23 wrong. The keyed ones are all about what the PMO has the authority to do. The wrong ones are almost all about giving the PMO something to do that belongs to the project manager.

Candidates get the PMO wrong in a specific way. They know it exists, they know it sets standards, and they treat it as a general-purpose escape hatch. The bank punishes that at a ratio of nearly four to one.

What does the exam key the PMO for?

Its authority, and only its authority. Two items make this concrete.

The first asks who can sign the project charter, choose three. The answers are the sponsor, the steering committee, and the project management office. The project manager is the one who cannot, because the charter is what grants them their authority in the first place. The PMO is in that list because it can be the body that authorises a project and empowers a project manager.

The second is about PMO types. A colleague mentions the organisation has a substantial directive PMO, and asks what happens next. Keyed: expect the PMO to assign you to a project. A directive PMO sits at the high-control end of the range, managing projects itself and supplying the project managers, who report into it. The strongest distractor has you reviewing the frameworks and templates the PMO mandates, which is what a controlling PMO would have you do. The degree of control is what the label is telling you.

What does PMBOK 8 actually say about PMO types?

PMBOK 8 says there is no universally ideal PMO model, so the question of which type to adopt is the wrong one to ask.

A sponsor standing up a PMO asks which of the standard types to adopt so it is set up correctly from the start. The keyed answer is that there is no universally ideal PMO model, and the organisation should blend characteristics from several and tailor the result to its context.

PMBOK 8 addresses this directly in Appendix X2.4: it names the directive, supportive and agile PMO purely as examples that offer useful insights, not as competing options to rank, and treats them as a palette to combine rather than mutually exclusive paths. The PMOs valued most are the ones that customise their structure to their organisational context instead of adhering rigidly to a predefined type.

Two of the three distractors are the answers a prep course would produce. Adopt a directive PMO because ownership gives it authority. Start supportive and move up to controlling once standards are established. Both treat one model as inherently right, which is precisely what the standard declines to do.

Common trap: reading the PMO as a resource pool or an estimating service. In one item a project manager inside a program has known high-level requirements but uncertain priorities, and one option asks the PMO to estimate the tasks across all the program's projects and issue the plan. It loses, and the explanation is blunt: the PMO does not own this project's estimates. In another, a manager building a team for speed can ask the PMO which resources are available and assign them, and loses to choosing a small co-located team. This bank offers the PMO-as-service-desk option repeatedly, and keys it zero times.

Where does the PMO turn into a distractor?

Whenever the option hands the PMO work the project manager owns. Five examples, and the PMO loses all five.

The comms item is the subtlest. The team followed the PMO's recommended methods and stakeholders are complaining about the volume. Having the sponsor tell them the PMO's methods are standard answers a reasonable objection with authority. The keyed answer establishes where stakeholder needs and organisational needs overlap, runs the change as an experiment, and lets the retrospectives decide. The PMO's standard being a standard is not an argument that it is working here.

There is one genuine exception worth knowing. When a PMO is mid-transformation and has already tailored a framework to the organisation, the keyed answer completes the tailoring sequence: enable per-project tailoring by size and complexity, and implement ongoing improvement. PMBOK 8 gives that sequence its own section. The PMO is keyed there because the item is about the PMO's own work, not about offloading yours onto it.

FAQ

When is the PMO the keyed answer on the PMP exam? When the item is testing what authority the PMO holds. It can sign a project charter, and a directive PMO assigns project managers to projects, because a directive PMO manages the projects itself.

Which PMO type does PMBOK 8 say is best? None. PMBOK 8 names directive, supportive and agile PMOs as illustrative examples rather than options to rank, and says there is no universally ideal model. The bank keys blending characteristics and tailoring to context.

Why is asking the PMO so often a distractor? Because it is usually offered as a way to hand off work the project manager owns, such as estimating this project's tasks or picking its resources. The PMO sets standards; it does not run your project for you.

Is a PMO the same as a steering committee? No, though one bank item lists both as bodies that can sign a charter. A steering committee is a governance body that decides; a PMO is an organisational function that supports, controls, or directs project delivery depending on its model.

Try it yourself

PMP Practice's 2,141 questions are certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained rather than just marked wrong. Start the free 20-question sample — no card, no signup required to try it.

Related reading: Project Governance: Who Decides What, and Where Your Authority Ends and Your Project Sits Inside a Programme: 59 Scenarios Where the Answer Is Sideways, Not Up. Governance is mapped on the Business Environment study page.

Sources: PMI, 2026 PMP Examination Content Outline.

FAQ