Practice Scaled Agile Leading SAFe with free sample questions, timed mock exams, and detailed explanations for SAFe roles, flow, and planning decisions.
Leading SAFe is the SAFe Agilist certification for professionals working in scaled lean-agile environments where flow, alignment, and transformation leadership matter. If you are searching for Leading SAFe sample exam questions, a practice test, or an exam simulator, this is the main PM Mastery page to start on web and continue on iOS or Android with the same account.
Start a practice session for AI-EMPOWERED SAFe Agilist (SA) (Leading SAFe) below, or open the full app in a new tab. For the best experience, open the full app in a new tab and navigate with swipes/gestures or the mouse wheel—just like on your phone or tablet.
Open Full App in a New TabA small set of questions is available for free preview. Subscribers can unlock full access by signing in with the same account they use on web and mobile.
Use on iPhone or Android too: PM Mastery on the App Store or PM Mastery on Google Play using the same account you use on web. The same subscription works across web and mobile.
Leading SAFe usually rewards the option that improves end-to-end flow, aligns priorities, supports lean decision-making, and reinforces change leadership without adding heavy coordination overhead.
| Topic | Weight | Estimated questions |
|---|---|---|
| Adapting and Thriving with SAFe | 8% | 4 |
| Building a Foundation with Mindset, Values and Principles | 21% | 9 |
| Establishing Team and Technical Agility | 8% | 4 |
| Product Development Flow | 27% | 12 |
| Exploring Lean Portfolio Management (LPM) | 28% | 13 |
| Leading the Change | 8% | 4 |
If you want concept-first reading before heavier simulator work, use the companion guide at PMExams.com .
These sample questions cover multiple blueprint areas for Leading SAFe. Use them to check your readiness here, then move into the full PM Mastery question bank for broader timed coverage.
Topic: Adapting and Thriving with SAFe
In SAFe, what is the primary role of PI Planning for an Agile Release Train (ART)?
Best answer: C
Explanation: PI Planning is the ART’s alignment event where teams and stakeholders agree on a shared mission, identify dependencies, and commit to a set of PI Objectives. It synchronizes multiple teams around what will be delivered and how the work will be coordinated across the PI. This upfront alignment is what enables the ART to execute as a system rather than as independent teams.
Topic: Exploring Lean Portfolio Management (LPM)
A portfolio is considering an epic to reduce customer drop-off during mobile account onboarding while staying within security and compliance guardrails. The LPM team wants an epic hypothesis statement that enables fast learning and good flow.
Which option best contains the required components (hypothesis, expected outcomes, and leading indicators)?
Best answer: C
Explanation: An epic hypothesis statement combines a testable hypothesis with measurable expected outcomes and leading indicators that provide early feedback. The best choice includes all three, with leading indicators that can be observed quickly to guide decisions and reduce queues of unvalidated work.
Topic: Product Development Flow
An ART starts PI Planning, but Product Management cannot clearly present the PI Vision or the top prioritized features. Most feature/story details are also not refined enough for teams to break down and estimate. What is the most likely near-term impact on the PI Planning outcome?
Best answer: D
Explanation: PI Planning relies on key inputs such as a clear PI Vision, the top prioritized features, and sufficient backlog readiness to enable teams to plan, estimate, and manage dependencies. When those inputs are missing, teams spend the event debating intent and scope, resulting in PI Objectives and plans that are inconsistent and low confidence. The immediate effect is reduced alignment and predictability for the upcoming PI.
Topic: Product Development Flow
An Agile Release Train (ART) is preparing for PI Planning. Leaders want to ensure teams have the right information available before the event so they can plan effectively.
Which item is NOT a typical input to PI Planning?
Best answer: A
Explanation: Typical PI Planning inputs help teams understand direction and preparedness: the Vision and business context, the top Features expected in the PI, and sufficient architecture runway/backlog readiness to plan and estimate. These inputs enable meaningful draft plans, dependency management, and PI Objectives. Team execution metrics are more commonly used in Inspect and Adapt than as a standard PI Planning input.
Topic: Establishing Team and Technical Agility
Mid-PI, a cross-functional team has eight work items in progress and is frequently context-switching. Work is piling up in review/testing, and the team has missed its last two iteration goals. A stakeholder asks them to start another “urgent” item immediately.
Which action is most likely to improve near-term flow and predictability?
Best answer: A
Explanation: The team shows classic overload signals: high WIP, context switching, and work stuck in downstream stages. The fastest corrective action is to stop starting new work, limit WIP, and swarm to finish a small set of highest-value items. That reduces queues and handoffs, restoring flow and making outcomes more predictable in the near term.
Topic: Establishing Team and Technical Agility
Midway through a PI, an ART’s features are frequently blocked in the last week before release because a centralized security group can only do manual reviews in large batches. This creates unplanned work, increases WIP, and misses the iteration cadence. Compliance checks still must happen, but flow needs to improve.
What is the BEST next action consistent with DevSecOps in SAFe?
Best answer: C
Explanation: The late, batched manual review is a classic sign that security is outside the flow. The best correction is to build security into the Continuous Delivery Pipeline with automated checks and make it part of the teams’ Definition of Done. This reduces handoffs and stabilizes iteration and release predictability while still supporting compliance.
Topic: Product Development Flow
After releasing an MVP, a Product Manager rejects a report highlighting social-media impressions and total sign-ups. Instead, they ask for metrics like activation rate, repeat usage, and retention for the target segment to decide whether to persevere or pivot.
Which SAFe concept is this practice best aligned with?
Best answer: A
Explanation: The practice focuses on actionable, leading indicators of customer value such as adoption, engagement, and retention to validate an MVP. In SAFe, this aligns with Lean Startup thinking and innovation accounting, which avoids vanity metrics and supports evidence-based pivot/persevere decisions. The intent is to learn whether the solution is delivering real customer outcomes.
Topic: Leading the Change
Several teams on an ART are adopting test automation, but practices differ and progress stalls after initial training. A few experienced internal coaches convene a voluntary, cross-team group that meets weekly to share patterns, pair on real problems, and mentor new practitioners so the change sticks.
Which SAFe concept best matches this approach to sustaining Lean-Agile change?
Best answer: D
Explanation: This scenario describes ongoing, voluntary, cross-team learning and mentoring that reinforces new ways of working beyond a one-time training. In SAFe, Communities of Practice provide the social structure to share skills and standards, and internal coaches help teams apply and sustain those practices in daily work.
Topic: Product Development Flow
A regulated enterprise wants its Agile Release Train to move to Release on Demand. In the last PI, the train invested in test automation, deployment automation, and compliance controls.
Which is the best evidence that the ART is truly progressing toward releasing on demand?
Best answer: D
Explanation: Release on Demand is validated by evidence that the system is continually production-ready, not by plans or tool installation. The strongest indicator combines automation, built-in quality, and governance readiness by showing repeatable deployments that can be released at the business’s discretion.
Topic: Building a Foundation with Mindset, Values and Principles
Midway through a PI, Product Management asks the ART to “quickly add” a new feature they believe will improve customer outcomes. Several teams are already working near capacity, and there are known cross-team dependencies. As the RTE, you want to respond in a way that reinforces transparency and trust before any commitment is made.
What is the FIRST thing you should ask for or make visible to the ART and stakeholders?
Best answer: A
Explanation: Transparency supports trust by making the real constraints and tradeoffs visible so decisions can be made with shared facts. Before accepting new work mid-PI, the ART should surface current capacity, progress, and how the change would affect committed PI objectives and cross-team dependencies. That information enables an informed, aligned decision rather than opinion-based negotiation.
Topic: Building a Foundation with Mindset, Values and Principles
A company is organized in functional silos (UX, architecture, development, test, operations). Features routinely wait in queues for specialized teams, and work is frequently “done” by one group but blocked waiting for the next.
Leadership is considering reorganizing around a development value stream for its main customer product. Which comparison best explains why this would likely improve delivery?
Best answer: B
Explanation: Value-stream organization improves delivery primarily by optimizing flow of value to the customer. By aligning people to the steps needed to deliver value, teams become cross-functional and can reduce handoffs, queues, and rework created by functional silos. This shortens lead time and increases predictability without relying on more coordination layers.
Topic: Product Development Flow
During PI Planning, a team on an Agile Release Train estimates they have 120 story points of capacity for the PI. Their draft plan commits to 165 points and includes two features with unresolved external dependencies. The Product Manager wants to keep all features “to hit the PI Objectives,” and the team states they will “work nights if needed.” As the Release Train Engineer, what is the best next action?
Best answer: A
Explanation: The plan shows clear overcommitment (committed work exceeds capacity) and unmanaged dependency risk. In SAFe, the right response in PI Planning is to re-plan: reduce or split scope, resequence work, and make dependency owners and timing explicit so the PI plan is realistic and flow-oriented.
Topic: Product Development Flow
A Product Manager is preparing an experiment to validate an onboarding problem discovered in Design Thinking. Which option contains the best problem statement and success metric (evidence) to validate whether the experiment is working?
Best answer: D
Explanation: A good experiment problem statement is specific about the user and the undesired outcome, and the success metric measures an observable behavioral change. The best metric is outcome-based, includes a baseline, and is time-bound so the team can validate progress with evidence rather than activity.
Topic: Establishing Team and Technical Agility
Your organization is forming its first Agile Release Train (ART) to “deliver faster.” An executive asks whether the ART should be set up with a fixed, repeatable schedule, but provides no details about what the train will deliver.
Which question should you ask first before recommending how to set up the ART?
Best answer: B
Explanation: An ART is a long-lived team of teams organized around a value stream and aligned to deliver value predictably. Its cadence is timeboxed (iterations within a PI), enabling synchronization, integration, and frequent evaluation of progress. Clarifying the intended value and the expected PI/iteration rhythm is the most foundational input before designing the train.
Topic: Building a Foundation with Mindset, Values and Principles
A bank describes a “loan fulfillment value stream” as the steps from customer application through underwriting, approval, funding, and ongoing servicing using its current systems and staff. In SAFe, what is this an example of?
Best answer: D
Explanation: This is an operational value stream because it focuses on how the business delivers value to customers through operational steps (application to servicing) using the current solution. A development value stream would instead describe how the bank designs, builds, and evolves the systems that enable loan fulfillment.
Topic: Product Development Flow
During PI Planning, a Product Manager asks the ART to “define the value” of a planned enhancement so it can be prioritized. Which statement best describes value as a customer outcome rather than an internal output?
Best answer: A
Explanation: In SAFe, value is best expressed as the outcome a customer achieves, not the solution produced. A customer outcome is observable in customer behavior or results (for example, time saved, errors reduced, satisfaction increased) and can be measured to confirm value delivery.
Topic: Exploring Lean Portfolio Management (LPM)
A portfolio manager wants to use an AI assistant to quickly draft an Epic Hypothesis Statement for “AI-assisted claims triage” in a regulated business. The AI tool cannot be given customer PII, and humans remain accountable for decisions. What is the best next step to optimize value delivery and flow while ensuring the epic is validated with measurable outcomes and leading indicators?
Best answer: B
Explanation: In SAFe LPM, an epic should be framed as a hypothesis and validated with evidence before significant investment. The best option uses AI to accelerate drafting while explicitly identifying measurable outcomes and leading indicators that will prove or disprove assumptions via an MVP. It also respects guardrails by keeping humans accountable and avoiding restricted data.
Topic: Building a Foundation with Mindset, Values and Principles
An ART is repeatedly missing PI Objectives. During the PI, work often pauses while teams wait days for an Architecture Review Board or steering committee decision on routine trade-offs (scope swaps, design choices, sequencing). WIP is growing, predictability is dropping, and teams do rework when late decisions change direction.
In SAFe terms, what is the most likely underlying cause?
Best answer: B
Explanation: The strongest clue is that routine, frequent decisions are being escalated to centralized bodies, creating approval queues. In SAFe, failing to decentralize day-to-day decisions (while keeping governance via intent and guardrails) slows flow, increases WIP, and harms predictability. Decentralizing with clear decision rules reduces delays without losing control.
Topic: Adapting and Thriving with SAFe
An ART has five Agile teams split across three time zones. Most PI work requires cross-team integration, but dependencies are being discovered late, creating queues for shared components and causing rework near the end of each iteration. As a SAFe leader, what action best optimizes value delivery and flow while maintaining alignment and quality?
Best answer: C
Explanation: High dependency density plus distributed execution increases coordination costs and the risk of late integration surprises. SAFe optimizes flow by aligning teams on a shared cadence and making dependencies visible and actively managed through ART-level planning and synchronization. This improves integration quality and reduces waiting and rework driven by unmanaged handoffs.
Topic: Establishing Team and Technical Agility
An Agile Release Train (ART) wants to adopt continuous deployment because production releases currently require many manual steps and outcomes vary by who performs them. Which approach is NOT aligned with continuous deployment in SAFe?
Best answer: C
Explanation: Continuous deployment aims to remove manual handoffs by automating the path to production. Automation and versioned scripts make deployments consistent and repeatable across environments and over time. Keeping releases dependent on a human-run runbook maintains variability and manual effort, working against the goal.
Topic: Adapting and Thriving with SAFe
An ART has missed many PI objectives for the last two PIs. WIP keeps increasing, predictability is dropping, and rework from late defects is growing. Although PI objectives are clear at PI Planning, the same systemic issues recur every iteration. The RTE notes the ART has skipped Inspect and Adapt and team retrospectives produce actions that are not tracked or given capacity.
What is the most likely underlying cause in SAFe terms?
Best answer: B
Explanation: A Continuous Learning Culture enables relentless improvement by turning feedback and metrics into prioritized improvement work and experimentation. When Inspect and Adapt and retrospectives are skipped, systemic problems repeat, and flow and quality degrade over time. The symptoms persist because the ART is not learning and adapting its way of working.
Topic: Adapting and Thriving with SAFe
An insurer has mapped an operational value stream for “Handle a Claim” and identified the supporting development value stream that builds and evolves the claims platform. Leaders want to reorganize around value and decide how to use Agile Release Trains (ARTs).
Which statement is NOT aligned with SAFe guidance on how value streams and ARTs relate?
Best answer: C
Explanation: In SAFe, value streams help identify how value flows to the customer, and ARTs are organized to continuously deliver that value. ARTs are designed to be long-lived and stable, typically aligned to one development value stream or a clear slice of it. Treating an ART as a temporary project team breaks the organizing-around-value intent and reduces flow and learning continuity.
Topic: Adapting and Thriving with SAFe
A product organization is overwhelmed by feature requests and fast-moving competitors. Instead of prioritizing by the number of features delivered or team utilization, leaders decide to rank work by measurable customer outcomes (e.g., onboarding completion) and to use frequent feedback and experiments to validate value.
Which SAFe concept best matches this approach?
Best answer: D
Explanation: In the digital age, outputs (features shipped) are a weak proxy for value because markets and customer needs change quickly. Customer Centricity and Design Thinking focuses prioritization on real customer problems and measurable outcomes, using rapid learning loops to confirm what actually delivers value.
Topic: Leading the Change
An organization has launched two Agile Release Trains and is trying to sustain Lean-Agile ways of working. To “reduce overhead,” leaders stop funding internal Agile coaching and cancel Communities of Practice, telling teams to learn by sharing tips informally during PI Planning.
What is the most likely near-term impact of this decision?
Best answer: B
Explanation: Communities of Practice and internal coaching accelerate learning, spread proven practices, and create lightweight alignment across teams. Removing them typically causes teams to diverge in how they work and solve problems, which quickly shows up as more variability, rework, and slower flow. The near-term result is reduced predictability and less reliable delivery within the PI.