SSM Supporting ART Events Practice Question
During the Scrum of Scrums (SoS) meeting, a Scrum Master from Team Beta reports that they have a dependency on Team Gamma for an API that is critical for their current iteration goal. Team Gamma's Scrum Master is not present. What should the Scrum Master do first?
⚠ Common exam trap
The trap here is escalating or altering plans before attempting direct follow-up, when the immediate step is to make the dependency visible and coordinate.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Record the dependency on the program board and follow up with Team Gamma's Scrum Master after the SoS.
In the Scrum of Scrums, dependencies are made visible. When a team's representative is absent, the Scrum Master should record the dependency on the program board and follow up with the missing team's Scrum Master afterward. This ensures the dependency is tracked and addressed without disrupting the SoS, and it maintains the collaborative spirit of the ART.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Escalate the issue to the Release Train Engineer immediately during the SoS to force Team Gamma's attendance.
Why it's wrong here
Escalating immediately to the RTE may be premature, as the Scrum Master can first follow up directly with Team Gamma's Scrum Master. The SoS is intended for team-level coordination; the RTE should be involved if the dependency cannot be resolved. Taking a collaborative approach before escalating preserves the teams' autonomy and fosters a problem-solving culture.
- ✗
Instruct Team Beta to work on other backlog items until Team Gamma is available to provide the API.
Why it's wrong here
While reprioritizing work might be a temporary measure, it does not address the dependency itself. The Scrum Master's first action should be to make the dependency visible and follow up with Team Gamma's Scrum Master. Simply shifting work could delay the critical integration and affect the iteration goal, and it may lead to further misalignment across the ART.
- ✗
Ask Team Beta to proceed without the API and adjust their iteration goal accordingly.
Why it's wrong here
Adjusting Team Beta's iteration goal without first attempting to resolve the dependency undermines the team's commitment and may not be necessary. The Scrum Master should facilitate coordination to secure the API, rather than prematurely changing the goal. This approach also avoids masking the dependency issue, which could impact other teams and the ART's overall delivery.
- ✓
Record the dependency on the program board and follow up with Team Gamma's Scrum Master after the SoS.
Why this is correct
The Scrum of Scrums is a coordination meeting where dependencies are surfaced. If a team's representative is absent, the Scrum Master should capture the dependency on the program board and then directly follow up with the missing team's Scrum Master to ensure it is addressed. This maintains transparency and keeps the dependency visible for tracking and resolution.
About these practice questions
Courseiva writes every SSM question from scratch — 385 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Scaled Agile exam blueprint
This SSM practice question is part of Courseiva's free Scaled Agile certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SSM exam.