nerdexam
PMI

PMP · Question #1328

A project team member informs the project manager that a stakeholder is contacting the team member to request status updates. The team member is being distracted by these repeated requests, which are

The correct answer is A. Review this stakeholder's communication requirements.. To address a stakeholder distracting a team member with repeated status requests, the project manager should review the stakeholder's documented communication requirements to ensure appropriate communication channels and frequencies are being followed.

Submitted by andres_qro· Apr 18, 2026Process

Question

A project team member informs the project manager that a stakeholder is contacting the team member to request status updates. The team member is being distracted by these repeated requests, which are interfering with the completion of assigned tasks. What should the project manager do?

Options

  • AReview this stakeholder's communication requirements.
  • BInform the team member to stop sending any further updates to the stakeholder.
  • CIncrease the frequency of updates given to this stakeholder.
  • DRaise this issue to the project sponsor in the next project status review meeting.

How the community answered

(35 responses)
  • A
    80% (28)
  • B
    6% (2)
  • C
    11% (4)
  • D
    3% (1)

Why each option

To address a stakeholder distracting a team member with repeated status requests, the project manager should review the stakeholder's documented communication requirements to ensure appropriate communication channels and frequencies are being followed.

AReview this stakeholder's communication requirements.Correct

The project manager is responsible for managing stakeholder communications effectively. Repeated requests from a stakeholder indicate a potential misalignment between the stakeholder's expectations and the established communication plan. Reviewing the communication requirements for that specific stakeholder will help determine the agreed-upon frequency, format, and content of updates, allowing the PM to realign expectations and protect the team's productivity.

BInform the team member to stop sending any further updates to the stakeholder.

Informing the team member to stop sending updates entirely is confrontational and unprofessional; the issue is the *repeated* and *distracting* nature, not necessarily the updates themselves.

CIncrease the frequency of updates given to this stakeholder.

Increasing the frequency of updates without understanding the underlying issue might exacerbate the problem, as it could reinforce the stakeholder's behavior or lead to more distractions.

DRaise this issue to the project sponsor in the next project status review meeting.

Raising this issue to the project sponsor is an escalation that might be necessary later if direct attempts to manage communication fail, but the first step is for the PM to address it directly by reviewing and potentially adjusting the communication plan.

Concept tested: Stakeholder communication management

Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/communication-management

Topics

#Stakeholder Communication#Communication Management Plan#Communication Requirements#Issue Resolution

Community Discussion

7
Lena V.Lena V.May 9, 2026

A. The PMBOK wants you to check the stakeholder's communication requirements first to see if the requests fall outside the agreed plan. B is too heavy-handed, C rewards bad behavior, and D skips the PM's responsibility to manage the situation directly.

14
Samuel O.Samuel O.May 11, 2026

Agree on A, and in practice flagging the gap between the agreed plan and the new request also gives you the paper trail you need when that same stakeholder escalates to your sponsor two weeks later.

0
Samuel O.Samuel O.Apr 23, 2026

Confirmed A on exam last week. This scenario is classic PMI territory where a stakeholder bypasses the communication plan and goes straight to a team member, which happens all the time in the field when someone feels out of the loop. The right move is always to circle back to the stakeholder engagement assessment and the communications management plan to see what was actually agreed upon, rather than just telling the team member to ignore them or escalating to the sponsor before you have even assessed the gap. Usually the root cause is that the stakeholder's information needs shifted mid-project and the plan was never updated to reflect

1
Wei W.Wei W.Apr 24, 2026

Good call on A, and the stakeholder engagement assessment is exactly where I would start too, though I would also make sure the team member has a simple, agreed-upon response for those moments so they are not left guessing until the plan gets updated.

0
Orla P.Orla P.Apr 27, 2026

A. Check the comms plan first. B is tempting but too harsh without knowing what they agreed to.

1
Wei W.Wei W.May 5, 2026

Picking C. More frequent updates means the stakeholder gets what they need without chasing the team.

-1
Lena V.Lena V.May 5, 2026

A is correct here. The stem is asking about transparency into project artifacts and progress, which is exactly what a shared information radiator provides, while C is about communication frequency, not visibility.

0
Full PMP Practice