Free SAFe-SASM Exam Braindumps
SAFe Advanced Scrum Master Questions 11–15 (page: 4)

Updated On: 10-Feb-2026

The Agile Team includes the Scrum Master and which other key role?

  1. Product Owner
  2. Release Train Engineer
  3. Project Manager
  4. Product Manager

Answer(s): A

Explanation:

Agile Team Composition: According to SAFe, an Agile Team is composed of cross-functional members who work together to deliver value. The team includes:
Scrum Master: Facilitates the team's processes, helps remove impediments, and supports continuous improvement.
Product Owner: Represents the customer and stakeholders, prioritizes the backlog, and ensures the team is working on the most valuable items.
Developers: The team members who design, build, and test the product. Key Role: The Product Owner is essential to the Agile Team as they provide the vision, set priorities, and ensure that the team is delivering value that aligns with the customer and business needs.
SAFe Scrum Master


Reference:

The SAFe framework emphasizes the critical role of the Product Owner within the Agile Team, ensuring alignment and effective backlog management.



What is the purpose of the Large Solution level in SAFe?

  1. To coordinate the work of multiple Agile Teams on the Agile Release Train (ART)
  2. To regulate large batch delivery across multiple ARTs at the Solution level
  3. To coordinate multiple Agile Release Trains that develop the same Solution
  4. To create large Portfolio-level Solutions that the ART can use to create organizational alignment

Answer(s): C

Explanation:

Large Solution Level in SAFe: This level is designed for enterprises where multiple Agile Release Trains (ARTs) and suppliers collaborate to build and deploy complex solutions that require coordination beyond a single ART.
Purpose: The Large Solution level provides the practices, roles, and artifacts necessary to coordinate the efforts of multiple ARTs:
Solution Train: A structure that manages the delivery of large solutions, aligning the efforts of multiple ARTs.
Solution Management and Solution Architect/Engineer: Roles responsible for defining the solution's vision, roadmap, and architecture.
Solution Backlog and Solution Kanban: Tools to manage and prioritize work across multiple ARTs. Coordination: The primary focus is on ensuring that all ARTs are aligned, integrated, and delivering cohesive, high-quality solutions.
SAFe Scrum Master


Reference:

The SAFe framework details the Large Solution level and its role in coordinating the efforts of multiple ARTs to deliver complex, enterprise-level solutions.



What is one problem with phase-gate Milestones?

  1. They assume a point Solution exists and can be built right the first time
  2. They force design decisions too late in the process
  3. They account for variability inherent in the process
  4. They require the Product Owner to act as gatekeeper or guardian of the process

Answer(s): A

Explanation:

Phase-gate milestones are traditional project management mechanisms that mark the end of one phase and the beginning of another. One major problem with phase-gate milestones is that they assume a point solution exists and can be built correctly the first time. This assumption does not account for the iterative nature of Agile methodologies, where solutions are developed incrementally and iteratively, with feedback loops and continuous improvement. Assuming a point solution can be finalized early often leads to rigidity, lack of adaptability, and higher risks of delivering a product that does not meet the actual needs or expectations.



What is one output from the problem-solving workshop?

  1. ROAMed risks
  2. All the potential Solutions the team could identify
  3. An assessment report
  4. Top improvement items for the next PI

Answer(s): D

Explanation:

One of the primary outputs from the problem-solving workshop in SAFe is identifying the top improvement items for the next Program Increment (PI). These workshops focus on analyzing issues, determining root causes, and formulating actionable improvements. By prioritizing and committing to these improvement items, teams can systematically address problems and enhance their performance and productivity in subsequent PIs.



How is average lead time measured in a Kanban system?

  1. By taking the average velocity over the last three iterations
  2. Measure the vertical distance between arrival and departure lines on a cumulative flow diagram
  3. Measure the horizontal distance between arrival and departure lines on a cumulative flow diagram
  4. Measure the lead time for at least three items and calculate the statistical mean of the items

Answer(s): C

Explanation:

In a Kanban system, average lead time is measured by observing the horizontal distance between the arrival and departure lines on a cumulative flow diagram (CFD). The CFD visualizes the flow of work items through various stages of the workflow. The horizontal distance between the points where work items enter and leave a particular stage represents the lead time. By calculating this distance over multiple items, teams can determine the average lead time, providing insights into process efficiency and areas for potential improvement.



Viewing page 4 of 13
Viewing questions 16 - 20 out of 60 questions


Post your Comments and Discuss Scaled Agile SAFe-SASM exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!