I85PREP
⌘ K
SAFe SSM study materials
SAFe SSM study resources

SAFe SSM practice questions

One question at a time. Build your SAFe SSM understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Introducing Scrum in SAFe®

In SAFe, what is the typical timebox for an iteration?

  1. Two weeks Correct answer.
  2. Four weeks
  3. Three weeks
  4. Six weeks

Explanation

SAFe recommends that all teams on an Agile Release Train adopt a standard two-week iteration cadence so that development, integration, and learning stay synchronized. Other lengths are permitted, but two weeks is the normal default for an ART.

Question 2Introducing Scrum in SAFe®

Which of the following is a core responsibility of the SAFe Scrum Master/Team Coach?

  1. Prioritizing the portfolio backlog across value streams
  2. Establishing the architectural runway for the Agile Release Train
  3. Coaching the team and facilitating its events Correct answer.
  4. Approving team PI Objectives on behalf of the Business Owners

Explanation

The Scrum Master/Team Coach is a servant leader and coach at the team level, responsible for facilitating team events, building a high-performing team, and helping remove impediments. Responsibilities that span the whole ART or portfolio belong to other roles such as the RTE, Business Owners, or portfolio leadership.

Question 3Introducing Scrum in SAFe®

What is the standard timebox for the Daily Stand-up in SAFe Scrum?

  1. Fifteen minutes Correct answer.
  2. Ten minutes
  3. Five minutes
  4. Thirty minutes

Explanation

The Daily Stand-up is a short, daily synchronization event for the team, timeboxed to fifteen minutes. Keeping it brief forces the team to focus on progress toward the Iteration Goals and on impediments rather than on problem solving.

Question 4Introducing Scrum in SAFe®

What is the main purpose of Backlog Refinement in SAFe Scrum?

  1. To commit the team to PI Objectives negotiated with Business Owners
  2. To demonstrate the integrated increment to ART stakeholders
  3. To detail backlog items until they are ready to be pulled Correct answer.
  4. To inspect the team's process and agree on improvements

Explanation

Backlog Refinement is an ongoing activity in which the team and Product Owner clarify, split, and estimate upcoming backlog items so they meet the team's definition of ready. Items are prepared ahead of Iteration Planning rather than being designed during it.

Question 5Introducing Scrum in SAFe®

Which statement best describes an Agile Team in SAFe?

  1. It is a temporary group formed only for the two-day PI Planning event
  2. It is staffed and directed by a functional manager who assigns daily tasks
  3. It has the skills needed to define, build, test, and deliver value Correct answer.
  4. It consists of developers plus a project manager who owns the schedule

Explanation

An Agile Team in SAFe is a long-lived, cross-functional group that contains all the skills necessary to define, build, test, and deliver value as an increment each iteration. Teams are self-managing and organize their own work rather than receiving task assignments from outside.

Question 6Introducing Scrum in SAFe®

What is the primary focus of the Iteration Retrospective?

  1. Improving how the team works together and delivers Correct answer.
  2. Re-planning the remaining iterations of the current PI
  3. Demonstrating the iteration's increment to stakeholders
  4. Reviewing the ART's progress against its PI Objectives

Explanation

The Iteration Retrospective is a team-level event in which the team inspects its way of working and agrees on small improvements to apply in the next iteration. ART-wide inspection against PI Objectives happens later, at the Inspect and Adapt event.

Question 7Introducing Scrum in SAFe®

Why does SAFe generally use the term "iteration" instead of "sprint"?

  1. To stay method-agnostic across Scrum, Kanban, and other methods Correct answer.
  2. Because SAFe iterations are always longer than the sprints used in Scrum
  3. Because a sprint includes neither a review nor a retrospective
  4. Because iterations are used only inside the IP iteration

Explanation

SAFe is method-agnostic: teams may apply Scrum, Kanban, or another approach, so SAFe uses the neutral term "iteration" for the team's timebox. Scrum-based teams still perform the familiar Scrum events within that iteration.

Question 8Introducing Scrum in SAFe®

How does the Iteration Review differ from the System Demo?

  1. The System Demo is held only once per PI, during the Inspect and Adapt event
  2. The Iteration Review is a two-day event that replaces PI Planning for small teams
  3. The Iteration Review is team-level; the System Demo covers the full ART Correct answer.
  4. The Iteration Review is facilitated by the RTE, the System Demo by the Scrum Master

Explanation

At the Iteration Review the team inspects its own increment with the Product Owner and stakeholders and adapts its backlog. The System Demo shows the integrated work of all teams on the ART, giving stakeholders a view of the whole solution's progress each iteration.

Question 9Introducing Scrum in SAFe®

What is the primary purpose of the Innovation and Planning (IP) iteration?

  1. To provide a cadence-based buffer for innovation, planning, and learning Correct answer.
  2. To give the team extra capacity for carrying over stories that were not finished
  3. To harden the solution and run regression tests before the system demo
  4. To replace the Iteration Retrospective at the end of the PI

Explanation

The IP iteration occurs once per PI and acts as a cadence-based buffer that absorbs estimation variance while providing dedicated time for PI Planning, Inspect and Adapt, innovation, and learning. It is not a hardening or catch-up sprint, because quality is built in continuously.

Question 10Introducing Scrum in SAFe®

During PI Planning, what is the Scrum Master/Team Coach's main responsibility?

  1. Presenting the ART's business context and vision to all teams
  2. Assigning the team's stories to individual developers for the PI
  3. Owning the ART backlog and prioritizing features for the PI
  4. Facilitating team breakouts and helping draft PI Objectives Correct answer.

Explanation

In PI Planning the Scrum Master/Team Coach facilitates the team's breakout sessions, helps the team estimate and negotiate scope, and supports drafting of its PI Objectives. This keeps the team productive and aligned while the RTE facilitates the overall event.

Question 11Introducing Scrum in SAFe®

What is an Iteration Goal in SAFe?

  1. A commitment to deliver a specific feature by the end of the PI
  2. A metric that measures the team's predictability over several iterations
  3. A high-level summary of the business value the team intends to deliver Correct answer.
  4. A list of every story the team will complete in the iteration

Explanation

Iteration Goals are short, high-level summaries of the business value the team intends to deliver in the iteration, and they align the team's work with its PI Objectives. They are communicated to the team's stakeholders so progress can be tracked without inspecting every story.

Question 12Introducing Scrum in SAFe®

What is the purpose of the ART Sync?

  1. To align Scrum Masters and Product Owners on progress and dependencies Correct answer.
  2. To plan the next PI and commit teams to their PI Objectives
  3. To demonstrate the integrated solution to Business Owners and stakeholders
  4. To review the team's iteration results and update the team backlog

Explanation

The ART Sync combines the Scrum of Scrums and the Product Owner Sync so that Scrum Masters and Product Owners can coordinate progress, surface risks, and resolve cross-team dependencies. It is typically facilitated by the RTE and complements, rather than replaces, the team's own events.

Question 13Introducing Scrum in SAFe®

What takes place during the Inspect and Adapt event?

  1. The ART reviews the PI results, runs a retrospective, and solves problems Correct answer.
  2. Teams plan the next PI and create their team PI Objectives
  3. Business Owners review and approve the team's iteration goals for the next PI
  4. The Scrum Master presents the team's velocity trend to the RTE

Explanation

Inspect and Adapt is an ART-level event held at the end of each PI, where the current state of the solution is demonstrated and measured, the ART reflects on its performance, and a structured problem-solving workshop identifies improvement items. Those improvements feed the next PI Planning.

Question 14Introducing Scrum in SAFe®

Which two inputs are most important at the start of Iteration Planning?

  1. The team's available capacity and the prioritized team backlog Correct answer.
  2. The portfolio Kanban and the enterprise strategic themes
  3. The solution demo script and the ART's architectural runway
  4. The team's velocity from the last PI and the system demo results

Explanation

Iteration Planning begins with how much capacity the team actually has, given time off, ceremonies, and known obligations, and with the prioritized team backlog the Product Owner brings forward. From these the team selects stories and agrees on its Iteration Goals.

Question 15Introducing Scrum in SAFe®

Which statement best describes the SAFe Product Owner's focus?

  1. Defining the ART's vision, features, and roadmap for the next PI
  2. Facilitating the team's events and removing its impediments
  3. Building and prioritizing the team backlog for value delivery Correct answer.
  4. Managing the ART's continuous delivery pipeline and releases

Explanation

In SAFe the Product Owner focuses inward on the team, building, refining, and prioritizing the team backlog so the team delivers value continuously. The Product Manager owns the ART-level vision, roadmap, and feature backlog that the Product Owner draws from.

Question 16Introducing Scrum in SAFe®

How do features and stories relate in SAFe?

  1. Features and stories are synonyms used at the same backlog level
  2. Stories are created by Business Owners to fund features
  3. Features are ART-level items that teams split into stories Correct answer.
  4. Stories are ART-level items that teams break down into features

Explanation

Features are the ART-level backlog items that describe the solution's functionality, and each feature is decomposed by a team into smaller stories that fit within an iteration. Stories therefore live on the team backlog while features live on the ART backlog.

Question 17Introducing Scrum in SAFe®

How is velocity most useful to an Agile Team?

  1. It forecasts how much work the team can complete in an iteration Correct answer.
  2. It sets the mandatory number of hours each developer must work
  3. It ranks features for the Product Manager on the ART backlog
  4. It measures the business value delivered to the customer per PI

Explanation

Velocity is a historical measure of how much backlog work the team completes per iteration, and its main use is forecasting how much can be taken on in the next iteration. It is a planning aid for the team, not a productivity yardstick applied to individuals.

Question 18Introducing Scrum in SAFe®

A team member repeatedly waits days for access to a test environment. What is the Scrum Master's best response?

  1. Help remove the impediment and address its root cause Correct answer.
  2. Escalate it to the Product Owner to reprioritize the backlog
  3. Add the waiting time to the team's velocity calculation
  4. Instruct the developer to work around the environment gap

Explanation

Removing impediments and helping the team address their underlying causes is a core Scrum Master/Team Coach accountability. A recurring environment delay is a systemic issue, so the goal is to fix the cause so the delay does not return.

Question 19Introducing Scrum in SAFe®

A team's PI Objectives were assigned a planned business value of 40, and the actual business value achieved was 30. What is the predictability measure?

  1. 70%
  2. 133%
  3. 25%
  4. 75% Correct answer.

Explanation

The predictability measure is calculated as actual business value divided by planned business value, multiplied by 100, so 30 divided by 40 gives 75%. It tells the ART how reliably planned value was delivered across the PI.

Question 20Introducing Scrum in SAFe®

Why are business values assigned to team PI Objectives?

  1. To assess planned value and later measure predictability Correct answer.
  2. To calculate each developer's individual performance rating for the PI
  3. To replace the need for a System Demo at the end of each iteration
  4. To decide which team gets the largest share of the next PI's budget

Explanation

Business Owners assign a business value to each PI Objective, which expresses the planned value of the ART's commitments and enables the predictability measure once actual value is assessed. This keeps the focus on outcomes delivered rather than on activity or effort.

Question 21Introducing Scrum in SAFe®

An ART's teams finish their stories each iteration, but the System Demo repeatedly fails to show working end-to-end functionality. Which SAFe practice is most likely missing?

  1. Continuously integrating team work into a common solution Correct answer.
  2. Timeboxing the Iteration Retrospective to one hour
  3. Holding a Daily Stand-up within each team
  4. Assigning business value to team PI Objectives at PI Planning

Explanation

Built-in quality requires that teams continuously integrate their work into a shared solution so that functionality works end to end, not just within each team's stories. When integration is deferred, individual stories appear complete while the System Demo cannot show a working whole.

Question 22Introducing Scrum in SAFe®

A team's stories routinely carry over into the next iteration. As Scrum Master/Team Coach, what is the most useful action?

  1. Increase the team's velocity target so carryover is absorbed
  2. Ask the Product Owner to add more stories to fill the team's capacity
  3. Recommend splitting stories into smaller slices during refinement Correct answer.
  4. Move the unfinished stories into the IP iteration each PI

Explanation

Large stories are a common cause of carryover because they cannot be finished within the timebox. Coaching the team and Product Owner to slice items smaller during Backlog Refinement improves flow and makes progress visible every iteration.

Question 23Characterizing the role of the Scrum Master

In SAFe, which statement best characterizes the primary role of the Scrum Master?

  1. A proxy for the Product Owner who orders the team backlog
  2. A project manager who assigns tasks and tracks individual utilization
  3. A servant leader and coach who helps the team adopt, practice, and continuously improve Agile ways of working Correct answer.
  4. A technical lead who makes design and architecture decisions for the team

Explanation

SAFe describes the Scrum Master as a servant leader and coach for the team and the surrounding organization. The role focuses on teaching Agile and SAFe practices, facilitating events, removing impediments, and building a high-performing, self-managing team. Authority comes from influence and trust rather than from positional power over the work itself.

Question 24Characterizing the role of the Scrum Master

What is the Scrum Master's primary focus during PI Planning?

  1. Running the management review and problem-solving session for the ART
  2. Facilitating the team's planning activities and helping the team build and commit to its objectives Correct answer.
  3. Approving the final program board on behalf of the Business Owners
  4. Setting the business priority of each feature for the ART

Explanation

The Scrum Master helps the team prepare for and execute its part of PI Planning, including creating draft plans, identifying dependencies, and committing to PI objectives. ART-level facilitation and the management review belong to the Release Train Engineer. Business priorities are set by Business Owners and Product Management.

Question 25Characterizing the role of the Scrum Master

In SAFe, the Scrum Master works most closely with which role to keep the team backlog refined and ready for Iteration Planning?

  1. The Product Owner Correct answer.
  2. The System Architect
  3. The Release Train Engineer
  4. The Business Owners

Explanation

The Product Owner owns the content and order of the team backlog, and the Scrum Master coaches and supports that work so items are ready and understood by the team. The day-to-day partnership between these two roles is what keeps planning smooth. The other roles interact with the team but do not own backlog readiness.

Question 26Characterizing the role of the Scrum Master

Which behavior best illustrates servant leadership by a Scrum Master?

  1. Assigning daily work to each team member at the stand-up
  2. Deciding for the team when consensus takes too long
  3. Escalating every team issue to the Release Train Engineer
  4. Asking the team what it needs and clearing obstacles so it can do its best work Correct answer.

Explanation

Servant leadership puts the needs of the team and the people it serves first, with the leader working to remove barriers and enable others. The Scrum Master asks rather than directs, and shifts from controlling work to supporting the team's growth. Decisions about the work stay with the team.

Question 27Characterizing the role of the Scrum Master

Which outcome is the Scrum Master ultimately coaching the team toward?

  1. A team that maximizes story points delivered per Iteration
  2. A team that keeps its practices unchanged across PIs to reduce variation
  3. A self-managing, high-performing team that owns its process and outcomes Correct answer.
  4. A team that depends on the Scrum Master for all significant decisions

Explanation

The purpose of coaching in SAFe is to build a team capable of managing its own work and continuously improving how it operates. Success is measured by growing capability and ownership, not by the Scrum Master becoming indispensable. Practices should evolve as the team learns.

Question 28Characterizing the role of the Scrum Master

Which statement accurately describes the Scrum Master's authority within an Agile team?

  1. The Scrum Master influences through trust, coaching, and facilitation rather than positional authority Correct answer.
  2. The Scrum Master holds the same decision rights as a functional manager over the team members
  3. The Scrum Master directs the team's day-to-day work to keep delivery on schedule
  4. The Scrum Master approves individual team members' time off and performance ratings

Explanation

The Scrum Master leads through influence, credibility, and service to the team rather than through hierarchical control. This is what distinguishes the role from a line manager or project manager. Team members remain accountable for their own work and behavior.

Question 29Characterizing the role of the Scrum Master

Which event is the Scrum Master most directly responsible for facilitating at the team level?

  1. The Portfolio Sync
  2. Inspect & Adapt
  3. The ART Sync
  4. The Iteration Retrospective Correct answer.

Explanation

The Scrum Master facilitates the team's own events, including Iteration Planning, the Daily Stand-up, the Iteration Review, and the Iteration Retrospective. ART-level ceremonies such as the ART Sync, Inspect & Adapt, and portfolio syncs are facilitated by the Release Train Engineer or portfolio roles. Teams may rotate facilitation, but the Scrum Master ensures these events happen and are effective.

Question 30Characterizing the role of the Scrum Master

A new team member asks who is responsible for teaching the team Scrum, SAFe, and Kanban practices. What is the Scrum Master's role?

  1. Each team member is expected to learn independently without guidance
  2. The Scrum Master educates the team in Scrum, SAFe, and Kanban and coaches the team on its agreed process Correct answer.
  3. The Product Owner teaches Agile practices while the Scrum Master only schedules meetings
  4. The Release Train Engineer teaches all team-level practices across the ART

Explanation

A core SAFe Scrum Master responsibility is educating the team in Scrum, SAFe, and Kanban and helping the team follow its agreed ways of working. Teaching is delivered through coaching and modeling rather than one-time instruction. The Release Train Engineer supports the ART broadly but does not replace team-level coaching.

Question 31Characterizing the role of the Scrum Master

A team member reports that the shared test environment has been unavailable for two days, blocking verification of completed work. What should the Scrum Master do first?

  1. Reassign the blocked work to another team that has a working environment
  2. Ask the Product Owner to remove the affected stories from the backlog
  3. Record it in the risk list and revisit it at the next PI Planning session
  4. Help the team resolve the blocker and escalate to the Release Train Engineer if it is beyond the team's ability Correct answer.

Explanation

Impediment removal starts with helping the team solve what it can on its own, and escalates through the Release Train Engineer or other ART channels when the cause lies outside the team's control. Prompt action protects flow and keeps commitments realistic. Removing stories hides the systemic problem instead of addressing it.

Question 32Characterizing the role of the Scrum Master

At Iteration Planning, the team looks to the Scrum Master to decide how the work should be divided among members. What is the most appropriate response?

  1. Ask the team how it wants to organize the work and support the decision it makes Correct answer.
  2. Assign the work to the most experienced developer to reduce risk
  3. Make the assignments so planning finishes on schedule
  4. Defer the decision to the Release Train Engineer

Explanation

Self-management means the team decides how to organize and carry out its own work. The Scrum Master's job is to create the conditions for that decision, not to make it. Assigning work, even with good intentions, trains the team to wait for direction.

Question 33Characterizing the role of the Scrum Master

How does a Scrum Master typically contribute in the Scrum of Scrums?

  1. By representing the team's progress, dependencies, and impediments to the other teams Correct answer.
  2. As the sole decision-maker for the team's priorities
  3. Only when the Release Train Engineer is unavailable
  4. By sending the Product Owner in their place

Explanation

Scrum Masters attend the Scrum of Scrums to represent their team, surface cross-team dependencies, and coordinate impediment resolution with peers and the Release Train Engineer. The event is about coordination and flow across teams, not about resetting priorities. Attendance is a standing responsibility rather than a backup arrangement.

Question 34Characterizing the role of the Scrum Master

Which responsibility belongs to the Release Train Engineer rather than to the team's Scrum Master?

  1. Helping the team clear day-to-day impediments
  2. Coaching the team on limiting work in progress
  3. Facilitating the team's Iteration Retrospective
  4. Facilitating ART-level events such as PI Planning and Inspect & Adapt Correct answer.

Explanation

The Release Train Engineer is the ART's servant leader and coach, facilitating ART-level events such as PI Planning, the ART Sync, the System Demo, and Inspect & Adapt. Team-level facilitation, coaching, and impediment removal sit with the Scrum Master. The two roles cooperate closely, but their scope differs.

Question 35Characterizing the role of the Scrum Master

A team's Kanban board shows work piling up in the 'in progress' column while downstream columns sit idle. What is the Scrum Master's best response?

  1. Move stalled items to 'done' so the board reflects progress
  2. Ask the Release Train Engineer to raise the ART work-in-progress limits
  3. Coach the team to respect its work-in-progress limits and address the bottleneck together Correct answer.
  4. Add people to the team immediately to increase capacity

Explanation

The Scrum Master uses the team board to help the team see flow problems and then coaches the team to resolve them, for example by honoring work-in-progress limits and focusing on the constraint. Solving the flow problem is a team learning opportunity. Adjusting metrics or headcount does not fix the underlying bottleneck.

Question 36Characterizing the role of the Scrum Master

Which activity best describes how a Scrum Master supports the Product Owner?

  1. Writing the team's user stories and ordering the team backlog
  2. Coaching backlog management practices and helping the team understand backlog items Correct answer.
  3. Deciding which features are placed on the program board
  4. Approving the PI objectives together with the Business Owners

Explanation

The Scrum Master supports the Product Owner by coaching on backlog practices and by ensuring the team comprehends and can act on backlog items. Content decisions and ordering remain with the Product Owner. This partnership keeps the backlog healthy without diluting accountability.

Question 37Characterizing the role of the Scrum Master

How do the outcomes of a team's Iteration Retrospectives connect to the ART's Inspect & Adapt event?

  1. Retrospective actions replace the need for an ART-level Inspect & Adapt
  2. Only the Release Train Engineer may collect retrospective actions for the ART
  3. Improvement items surfaced in retrospectives can feed the ART's structured problem-solving in Inspect & Adapt Correct answer.
  4. Retrospective actions must be approved by the Business Owners before use

Explanation

Iteration Retrospectives generate team-level improvements, and those that are systemic or cross-team can be carried into the Inspect & Adapt problem-solving session. This creates a continuous improvement loop from the team to the ART. Inspect & Adapt addresses broader, data-driven improvements rather than duplicating team retrospectives.

Question 38Characterizing the role of the Scrum Master

Which action best reflects the Scrum Master promoting built-in quality?

  1. Adding a hardening and testing phase at the end of every PI
  2. Assigning one team member to own all quality issues
  3. Coaching the team to build quality in through practices such as test automation and a clear definition of done Correct answer.
  4. Deferring refactoring work until after the System Demo

Explanation

Built-in quality means the team applies practices such as test automation, continuous integration, and a shared definition of done as part of daily work rather than inspecting quality in later. The Scrum Master reinforces this through coaching and by helping the team make these practices visible. Deferred testing and single-owner quality reduce shared accountability.

Question 39Characterizing the role of the Scrum Master

Halfway through an Iteration, a stakeholder asks the team to add an urgent feature that was not planned. What is the Scrum Master's most appropriate action?

  1. Work with the Product Owner and the stakeholder to evaluate the request against current commitments and flow Correct answer.
  2. Add the item to the team board as unplanned work without discussion
  3. Refuse the request outright and escalate the stakeholder to the Release Train Engineer
  4. Instruct the team to accept the work and extend the Iteration by a week

Explanation

The Scrum Master protects the team's Iteration while keeping the request visible and routed through the proper decision channel. The Product Owner owns priority, and the conversation should compare the new request with existing commitments and capacity. Unilateral acceptance or refusal both bypass that accountability.

Question 40Characterizing the role of the Scrum Master

Two team members disagree sharply during an Iteration Retrospective. What is the Scrum Master's most useful contribution?

  1. Report the disagreement to the Release Train Engineer as a team conflict
  2. End the discussion and move to the next agenda item
  3. Help the team work through the disagreement constructively so all perspectives are heard Correct answer.
  4. Decide which viewpoint the team should adopt

Explanation

The Scrum Master facilitates healthy conflict so that diverse perspectives improve the team's decisions and relationships. Shutting down or resolving the disagreement from above prevents the team from building its own conflict-handling skills. Escalation is not warranted for a normal disagreement being worked through.

Question 41Characterizing the role of the Scrum Master

How can a Scrum Master best help a team use its metrics?

  1. Set stretch targets based on the team's highest Iteration on record
  2. Use velocity to rank the team against other teams in the ART
  3. Report individual utilization figures to management
  4. Help the team use its own flow and Iteration data to improve predictability and inspect progress Correct answer.

Explanation

Team metrics exist to help the team inspect and adapt its own way of working and forecast more reliably. Comparing teams or individuals with the same measure distorts behavior and ignores context. The Scrum Master coaches data-informed reflection rather than target-setting from a single best result.

Question 42Characterizing the role of the Scrum Master

Which practice best supports a Scrum Master's own continuous learning in SAFe?

  1. Waiting for the Release Train Engineer to assign formal training
  2. Taking part in the Scrum Master/Team Coach Community of Practice and sharing lessons with peers Correct answer.
  3. Relying solely on the certification obtained at the start of the role
  4. Restricting learning to what emerges inside the team's retrospectives

Explanation

SAFe encourages practitioners to keep growing through Communities of Practice, peer exchange, and shared experience across teams and the ART. Continuous learning is an expectation of the role, not a one-time credential. Peer communities accelerate the spread of effective practices.

Question 43Characterizing the role of the Scrum Master

What is the Scrum Master's contribution to the System Demo?

  1. Presenting all of the team's features on the team's behalf
  2. Deciding which stakeholders are permitted to attend
  3. Certifying the demo as complete on behalf of the Release Train Engineer
  4. Helping the team prepare, demonstrate integrated work, and gather stakeholder feedback Correct answer.

Explanation

The Scrum Master supports the team in preparing for the System Demo and in using the feedback it receives to adjust the backlog and plans. The team demonstrates its own work, which keeps ownership with those who built it. Attendance and ART-level facilitation are managed by the Release Train Engineer and the ART.

Question 44Characterizing the role of the Scrum Master

While building its PI plan, a team discovers dependencies on two other teams. What is the Scrum Master's best action?

  1. Adjust the other teams' plans so the dependency disappears
  2. Remove the dependent features from the team's plan to keep it clean
  3. Help the team make the dependencies visible on the program board and agree on follow-up with the other teams Correct answer.
  4. Escalate every dependency to the Business Owners for prioritization

Explanation

PI Planning is the moment to surface cross-team dependencies and coordinate them openly so the ART can plan realistically. The Scrum Master facilitates that visibility and follow-through rather than editing other teams' plans. Escalation is reserved for dependencies that cannot be resolved through coordination.

Question 45Characterizing the role of the Scrum Master

A team has missed its Iteration goals for three consecutive Iterations and consistently blames external dependencies. What is the Scrum Master's best first step as a coach?

  1. Help the team examine its own data and identify root causes it can influence Correct answer.
  2. Reduce the team's PI objectives at the next planning session
  3. Escalate to the Release Train Engineer that the team cannot meet its commitments
  4. Instruct the team to plan fewer stories in the next Iteration

Explanation

Effective coaching starts with helping the team inspect its own evidence and separate what it controls from what it does not. This builds the team's capability to solve problems rather than depending on someone else to adjust the plan. Escalation and scope reduction may follow, but only after the team has analyzed the causes.

Question 46Characterizing the role of the Scrum Master

How does a SAFe Scrum Master most appropriately support a team's adoption of continuous delivery?

  1. Schedule releases every six months to reduce deployment risk
  2. Create a separate operations group to handle all deployments for the team
  3. Leave all technical practice decisions to the System Architect
  4. Coach the team to automate its delivery pipeline and apply built-in quality practices in daily work Correct answer.

Explanation

The Scrum Master supports technical agility by coaching the team to adopt practices such as pipeline automation, continuous integration, and built-in quality as part of how it works every day. This complements the architect's technical guidance rather than replacing it. Separating deployment from the team slows feedback and increases risk.

Question 47Characterizing the role of the Scrum Master

A team's largest impediment is an organizational policy that blocks on-demand deployment across the ART. What is the Scrum Master's most appropriate response?

  1. Ask the Product Owner to negotiate the policy change with the team
  2. Accept the policy as outside the team's control and stop raising it
  3. Quietly bypass the policy for the team's own releases
  4. Surface the organizational impediment through Inspect & Adapt and work with the Release Train Engineer and leadership to resolve it Correct answer.

Explanation

Scrum Masters serve as change agents who help the organization see and remove systemic impediments, using structured problem-solving and leadership engagement rather than silence. Inspect & Adapt is a natural venue for raising ART-wide and organizational blockers with data. Bypassing policy or pushing the issue onto the Product Owner avoids the real ownership.

Question 48Characterizing the role of the Scrum Master

Which stance best characterizes how a SAFe Scrum Master exercises influence over the team?

  1. Reporting team performance upward on behalf of the Product Owner
  2. Coaching and serving the team rather than directing its work Correct answer.
  3. Approving each team member's daily work plan before stand-up
  4. Assigning tasks to team members according to their skill profiles

Explanation

SAFe Scrum Masters lead through influence, acting as servant leaders and coaches who help the team manage its own work. Directing assignments or approving individual plans would take ownership away from the team and undermine self-management.

Question 49Characterizing the role of the Scrum Master

What is the Scrum Master's most appropriate contribution during the Daily Stand-up?

  1. Keeping the discussion focused on Iteration goal progress Correct answer.
  2. Collecting each member's hours worked for the team's burndown
  3. Deciding which blocked items the team should drop from the Iteration
  4. Summarizing the team's status for the Release Train Engineer

Explanation

The Daily Stand-up exists so the team can inspect progress toward the Iteration goals and adapt its plan, and the Scrum Master keeps that conversation focused and time-boxed. Status reporting, hour collection, and scope decisions are not the Scrum Master's to make in that event.

Question 50Characterizing the role of the Scrum Master

What is the Scrum Master's role regarding the team's Definition of Done?

  1. Auditing increments personally against the Definition of Done
  2. Deferring Definition of Done decisions to the System Architect
  3. Writing the Definition of Done and publishing it to the ART
  4. Coaching the team to define and apply its Definition of Done Correct answer.

Explanation

The Definition of Done is a team agreement, and the Scrum Master coaches the team to create it and apply it consistently to every increment. Writing it for the team or auditing work personally shifts accountability away from the people doing the work.