SSM Introducing Scrum in SAFe Practice Question
During PI Planning, a team identifies a major technical risk that could block their progress for three iterations. What is the most appropriate action for the Scrum Master to take?
⚠ Common exam trap
Test-takers frequently pick choices that involve ignoring the risk until the iteration starts or handling it strictly within the single team, ignoring the ART-wide ROAMing process during PI Planning.
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
✓
Add the risk to the ART's ROAM board during the PI Planning session.
The Scrum Master must facilitate transparency regarding the risk. In SAFe, risks are managed using the ROAM technique (Resolved, Owned, Accepted, Mitigated). By bringing this to the attention of the ART during the PI Planning 'ROAMing' session, the Scrum Master ensures that leadership is aware and can provide the necessary support or resources to mitigate the issue before it derails the entire Program Increment.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Keep the risk hidden from management to avoid looking incompetent.
Why it's wrong here
Hiding risks is dangerous and anti-Agile. SAFe relies on transparency to enable effective decision-making. If a risk is hidden, the ART cannot plan accordingly, leading to inevitable failure. Proactive communication of risks allows the train to adjust plans and provides leadership the opportunity to resolve or mitigate issues.
- ✓
Add the risk to the ART's ROAM board during the PI Planning session.
Why this is correct
The ROAM board is the standard mechanism for managing risks in SAFe. By adding the risk, it becomes visible to all stakeholders, allowing the ART to collectively decide how to handle it. This ensures that serious impediments are formally tracked and managed rather than ignored or handled in isolation.
- ✗
Ask the team to ignore the risk and hope it resolves itself.
Why it's wrong here
Ignoring risks is a recipe for project failure. Risks that remain unaddressed will eventually manifest as blockers, causing significant delays and loss of value. The Scrum Master's role is to ensure these risks are faced head-on, so the team can develop contingency plans or focus on alternative approaches.
- ✗
Immediately disband the team and reassign them to other projects.
Why it's wrong here
Disbanding a team due to a technical risk is an extreme and unnecessary reaction. Technical risks are a common part of software development. The goal is to address the risk, not to dissolve the team. This reaction would destroy morale and prevent the organization from learning how to overcome challenges.
Visual reference
About these practice questions
This SSM question is part of Courseiva's 385-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.