SAFe SSM · Scaled Agile · Supporting Team Events · Bank updated 2026-09-28
SAFe SSM practice questions: Supporting Team Events
5 free questions from 21 on this area · answer and explanation for each · no sign-up
These 5 questions come from the Supporting Team Events section of our SAFe SSM bank (21 questions on this area, which carries 19% of the real exam). Every question is original, with the correct answer explained and linked to the source it is drawn from.
Free: 6 questions in study mode, no card. All 21 Supporting Team Events questions and the full SAFe SSM bank: $15 one-time.
1/5 · Supporting Team Events · easy
What best characterizes Backlog Refinement in SAFe?
AAn ongoing activity in which the Product Owner and team review, split, and estimate Stories so the Team Backlog is ready for Iteration Planning
BA dedicated, one-time event held only on the final day of the Iteration, where the team re-estimates every open Story in the Team Backlog at once
CA meeting where the Scrum Master/Team Coach alone decides the priority order of Team Backlog Stories to reduce the Product Owner's workload
DAn activity conducted exclusively during PI Planning, where the ART splits and estimates Features for the entire Program Increment
2/5 · Supporting Team Events
A Story planned for the Iteration has its code written, but automated tests are not yet complete, as the Iteration Review approaches. What is the most appropriate approach for the team?
AHave the Scrum Master/Team Coach personally complete the missing tests before the Review so the Story can be shown as done
BDemo the unfinished Story as if it were complete to maintain a positive impression with stakeholders, since it will likely be finished soon
CSkip the Iteration Review entirely for this Iteration, since not all committed Stories were finished and there is little to show
DDemonstrate only the Stories that meet the Definition of Done and be transparent that the incomplete Story will carry forward
3/5 · Supporting Team Events
In SAFe's Flow Metrics, what does Flow Velocity measure for a team?
AThe percentage of time a work item is actively being worked on versus waiting in a queue, tracked over time
BThe number of PI Objectives achieved by the whole Agile Release Train in a Program Increment, compared against the plan
CThe number of work items a team completes per Iteration without any rework, tracked over time as a quality trend
DThe number of Stories or story points a team completes per Iteration, tracked over time to see throughput trends
4/5 · Supporting Team Events · hard
A team's Flow Velocity looks strong and stable across several Iterations, yet stakeholders report that individual Stories still take a long time to move from 'started' to 'done.' Which combination of Flow Metrics should the Scrum Master/Team Coach investigate together to explain this apparent contradiction?
AIteration Goal achievement and PI predictability, since a falling share of goals met is the clearest SAFe indicator of how long each Story took to move from started to done
BFlow Time, how long items take end-to-end, and Flow Efficiency, the ratio of active time to total time, since high WIP or queues inflate Flow Time and depress Flow Efficiency even while throughput stays stable
CEstimated versus actual story points per Story, since Flow Metrics do not apply to team-level delivery in SAFe and point overruns directly reveal which of the team's Stories were slowest to move from started to done
DFlow Velocity and Flow Distribution, since a stable velocity combined with a shifting distribution shows which types of work are taking too long to move from started to done
5/5 · Supporting Team Events · hard
A Scrum Master wants the team to use data during its Iteration Retrospective to drive process improvement. The team's velocity has been flat for three Iterations while a sister team on the same ART reports a higher velocity. Which use of metrics best aligns with SAFe guidance for this Retrospective?
AUse Flow Efficiency data to set individual performance targets for each team member, and agree those targets during the Retrospective to lift velocity in the next Iterations.
BReplace the Iteration Retrospective with a review of the team's flow metrics dashboard, since the metrics alone show where the process needs to improve.
CExamine the team's own flow metric trends, such as Flow Time and Flow Load over recent Iterations, to find where work is getting stuck in its own process.
DRank the team's velocity against the sister team's velocity on the same ART to find which team is more productive, and adopt the practices of the faster team next Iteration.
Answer: C. SAFe explicitly cautions against comparing velocity across teams because story-point sizing is relative and team-specific, making cross-team comparisons misleading and potentially harmful to trust and collaboration. Instead, SAFe promotes Flow Metrics (Flow Velocity, Flow Time, Flow Load, Flow Efficiency, Flow Predictability, Flow Distribution) as a more objective, systemic way for a team to inspect its own process trends during the Iteration Retrospective and identify real bottlenecks to address.
Source: the SAFe 6.0 framework (framework.scaledagile.com) + the official SAFe Scrum Master course content — Supporting Team Events
Other SAFe SSM areas
The same kind of free sample for every other section of the SAFe SSM bank:
Practise SAFe SSM with instant feedback
6 free questions in study mode · no card · full SAFe SSM bank with area filters and the error log: $15 one-time · no dumps, no ads.
Start SAFe SSM free →
ExamDeck is an independent study tool, not affiliated with, endorsed by, or sponsored by Scaled Agile. SAFe SSM and related marks are trademarks of their respective owners, used for identification only. Exam facts checked against official Scaled Agile materials (as of November 2026); always confirm current details with the vendor before booking.