SSM Supporting ART Events Practice Question
As the Scrum Master for Team Golf, you are facilitating the team's preparation for the upcoming PI System Demo. The team has completed all their stories for the Iteration, but during a dry run, you notice that the integration with another team's component fails intermittently due to an environment configuration mismatch. What should you do first?
⚠ Common exam trap
The trap here is thinking that documenting the issue or proceeding anyway is sufficient, when the Scrum Master should actively facilitate resolution of the integration problem.
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
✓
Work with the other team's Scrum Master to resolve the environment configuration mismatch before the demo.
The System Demo must run in an integrated environment that accurately represents the system. When an integration issue like an environment configuration mismatch is detected, the Scrum Master should collaborate with the other team's Scrum Master to resolve it before the demo. This ensures the demo provides valid feedback. Ignoring, canceling, or merely documenting the issue does not address the immediate need for a working demo.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Cancel the team's portion of the System Demo and reschedule for the next Iteration.
Why it's wrong here
Canceling the demo deprives the ART of valuable feedback and hides a real integration issue. The System Demo is a critical event for inspecting the integrated system. Rescheduling to the next Iteration delays problem resolution and violates the cadence. The Scrum Master should seek to fix the issue, not avoid the demo.
- ✗
Document the configuration mismatch as a risk in the team's backlog and continue with the dry run.
Why it's wrong here
Documenting the issue is good, but it does not resolve the immediate problem before the demo. The Scrum Master should take action to fix the environment, not just record it. The System Demo is imminent, and a known integration failure should be addressed now. Merely logging it as a risk does not fulfill the Scrum Master's responsibility to facilitate a successful demo.
- ✗
Proceed with the demo and hope the intermittent failure does not occur during the actual event.
Why it's wrong here
Hoping the failure does not occur is risky and unprofessional. The System Demo is meant to provide reliable feedback, and intermittent failures indicate a real integration problem. Ignoring it could lead to a failed demo and loss of stakeholder confidence. The Scrum Master should address the issue proactively rather than leave it to chance.
- ✓
Work with the other team's Scrum Master to resolve the environment configuration mismatch before the demo.
Why this is correct
The System Demo requires an integrated environment that mirrors production. An intermittent failure due to configuration mismatch is an integration issue that must be resolved for an accurate demo. Collaborating with the other team's Scrum Master is the most direct way to fix the environment and ensure the demo reflects the true system state.
Visual reference
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.