The build server has been down for two days. The developers have raised it in every daily scrum. The project manager has dutifully recorded it in the issue log and moved on. By the exam's standards, that project manager is failing — because noting an impediment is not removing it. Servant leadership questions live in this gap between acknowledging a problem and taking ownership of it, and with the People domain at 33% of the exam layered over a majority-agile question set, you will meet them again and again.
Servant leadership on the exam is not a personality style. It's a set of observable behaviors: clear obstacles personally, protect the team's focus, amplify the team's voice, grow people's capabilities, and facilitate decisions instead of making them all — while staying engaged and accountable. Three behaviors carry most of the questions.
Impediment removal: act, don't relay
The exam's implicit ladder: first, act within your own authority immediately. Second, collaborate directly with whoever controls the blockage. Only third — when the obstacle genuinely exceeds your reach or crosses a governance threshold — escalate, and even then with impact data, not blame. The most seductive distractor is "escalate to the sponsor," offered one rung too early. The second most seductive is passive tracking: log it, monitor it, raise it at the next meeting. Logs don't unblock teams.
Scenario 1. A pharmaceutical IT team cannot start integration testing because the infrastructure group hasn't provisioned the test environment promised two weeks ago. The sprint goal is now at risk. What should the project manager do?
- A. Record the delay in the risk register and monitor it
- B. Escalate to the sponsor to force the infrastructure group to prioritize the request
- C. Meet the infrastructure lead directly, explain the sprint impact, and agree on a provisioning date
- D. Instruct the team to build mocks and continue as if the environment existed
Answer: C. Direct, collaborative problem-solving with the blocking party is the servant leader's first real move. A is observation dressed up as action. B skips the conversation that usually solves it — escalation is a later rung, not the first. D mitigates the symptom and can be a sensible parallel step, but it leaves the impediment standing, which is why it's the runner-up and not the answer.
75 free questions, scored against the new domain weights. No card required.
Shielding: take the hit yourself
Shielding means intercepting disruption before it reaches the team — without becoming a wall that blocks legitimate stakeholder access. The pattern: the project manager has the uncomfortable conversation at the source, and new work gets routed through the backlog and the product owner rather than whispered to individual developers. What shielding never means: telling a junior team member to go push back on an executive themselves.
Scenario 2. A vice president repeatedly pulls an agile team's only database specialist into unrelated "quick favors" mid-sprint. The sprint goal is at risk for the second consecutive sprint. What should the project manager do?
- A. Ask the specialist to quietly decline the VP's requests
- B. Raise the pattern with the VP directly, show the impact on the sprint goal, and route future requests through the product backlog
- C. Escalate the VP's behavior to the PMO for a governance ruling
- D. Rebalance the sprint plan each time so the disruption is absorbed
Answer: B. The leader absorbs the political risk personally and converts invisible side work into visible, prioritizable backlog items. A pushes the conflict down onto the least powerful person in it. C jumps to governance before a direct conversation has been tried. D normalizes the disruption and silently taxes the team every sprint.
Empowerment vs. abdication: the line the exam draws
"Let the team decide" is correct when the decision sits in the team's domain — technical approach, task ownership, how to meet the sprint goal. But the exam distinguishes empowerment from abdication. Empowerment means delegating the decision with context, guardrails, and continued support. Abdication is "you figure it out" followed by absence. There's a mirror-image trap too: fake empowerment, where the leader delegates, dislikes the outcome, and overrides it. Watch for the option where the leader structures the decision and stays in the room without taking the pen.
Scenario 3. Two senior engineers have deadlocked for a week over building versus buying an integration layer, and the team asks the project manager — who lacks deep technical expertise — to just decide. What should the project manager do?
- A. Choose the cheaper option to protect the budget
- B. Refer the question to the enterprise architecture board
- C. Facilitate the team to agree on decision criteria, run a short timeboxed spike on each option, and decide together with data
- D. Tell the engineers the decision is theirs and move on to other work
Answer: C. The decision belongs to the team, but a servant leader adds structure — criteria, a timebox, cheap experiments — and stays engaged until it resolves. A imposes a decision on the weakest possible basis. B outsources a decision that sits within the team's authority. D is the abdication distractor: technically "empowering," practically abandonment of a stuck team.
The thread through all three
Every correct answer above has the same spine: the leader moves toward the problem, has the direct conversation, and leaves the team's ownership intact. That spine is also why psychological safety — an explicit 2026 emphasis — keeps appearing: teams only surface impediments early when raising bad news is safe. The option that thanks the messenger and investigates beats the option that finds the culprit.
These scenarios are rarely one-liners on the real exam — they arrive as multi-part situations, which we break down in our case questions guide. And the value system behind the correct options is mapped in the PMI-agile answer pattern. To pressure-test yourself, ExamElephant's free tier gives you 75 scenario questions; whatever you miss returns at 3 and 7 days until the reflex holds.
Paid passes are coming soon
The full 2,100-question bank, timed 180-question mock exams and unlimited tutoring. Leave your email and we'll tell you the day they open. Unsubscribe anytime. Privacy
FAQ
When is escalating actually the right answer?
When the impediment exceeds your authority or crosses a defined governance threshold — and after direct collaboration has been tried or is clearly futile. Escalate with impact data, not accusations.
Is servant leadership only tested in agile questions?
No. It anchors the People domain across all approaches. Predictive stems test the same instincts: direct conversation first, root cause before action, team ownership preserved.
How do I spot the abdication distractor?
Look for delegation with no support attached: no criteria, no timebox, no follow-up, leader exits. Empowerment options almost always include structure or continued availability.
How does psychological safety show up in questions?
Usually after a mistake or bad news: the correct option responds blamelessly, investigates the system, and keeps information flowing. Options that punish or single out the messenger are distractors.