September 7, 2026 · 6 min read
TL;DR: The word "feedback" appears in 64 of the bank's answer options: 19 keyed, 45 wrong. The split is not about whether to seek feedback. It is about the channel. Feedback attached to something people can see and react to gets keyed. Feedback funnelled into a survey, an anonymous box, or a report gets offered as the distractor.
Nobody fails a PMP question by thinking feedback is bad. They fail it by picking the option that collects feedback most thoroughly, when the keyed answer is the one that gives feedback somewhere to land.
Feedback attached to something concrete that a person can see, judge and react to, which then changes the next piece of work.
Look at what the keyed options have in common. Demonstrate the working increments. Have customers test prototypes and incremental releases in the environment the product will be used in. Adopt pair programming together with customer feedback sessions. Ask the team to adopt short feedback loops and continuous improvement. Run a sprint review that walks through the prototype and draws out the client's adjustments.
Every one of them puts a real thing in front of a real person and shortens the gap between their reaction and the next decision. None of them is a mechanism for gathering opinions.
One item makes the reasoning explicit. Several stakeholders have drifted away, rarely contributing input or attending meetings, and you choose two actions. The keyed pair is to visibly value and credit everyone's ideas, and to demonstrate the working increments. The explanation names one cause for each: people stop contributing when their input appears to change nothing, and they stop attending when meetings show no visible progress. Sending a reminder before each meeting is offered and rejected, because stakeholders rarely disengage for want of invitations.
Six options in the bank offer an anonymous channel. All six are distractors.
| Scenario | Anonymous option offered | What the bank keys |
|---|---|---|
| One member dominates the daily scrum | Anonymous feedback system to collect opinions | A private conversation with that person about the effect |
| Junior engineers go quiet in design reviews | Collect input privately, raise it anonymously later | Ground rules inviting questions, and modelling disagreement yourself |
| Assessing individual developer contributions | Anonymous peer surveys on contributions | Define measurable criteria in advance and tell everyone |
The reasoning is consistent across all three. Anonymous feedback denies the person being described any chance to respond, and it rarely changes behaviour. In the design-review item the problem is that juniors do not feel able to speak, and routing their doubts through anonymity accepts that condition instead of fixing it. Anonymity treats a safety problem as a collection problem.
Common trap: reading "we need more feedback" in the stem as a cue to pick the option that gathers the most of it. In the disengaged-stakeholder item the anonymous channel and the meeting reminder are both offered, and both lose to showing people working software. This bank names that pattern in its explanation rather than leaving you to infer it: the distractor gathers, the keyed answer gives the feedback somewhere to land. When two options both involve feedback, ask which one changes what the person sees next week.
Across all three, almost evenly, which is why feedback-shaped options turn up so often. Of the 64 options, the questions carrying them split 32 Process, 30 People, 9 Business Environment, with the heaviest tasks being value-based delivery, leading the project team, and engaging stakeholders.
That spread matters for exam strategy. A feedback-shaped answer is not a "People domain answer" you can rule in or out by the flavour of the scenario. It shows up in a quality question, a scope question, and a team-morale question, and the channel test applies to all three.
What kind of feedback does the PMP exam key? Feedback attached to something concrete and visible: a working increment, a demonstration, a prototype, a short loop that changes the next piece of work. The bank keys 19 such options.
Why are anonymous feedback channels almost always wrong? Anonymous options appear six times in the bank and are keyed zero times. They deny the person being described any chance to respond, and they treat a room where people cannot speak as a collection problem rather than a safety problem.
Is collecting feedback ever enough on its own? No. The bank's distractors repeatedly stop at gathering. Stakeholders disengage when their input appears to change nothing, so the keyed answers pair collection with something visible happening as a result.
Does this apply on predictive projects too? Yes. The demonstration and prototype answers cluster in adaptive scenarios, but the underlying test holds in predictive ones: a storyboard or prototype that stakeholders can adjust and agree is keyed over written requirement documents in an elicitation item, for the same reason.
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.
The Business Environment slice of this vein is smaller but real, and the domain is mapped on the Business Environment study page.
Related reading: Status Reporting on the PMP Exam: What the Report Is For, and Who It Is For and The Stakeholder Engagement Assessment Matrix: Unaware to Leading. The tasks behind these sit on the People domain study page.
What kind of feedback does the PMP exam key?
Feedback attached to something concrete and visible: a working increment, a demonstration, a prototype, a short loop that changes the next piece of work. The bank keys 19 such options.
Why are anonymous feedback channels almost always wrong?
Anonymous options appear six times in the bank and are keyed zero times. They deny the person being described any chance to respond, and they treat a room where people cannot speak as a collection problem rather than a safety problem.
Is collecting feedback ever enough on its own?
No. The bank's distractors repeatedly stop at gathering. Stakeholders disengage when their input appears to change nothing, so the keyed answers pair collection with something visible happening as a result.