September 8, 2026 · 7 min read
TL;DR: Email appears in twenty-six options in this bank and is keyed three times. The three keyed cases all reach an identified group with a specific fact that needs to exist in writing: a corrected cost share sent to everyone who got the wrong one, a status summary that precedes a meeting request, a weekly update on impacts and benefits. The twenty-three distractors use email where the stem calls for a conversation, and the explanations reject them on that basis rather than on any general dislike of the channel.
Nobody fails a PMP question because they think email is bad. They fail it because email is the answer that always looks defensible: it is documented, it is efficient, and it reaches everyone. This bank offers that reasoning twenty-three times and keys it three.
When a defined group needs a defined fact, and the written record is part of the point.
The beekeeping cooperative record is the cleanest. A funding update emailed to sixty members stated the cooperative would meet eighty per cent of the fit-out cost when the agreed share is fifty. Two members have already committed to expanding their hives on the strength of it. Keyed is email everyone who received the update with the corrected share and what it now costs them.
The explanation says why that beats the alternatives, and each alternative is instructive. Waiting for the scheduled month-end update leaves the wrong figure working for another three weeks. Speaking only to the two members who declared their plans leaves the other fifty-eight deciding on it unseen. Agreeing a future checking process fixes the next update and does nothing about this one.
The keyed answer matches the channel to the harm. The wrong figure went out by email to sixty people, so the correction goes out by email to the same sixty people, and it says not just the right number but what it costs each of them.
Because it is offered as a way of not having the conversation.
Sort the distractors and they fall into four groups:
| What the email option does | Bank example | What is keyed instead |
|---|---|---|
| Replaces a decision forum | Moving the substantive decisions to email | Fix the forum, do not route around it |
| Addresses a group to reach one person | A group email stressing standards without naming anyone | Speak to the individual privately |
| Defers an answer | Promise to email the information later | Answer, or say when and why |
| Substitutes broadcast for engagement | Regular email updates and reports to keep everyone informed | Two-way engagement suited to the stakeholder |
The group-email pattern is worth its own look. A message to the whole team stressing the importance of meeting standards without naming anyone is a distractor in this bank, and it is a real management habit rather than an invented one. It fails on two counts at once: the person causing the problem may not recognise themselves in it, and everyone who was not causing the problem now believes they might have been.
Common trap: believing that email's paper trail makes it the safe choice. The bank flatly rejects this in the decision-forum record, where accepting the loss as unavoidable and moving the substantive decisions to email is offered and is wrong. A written trail records what was said. It does not create the conditions in which the right thing gets said, and a decision made over three days of threaded replies is not better documented than one made in a meeting with minutes, it is just slower and harder to reconstruct. The bank's distractors trade on the assumption that documented equals defensible, and its explanations consistently ask a different question: did this channel give the situation what it needed?
The sponsor record teaches that the right answer is often email and something, not email or something.
A finance system rollout is in execution, a run of issues is materially slowing delivery, and a new sponsor has joined recently without yet meeting the project manager. Four options, all of which involve writing to the sponsor:
The last one is keyed. The explanation gives the two-part reasoning: the situation is urgent and the working relationship does not exist yet, so the communication has to establish both. The written summary gives the sponsor the facts before the conversation; asking for an immediate meeting conveys the urgency.
The three distractors each drop one half. Sending reports and waiting has facts and no urgency. Emailing the risk register and urging a response has urgency and no relationship. Inviting the sponsor to a recurring meeting and hoping has neither, and the word hope in the option is the bank telling you so.
Only in what email is competing against.
One record has a team adopting a new collaboration tool, with an option to keep email for major announcements but use the new tool for daily agile interactions. That is a distractor, and it is a distractor that sounds like sensible tool governance.
Another has two teams that agreed on a chat platform, with an option to remind both teams by email that the platform was agreed and is now the expected standard. Also a distractor.
Both fail for the same reason the group-email option failed: they answer a behaviour problem with a broadcast. A team that has drifted back to email has a reason for drifting, and an email announcing that they should stop is unlikely to be the intervention that surfaces it.
The keyed stakeholder-update record shows the other side. Sending stakeholders a weekly email update that includes the project's impacts and benefits is keyed, because there the job genuinely is to keep a wide group informed about something they do not need to negotiate. Same channel, different job, different verdict.
Is email ever the correct answer on the PMP exam? Yes, three times across twenty-six options in this bank. It is keyed when a specific group needs a specific fact and the written record matters: correcting a wrong figure that already went out to sixty members, summarising status for a sponsor before requesting a meeting, and sending stakeholders a weekly update covering impacts and benefits.
Why is email usually a distractor? Because it is offered as a substitute for a conversation the situation actually requires. The bank's distractors move substantive decisions to email, send a group message about a performance problem without naming anyone, promise to email information later instead of answering, and set up regular email updates in place of engagement that needs to be two-way.
When does the bank key email plus something else? The sponsor record is the clearest. A new sponsor has never met the project manager and delivery is materially slowing. Keyed is emailing a summary of status and key concerns and requesting an immediate face-to-face meeting. The email carries the facts and the meeting request carries the urgency; neither alone is keyed.
Does push communication mean email is wrong? No. Push communication is a legitimate method, and a weekly stakeholder email covering impacts and benefits is keyed in this bank. What makes an email option wrong is not that it pushes, it is that it pushes where the stem needs a response, a negotiation, or a private conversation.
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 two options differ only in whether anyone has to reply. No card, no signup required to try it.
Is email ever the correct answer on the PMP exam?
Yes, three times across twenty-six options in this bank. It is keyed when a specific group needs a specific fact and the written record matters: correcting a wrong figure that already went out to sixty members, summarising status for a sponsor before requesting a meeting, and sending stakeholders a weekly update covering impacts and benefits.
Why is email usually a distractor?
Because it is offered as a substitute for a conversation the situation actually requires. The bank's distractors move substantive decisions to email, send a group message about a performance problem without naming anyone, promise to email information later instead of answering, and set up regular email updates in place of engagement that needs to be two-way.
When does the bank key email plus something else?
The sponsor record is the clearest. A new sponsor has never met the project manager and delivery is materially slowing. Keyed is emailing a summary of status and key concerns and requesting an immediate face-to-face meeting. The email carries the facts and the meeting request carries the urgency; neither alone is keyed.
Does push communication mean email is wrong?
No. Push communication is a legitimate method, and a weekly stakeholder email covering impacts and benefits is keyed in this bank. What makes an email option wrong is not that it pushes, it is that it pushes where the stem needs a response, a negotiation, or a private conversation.