September 7, 2026 · 8 min read
TL;DR: Meeting options are keyed 29 times and used as distractors 56 times across this bank, which makes "call a meeting" one of the least reliable reflexes you can bring to the exam. The split runs along a clean line. A meeting with a named counterpart and a stated purpose, usually to understand something, tends to be keyed. A wide emergency or brainstorming meeting called before anyone knows the cause tends to be a distractor.
Most trap patterns in this bank are easy to state because the option is nearly always wrong. Overtime is never keyed. Removing a team member is never keyed. Meetings are not like that. They are correct often enough that a blanket rule in either direction will cost you questions.
We counted every answer option in the bank that proposes calling, scheduling, convening, or holding a meeting, workshop, or session. Twenty-nine are keyed. Fifty-six are distractors. The useful work is in telling which is which, and it turns out you can usually do it from the wording of the option alone.
Narrow, named, and aimed at understanding something rather than deciding something.
Look at the keyed ones side by side and the same sentence keeps appearing. Set up a meeting with the stakeholder to understand the concerns. Set up a meeting with the new VP to understand their concerns and add them to the stakeholder register. Hold a one-on-one meeting with the team member to identify any obstacles. Set up a virtual meeting with the government partners to ask how they would like updates delivered. Arrange a meeting with the vendor to discuss the problems.
Every one of those has a specific counterpart and a purpose that is informational. Nobody is being assembled to generate ideas. The project manager has identified who holds the information and is going to that person to get it.
The one-on-one is the sharpest version. Where a team member has reported no progress on a critical task at daily standup for several days running, the option list offers a brainstorming session with the team, a risk assessment meeting, and more detailed progress reports. The keyed answer is a one-on-one with that team member to identify obstacles, and the reasoning is worth memorising: several days of reporting no progress in a public forum usually means the obstacle is something the person will not say in front of the team, whether that is a dependency on someone senior, a skill gap they would rather not admit, or a competing demand from their line manager. The public forum is precisely where you will not learn it.
Because a meeting is the easiest thing to write that looks like action and commits to nothing.
The distractors cluster around three shapes. The first is the emergency brainstorm. A technical obstacle threatens a delivery date, and "Call an emergency meeting with all stakeholders to brainstorm solutions" is on the list; the keyed answer records the problem in the issue log so it gets an owner and a resolution date. A supplier quality problem surfaces that had already been identified as a risk earlier in the project, and "Call an urgent team meeting to brainstorm possible solutions" is offered; the keyed answer refers to the risk register for the response that was already analysed and approved. In both, a plan or an artefact already exists, and the meeting proposes to reinvent it from scratch under time pressure.
The second shape is the single all-hands meeting standing in for individual engagement. Stakeholders disagree on a project's objectives and approach, and one option holds a single general meeting with all of them to review a list of activities; the keyed answer identifies the root causes of the disagreement first, because people protecting different interests do not reconcile by being seated together. After a communications overhaul where each stakeholder group's needs have already been established individually, "Hold a single meeting to announce the new approach to all stakeholder groups at once" is a distractor, and the keyed answer updates the communications management plan so the arrangement is recorded somewhere durable.
The third shape is convening the wrong people. A developer hits ambiguity in a feature's acceptance criteria and one option calls a meeting of the steering committee. Acceptance criteria are the product owner's statement of what done means, so the keyed answer collaborates with the product owner. The meeting was not wrong in principle. The invitation list was.
Common trap: "The situation is urgent, so an emergency meeting must be the right level of response." Urgency in the stem raises the temperature, not the answer. In the client-threat scenario where a major client leaves an angry voicemail weighing cancellation, "Set up an emergency meeting with your sponsor to decide how to respond" is a distractor, and so is phoning the sponsor to report the threat and ask how to proceed. The keyed answer reviews the delivered work against the acceptance criteria and gathers details on exactly what disappointed the client, because managing the client is the project manager's own responsibility. This bank puts the urgent-feeling meeting next to the useful step on purpose and explains why it loses, rather than just marking it wrong.
Read five features of the option: who is invited, what the stated purpose is, whether a plan or register already holds the answer, the timing language, and how many parties genuinely have to decide.
| Feature of the option | Usually keyed | Usually a distractor |
|---|---|---|
| Who is invited | A named person or group who holds the information | All stakeholders, the whole team, a steering committee |
| Stated purpose | To understand, to ask, to clarify, to identify obstacles | To brainstorm, to announce, to gather collective input |
| What already exists | Nothing yet; the meeting is how you find out | A risk register, an issue log, a plan, or a known owner |
| Timing language | First, before deciding | Emergency, urgent, immediately, all at once |
| Number of parties who must decide | One counterpart, or a genuine multi-party decision | Everyone, as a way of avoiding choosing |
That fourth row has a real exception, and it is instructive. Emergency sessions are keyed when the decision genuinely belongs to several parties at once. A data-centre relocation is due to cut over this weekend when, on Friday afternoon, the backup verification fails and the images turn out to be corrupt. The outage window is announced, the vendor crew is booked, the migration team is standing by. "Call an emergency planning session before taking any corrective action" is the keyed answer there, because losing the backup removes the ability to undo the migration, which changes the risk profile of every remaining option and involves the infrastructure team, the vendor crew and the migration team simultaneously. The distractors are the ones that pick a direction alone: start building an alternative backup, postpone the cutover, or run it with extra monitoring.
Compare that with the emergency brainstorms that lose. The difference is not urgency, since both are urgent. It is whether the meeting is where the decision has to be made, or whether it is a way of not yet making one.
So the question to ask is: what will I know at the end of this meeting that I do not know now, and could I have found it out from one person? If a single named counterpart could have told you, go to them. If a plan already recorded the answer, read it. If neither is true and several parties must decide together, the meeting is the answer.
Is calling a meeting a good or bad answer on the PMP exam? Both, depending on the shape of the meeting. Across this bank, meeting options are keyed 29 times and appear as distractors 56 times. Meetings with a named person and a stated purpose, usually to understand something, are frequently keyed. Broad emergency or brainstorming meetings called before anyone knows the cause are usually distractors.
Why is an emergency all-stakeholder brainstorm so often wrong? Because it substitutes group activity for the specific next step. In one bank scenario a technical obstacle threatens a delivery date; "Call an emergency meeting with all stakeholders to brainstorm solutions" is offered, and the keyed answer records the problem in the issue log so it gets an owner and a resolution date.
When is an emergency meeting actually the keyed answer? When the decision genuinely belongs to several parties at once and time is short. In one scenario a data-centre cutover is hours away and the backup images turn out to be corrupt, involving the infrastructure team, the vendor crew and the migration team. "Call an emergency planning session before taking any corrective action" is keyed there.
Why does a one-on-one so often beat a team meeting? Because the information you need is usually something one person will not say in front of the group. Where a team member has reported no progress at standup for several days, the keyed answer is a one-on-one to identify obstacles. The obstacle is often a dependency on someone senior or a skill gap they would rather not admit publicly.
PMP Practice's 2,141 questions are certified against PMBOK 8 and the July 2026 ECO, and every wrong answer is explained, not just marked wrong, so you learn why the meeting option was written the way it was. Start the free 20-question sample. No card, no signup required to try it.
Related reading: The Communications Plan covers where these conversations get recorded, and Daily Standup: What Belongs There covers the meeting the exam expects you to keep narrow. The People domain study guide maps these to the 2026 ECO tasks.
Source: PMI, PMP Examination Content Outline.
Is calling a meeting a good or bad answer on the PMP exam?
Both, depending on the shape of the meeting. Across this bank, meeting options are keyed 29 times and appear as distractors 56 times. Meetings with a named person and a stated purpose, usually to understand something, are frequently keyed. Broad emergency or brainstorming meetings called before anyone knows the cause are usually distractors.
Why is an emergency all-stakeholder brainstorm so often wrong?
Because it substitutes group activity for the specific next step. In one bank scenario a technical obstacle threatens a delivery date; 'Call an emergency meeting with all stakeholders to brainstorm solutions' is offered, and the keyed answer records the problem in the issue log so it gets an owner and a resolution date.
When is an emergency meeting actually the keyed answer?
When the decision genuinely belongs to several parties at once and time is short. In one scenario a data-centre cutover is hours away and the backup images turn out to be corrupt, involving the infrastructure team, the vendor crew and the migration team. 'Call an emergency planning session before taking any corrective action' is keyed there.
Why does a one-on-one so often beat a team meeting?
Because the information you need is usually something one person will not say in front of the group. Where a team member has reported no progress at standup for several days, the keyed answer is a one-on-one to identify obstacles. The obstacle is often a dependency on someone senior or a skill gap they would rather not admit publicly.