Question 1

What is one way Design Thinking measures success?

Accepted Answer

D

Explanation: One of the key measures of success in Design Thinking, as highlighted in SAFe, is whether the solution is “desirable”—that is, if it meets real customer needs. Desirability is one of the three core aspects evaluated (desirable, feasible, viable) in Design Thinking. Reference: SAFe 6.0, “Design Thinking” article SPC 6.0 Guide, “Building Solutions with Agile Product Delivery” ===========

Question 2

When is the best time to release a product or Solution to the marketplace?

Accepted Answer

C

Explanation: SAFe promotes continuous delivery and recommends releasing products and solutions whenever they meet both business (market) and governance criteria, regardless of iteration or PI boundaries. This enables faster value delivery and more frequent feedback from customers. “The best time to release is whenever the solution meets market opportunity and governance requirements, not necessarily at PI or iteration boundaries.” (Source: SAFe 6.0 Framework: Release on Demand; SPC 6.0 Guide, “Building Solutions with Agile Product Delivery”)

Question 3

Which activity is associated with the release-on-demand step of the continuous delivery pipeline?

Accepted Answer

D

Explanation: The Continuous Delivery Pipeline in SAFe includes four steps: Continuous Exploration, Continuous Integration, Continuous Deployment, and Release on Demand. “Deploy” is the activity most directly associated with the “Release on Demand” step, where solutions are made available to end users whenever the business needs it. Reference: SAFe 6.0, “Release on Demand” in the “Continuous Delivery Pipeline” article SPC 6.0 Guide, “Building Solutions with Agile Product Delivery” ===========

Question 4

What description best represents Capabilities as defined in SAFe?

Accepted Answer

D

Explanation: In SAFe 6.0, Capabilities are defined as "higher-level solution behaviors that typically span multiple ARTs." They are maintained in the Solution Train Backlog and are sized and split into Features for implementation by individual ARTs. The SAFe 6.0 guidance specifically states: “Capabilities are larger solution behaviors that often span multiple Agile Release Trains. They are typically sized to be delivered in a Planning Interval (PI) and are broken down into Features to facilitate implementation.” This distinguishes Capabilities from Epics and Features. Unlike Epics, which require Lean Business Cases and approval through Portfolio Kanban, Capabilities follow a breakdown path to Features for execution. Therefore, they are a level above Features, not a synonym for Epics or Features. Reference: SAFe 6.0 Website: Capabilities SAFe Practice Consultant SPC (6.0) Training Guide — "Building Solutions with Agile Product Delivery" Module Terminology Update: "Solution Backlog" → "Solution Train Backlog" confirms the hierarchical location of Capabilities

Question 5

What activity calls for using the ROAM technique?

Accepted Answer

C

Explanation: The ROAM technique (Resolved, Owned, Accepted, Mitigated) is used during Planning Interval (PI) Planning to manage and categorize ART PI Risks. In the PI Planning session, all identified risks are discussed and then categorized using the ROAM framework, which helps teams and stakeholders clarify ownership, mitigation strategies, and acceptance of each risk. According to the SAFe 6.0 official guidance: "During PI Planning, teams identify program risks and then use the ROAM technique to classify each risk as Resolved, Owned, Accepted, or Mitigated. This collaborative activity ensures transparency and allows teams to address significant risks before proceeding." This activity does not take place during backlog refinement, ART syncs, or general team management; it is specific to the PI Planning event. Reference: SAFe 6.0 Website: PI Planning and ROAM SAFe Practice Consultant SPC (6.0) Training Guide — "Launching an Agile Release Train" Module New Terminology: "Program PI Risks" are now referred to as "ART PI Risks"

Question 6

You are working with an ART that is preparing for their first PI Planning event. All Features are
formulated and ready for WSJF prioritization. However, when you look over the list of Features, it
turns out that they are big tasks rather than Features.
What technique would be useful to fix the list of backlog items to be able to apply WSJF?

Accepted Answer

A

Explanation: Features in SAFe should be right-sized, delivering value and being small enough for incremental delivery within a PI. If the current backlog items are too large (“big tasks”), the best technique is to split them into smaller, more manageable Features. This enables meaningful WSJF prioritization and supports flow-based delivery. Reference: SAFe 6.0 Website: Features and Capabilities SPC 6.0 Guide: “Right-size Features to fit within a PI for effective prioritization and delivery.” ===========

Question 7

(Select 2) What are the responsibilities of a Business Owner?

Accepted Answer

A, B

Explanation: A: Business Owners assign business value to PI Objectives during PI Planning, ensuring alignment with business priorities and objectives. B: Business Owners participate in PI events (including Post-PI Planning) and help ARTs adjust plans to better meet business needs. Assigning value to Epics/Features (C) is the responsibility of Product Management. Ensuring the Solution Demo (D) is a shared leadership responsibility, not specific to Business Owners. Determining the roadmap (E) is owned by Product Management. Reference: SAFe 6.0 Website: Business Owners SPC 6.0 Guide: “Business Owners assign business value to objectives and participate in PI Planning and ART events.” ===========

Question 8

How does a team calculate its initial velocity during its first PI Planning meeting when teams don't have historic data?

Accepted Answer

D

Explanation: SAFe’s guidance for new teams without historical velocity is to assign 8–12 points per team member (typically 10) except Scrum Master and Product Owner, subtracting points for planned absences. “For initial velocity, a simple guideline is to assume 8–12 points per team member (excluding Scrum Master and Product Owner), then subtract 1 point for each day of vacation or holiday.” (Source: SAFe 6.0 Framework: PI Planning Preparation)

Question 9

The Innovation and Planning (IP) Iteration allows time for which of the following activities?

Accepted Answer

A

Explanation: The Innovation and Planning (IP) Iteration is a vital part of SAFe’s Program Increment (PI) cycle. Its main purposes include innovation, planning for the next PI, and supporting activities such as continuing education, infrastructure work, and hackathons. While it can be used for fixing defects or technical work, its explicit inclusion of continuing education distinguishes it from routine development. Reference: SAFe 6.0, “Innovation and Planning Iteration” article SPC 6.0 Practice Guide, “Coaching ART Execution” ===========

Question 10

What does Little's Law tell us?

Accepted Answer

A

Explanation: Little’s Law is a fundamental concept in Lean and flow-based systems. It states that the average wait time (Lead Time) in a queue or process is proportional to the number of items in the system (Work in Process, WIP) divided by the average processing rate. The easiest, most direct way to achieve better flow (reduce wait time) is to reduce the queue length (WIP). SAFe 6.0 specifically cites Little’s Law as the basis for limiting WIP to optimize flow. Other options are incorrect or incomplete: B is false; long queues increase wait time. C is only partially true but not always possible; reducing queue length is usually easier and more controllable. D is incorrect; Little's Law applies to average, stable systems, not varying rates. E is unrelated to Little’s Law specifically. Reference: SAFe 6.0 Website: Principle #6 – Visualize and limit WIP, reduce batch sizes, and manage queue lengths SPC 6.0 Guide: “Little’s Law demonstrates that reducing queue length is the fastest way to reduce wait time and improve flow.” ===========

Question 11

Vikas is a new Solution Architect and is trying to understand the Solution Context. What is the most important factor for him to consider?

Accepted Answer

D

Explanation: The Solution Context defines the environment in which the solution operates, including operational, regulatory, deployment, and support conditions. For a Solution Architect, understanding this environment is essential to ensure the solution will function as required in its real-world context. Reference: SAFe 6.0 Website: Solution Context SPC 6.0 Guide: “Solution Context describes the environment in which the solution operates.” ===========

Question 12

(Select 2) What are the right scenarios for using SAFe Foundations Training Materials?

Accepted Answer

B, D

Explanation: SAFe Foundations Training Materials are designed for broad awareness and initial education, especially for: B: Making an initial presentation on SAFe to the organization. D: Familiarizing executives and leaders with the basics of SAFe. Detailed role-based and process training (A, C, E) is better addressed through role-specific courses (e.g., “SAFe for Teams,” “SAFe Scrum Master,” “SAFe Release Train Engineer”). Reference: SAFe 6.0 Website: SAFe Foundations SPC 6.0 Guide: “Foundations materials are ideal for executive briefings and initial organizational awareness.” ===========

Question 13

Who is the content authority for an Agile Team?

Accepted Answer

B

Explanation: According to SAFe 6.0, “The Product Owner is the content authority for the team backlog. They are responsible for defining Stories and prioritizing the team backlog to streamline the execution of program priorities while maintaining the conceptual and technical integrity of the Features or components the team is responsible for.” The Scrum Master/Team Coach facilitates team events and removes impediments, but does not own content decisions. Product Manager and System Architect provide input and guidance but are not the content authority at the team level. Reference: SAFe 6.0, “Product Owner” article SPC 6.0 Practice Guide, “Establishing Team and Technical Agility” module ===========

Question 14

Iteration Goals have business value assigned by the Product Owner.

Accepted Answer

B

Explanation: PI Objectives (not Iteration Goals) are assigned business value by Business Owners at PI Planning. Iteration Goals are set by the team and Product Owner for focus during the iteration but are not assigned a separate business value metric. “Business Owners assign business value to PI Objectives during PI Planning. Iteration Goals, which guide team focus during an iteration, are not assigned business value.” (Source: SAFe 6.0 Framework: PI Objectives, Iteration Goals) ===========

Question 15

The portfolio Vision is an aggregation of every Agile Release Train's Vision?

Accepted Answer

B

Explanation: The portfolio Vision is not simply an aggregation of the ARTs’ Visions. Instead, the portfolio Vision is a higher-level, strategic expression of the portfolio’s direction and purpose, informed by the enterprise strategy and objectives. While ART Visions may align to and support the portfolio Vision, the portfolio Vision is created at the portfolio level and provides the overall context for the ARTs, not the other way around. Reference: SAFe 6.0 Website: Portfolio Vision SPC 6.0 Guide: “The portfolio vision provides strategic direction for all value streams and ARTs, and is not merely the sum of ART visions.” ===========

Free Scaled Agile SAFe-SPC Actual Exam Questions