.png&w=3840&q=75)
Question bank
SAFe Agilist (SA)
43 SAFe Agilist (SA) questions with the correct answer and a written explanation, organised across 6 exam domains.
- 43 questions
- 6 domains
- Foundation level
Question index
Jump straight to any question. Answers and explanations are inline.
- Agile Product Delivery · 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
- Digital Age and Business Agility · 14, 15, 16, 17, 18, 19
- Leading the Change · 20, 21, 22
- Lean Portfolio Management · 23, 24, 25, 26, 27, 28
- Lean-Agile Leaders · 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40
- Team and Technical Agility · 41, 42, 43
Agile Product Delivery
13 questions in this domain
- Question 1Single Choice
Which belief best represents the 'Confusing Business Agility with Team Agility' trap?
- AThe organization is agile because its teams use Scrum.Correct answer
- BScrum teams inspect and adapt every iteration.
- CPortfolio flow affects organizational agility.
- DBusiness value is delivered only at the team level.
Why this is the answer
The trap is assuming an organization is agile just because teams run Scrum. Business agility is broader than team-level process adoption.
- Question 2Multiple Select
Which statements reflect the trap of confusing Business Agility with Team Agility? Select all that apply.
- AAssuming Scrum adoption creates enterprise agility.Correct answer
- BUsing team agile maturity as the only measure of organizational agility.Correct answer
- CFocusing on customer outcomes when prioritizing work.
- DCollaborating across business and technology.
Why this is the answer
The correct choices show team-level practices being treated as organization-wide agility. The other options describe healthy behaviors rather than traps.
- Question 3Interactive
Review the logic in the code block. Which common trap does the condition represent?
- AConfusing Business Agility with Team AgilityCorrect answer
- BLocal Optimization
- CMistaking Agility for Working Faster
- DContinuous Improvement
Why this is the answer
The code makes business agility conditional on teams using Scrum. This is the trap of confusing business agility with team agility.
- Question 4Single Choice
What is the central concern of the Local Optimization pitfall?
- AImproving one department's speed at the expense of the wholeCorrect answer
- BMaximizing end-to-end customer value
- CEncouraging cross-functional collaboration
- DAligning metrics with enterprise goals
Why this is the answer
Local optimization means improving one area at the expense of the whole. It ignores end-to-end value and overall system performance.
- Question 5Multiple Select
Which statements describe the Local Optimization pitfall? Select all that apply.
- AImproving a department without considering the value stream.Correct answer
- BMaking one stage faster but slowing the overall system.Correct answer
- CImproving the whole delivery system.
- DUsing enterprise-level flow metrics.
Why this is the answer
Both correct answers show a sub-optimizing focus on one part rather than the whole value stream. Good agile practice optimizes the entire system.
- Question 6Interactive
Review the code block. Which pitfall is shown by checking only department-level results?
- ALocal OptimizationCorrect answer
- BTeam Agility
- CWorking Faster
- DCustomer Centricity
Why this is the answer
The code treats the department metric as success. This reflects local optimization because it ignores overall enterprise outcomes.
- Question 7Single Choice
What does the trap of mistaking agility for working faster usually emphasize?
- AIncreasing velocity rather than delivering valueCorrect answer
- BReducing lead time while improving quality
- CImproving customer satisfaction
- DEliminating non-value-added work
Why this is the answer
Mistaking agility for working faster focuses on speed and output. It does not check whether value is genuinely delivered to customers.
- Question 8Multiple Select
Which behaviors indicate the trap 'Mistaking Agility for Working Faster'? Select all that apply.
- ATreating higher team velocity as proof of agility.Correct answer
- BFavoring output speed over delivered customer value.Correct answer
- CMeasuring customer outcomes.
- DReducing batch sizes to improve flow.
Why this is the answer
Using velocity as the main sign of agility and prioritizing output speed over customer value are examples of the trap. The other options are healthy flow practices.
- Question 9Interactive
Review the code block. Which common trap is represented by the condition based on velocity?
- AMistaking Agility for Working FasterCorrect answer
- BConfusing Business Agility with Team Agility
- CLocal Optimization
- DPortfolio Prioritization
Why this is the answer
The condition uses velocity as the sole indicator of agility. That is the trap of mistaking agility for working faster.
- Question 10Single Choice
According to the playbook, what should be preferred over merely working faster?
- ADelivering valueCorrect answer
- BHigh throughput
- CMore story points
- DFull utilization
Why this is the answer
The playbook warns against focusing on working faster. Agility should focus on delivering value, not just increasing speed.
- Question 11Multiple Select
Which statements correctly distinguish business agility from team agility? Select all that apply.
- ATeam-level Scrum does not automatically make an organization business agile.Correct answer
- BBusiness agility extends beyond the team and includes the whole organization.Correct answer
- CIf every team uses Scrum, business agility is guaranteed.
- DTeam agility and business agility are identical.
Why this is the answer
Business agility includes organizational, portfolio, and customer outcomes. Team Scrum alone is not proof of business agility.
- Question 12Interactive
Review the function in the code block. Which trap is represented by its return condition?
- AConfusing Business Agility with Team AgilityCorrect answer
- BLocal Optimization
- CMistaking Agility for Working Faster
- DValue Stream Optimization
Why this is the answer
The function assumes every team using Scrum means business agility. That is the confusion between business agility and team agility.
- Question 13Single Choice
What is a possible outcome of applying the Local Optimization pitfall?
- AIt can harm the overall flow of valueCorrect answer
- BIt guarantees faster customer delivery
- CIt improves enterprise-wide performance
- DIt increases alignment with business goals
Why this is the answer
Local optimization can hurt the overall value stream. The other choices describe beneficial outcomes, not consequences of this trap.
Digital Age and Business Agility
6 questions in this domain
- Question 14Single Choice
What is a common trap when an organization confuses business agility with team agility?
- AAssuming Scrum teams mean the organization is agileCorrect answer
- BApplying Lean principles at the portfolio level
- CMeasuring time-to-market for a value stream
- DAligning work to customer value
Why this is the answer
Business agility requires the entire organization to adapt and deliver value, not just teams. The trap is assuming that team-level Scrum adoption automatically makes the enterprise agile.
- Question 15Multiple Select
Which examples demonstrate the 'Local Optimization' pitfall in a SAFe transformation?
- AImproving one department's speed while delaying the end-to-end value streamCorrect answer
- BMaking a function faster without considering the downstream impactCorrect answer
- CReducing handoff delays across the entire value stream
- DPrioritizing overall customer outcome over a team's local metric
Why this is the answer
Local optimization improves one part of the system at the expense of the whole. Actions that improve end-to-end flow and customer outcomes are the opposite of this trap.
- Question 16Interactive
Inspect the metrics listed in the code block. Which one is the strongest indicator of business agility?
- ATime-to-marketCorrect answer
- BTeam velocity
- CStory points completed
- DLocal efficiency
Why this is the answer
Business agility is measured by outcomes such as time-to-market, not by internal team throughput metrics like velocity or story points.
- Question 17Single Choice
Which choice best describes the trap of mistaking agility for 'working faster'?
- AOur velocity increased, so we are more agileCorrect answer
- BWe reduced cycle time for the entire value stream
- CWe improved customer satisfaction through shorter feedback loops
- DWe eliminated cross-team dependencies
Why this is the answer
Increasing velocity may simply mean teams are doing more work faster. Agility is about adapting to change and delivering business value, not maximizing throughput.
- Question 18Multiple Select
Which practices support true business agility rather than local optimization?
- AAlign incentives to end-to-end value deliveryCorrect answer
- BUse cross-functional collaboration to improve flowCorrect answer
- CMeasure success by business outcomesCorrect answer
- DMaximize one department's utilization
Why this is the answer
Business agility requires optimizing the entire value stream, aligning on business outcomes, and collaborating across functions. Maximizing one department's utilization can create local optimization.
- Question 19Interactive
What is the correct interpretation of the status variable shown in the code block?
- AIt proves the organization has achieved business agility
- BIt demonstrates team-level agility but not business agilityCorrect answer
- CIt guarantees faster delivery and improved outcomes
- DIt ensures no local optimization will occur
Why this is the answer
All teams trained in Scrum is a team-level achievement. Business agility also requires enterprise-wide alignment, rapid adaptation, and continuous delivery of customer value.
Leading the Change
3 questions in this domain
- Question 20Single Choice
Which common trap occurs when an enterprise believes that team-level Scrum adoption automatically makes the whole organization agile?
- AConfusing Business Agility with Team AgilityCorrect answer
- BThe Local Optimization Pitfall
- CMistaking Agility for Working Faster
- DIgnoring Lean Budgets
Why this is the answer
Business agility requires enterprise-wide alignment of strategy, flow, and customer outcomes. Team-level Scrum alone is not sufficient, so this is confusing business agility with team agility.
- Question 21Multiple Select
Which two statements describe common traps in an agile transformation? (Choose two.)
- AImproving one department's cycle time while slowing the overall value streamCorrect answer
- BIncreasing team velocity without verifying that the delivered solutions solve customer problemsCorrect answer
- CReleasing small increments frequently to gain fast customer feedback
- DAligning team objectives to enterprise strategic themes
Why this is the answer
The first option is local optimization; the second is mistaking velocity for agility. The other two are healthy agile behaviors, not traps.
- Question 22Interactive
Based on the metrics shown in the code block, which common trap is most clearly illustrated?
- AMistaking Agility for Working FasterCorrect answer
- BConfusing Business Agility with Team Agility
- CThe Local Optimization Pitfall
- DDeferring the Agile Release Train
Why this is the answer
The metrics focus on velocity and output while ignoring customer outcomes and the ability to reprioritize. This is the trap of mistaking agility for merely working faster.
Lean Portfolio Management
6 questions in this domain
- Question 23Single Choice
Why is it a trap to assume that teams doing Scrum means the organization has achieved business agility?
- AIt ignores that business agility requires alignment across the entire organization.Correct answer
- BIt slows down the adoption of team-level practices.
- CIt eliminates the need for Lean Portfolio Management.
- DIt limits the use of Scrum to one department.
Why this is the answer
Business agility is broader than team agility. Scrum at the team level does not guarantee enterprise-wide responsiveness, strategy alignment, or Lean Portfolio Management.
- Question 24Multiple Select
Which outcomes are typical of the 'Local Optimization' pitfall? Select two.
- AOne department improves its speed.Correct answer
- BEnd-to-end system flow often worsens.Correct answer
- CThe entire value stream becomes more efficient.
- DCross-departmental collaboration consistently increases.
Why this is the answer
Local optimization improves a silo but can suboptimize the whole system. It does not guarantee value stream efficiency or increased collaboration.
- Question 25Interactive
Review the JSON dashboard. Which pattern reflects the 'Mistaking Agility for Working Faster' trap?
- AVelocity rises while quality falls.Correct answer
- BCycle time remains unchanged.
- CPredictability stays above target.
- DWork in process consistently decreases.
Why this is the answer
The trap is focusing on increasing velocity without considering quality. Rising velocity with declining quality points to 'working faster' rather than true agility.
- Question 26Single Choice
What is a key sign of the local optimization pitfall?
- AA department improves its performance but the overall organization loses value.Correct answer
- BThe whole value stream increases throughput.
- CCapacity and demand are balanced.
- DPortfolio decisions are tied to strategic themes.
Why this is the answer
The local optimization pitfall occurs when one department gains speed at the expense of end-to-end value delivery. Whole-system performance often drops.
- Question 27Multiple Select
Which two statements reflect the difference between business agility and team agility?
- ABusiness agility requires enterprise-wide strategy and portfolio responsiveness.Correct answer
- BTeam agility alone ensures fast value delivery across the organization.
- CBusiness agility considers the entire value stream.Correct answer
- DTeam agility is sufficient for Lean Portfolio Management.
Why this is the answer
Business agility includes strategy and portfolio responsiveness across the value stream. Team agility is necessary but not sufficient for enterprise agility.
- Question 28Interactive
Review the CSV delivery summary. What does the data demonstrate?
- ADepartments optimized locally while the whole value stream suffered.Correct answer
- BThe organization improved cross-functional flow.
- CLean Portfolio Management is no longer needed.
- DAll departments increased business agility.
Why this is the answer
The CSV shows department velocity improving while value stream flow declines. That is the local optimization pitfall in action.
Lean-Agile Leaders
12 questions in this domain
- Question 29Single Choice
What is the main danger of assuming that an organization is agile just because its teams use Scrum?
- AIt causes the organization to overinvest in Scrum training.
- BIt confuses team-level agility with business agility.Correct answer
- CIt stops teams from using iterative development.
- DIt automatically decreases time-to-market for all products.
Why this is the answer
Business agility requires coordinated strategy, investment, and customer responsiveness across the enterprise. Team-level Scrum alone cannot deliver those enterprise-wide capabilities.
- Question 30Multiple Select
Which two examples illustrate the local optimization pitfall in a Lean-Agile transformation?
- ASpeeding up one department while creating more rework for downstream teams.Correct answer
- BForming cross-functional teams to reduce handoffs across departments.
- CMaximizing utilization in one component team even though it increases inventory waiting elsewhere.Correct answer
- DAligning team incentives with the strategic themes of the portfolio.
Why this is the answer
Local optimization suboptimizes the whole value stream. Cross-functional teams and strategic alignment improve total system performance rather than favor one area.
- Question 31Interactive
Use the exhibit to select the signal that most clearly shows the organization is mistaking team-level agility for business agility.
- AThe number of Scrum teams is 35.
- BTeams release an increment every two weeks.
- CPortfolio-level agility and customer value tracking have not started.Correct answer
- DThere are fewer than 50 Scrum teams.
Why this is the answer
Team-level indicators like Scrum team count and bimonthly releases do not equal business agility. The absence of portfolio-level and customer-value capability exposes the confusion.
- Question 32Single Choice
Which statement best contrasts agility with simply working faster?
- AAgility is about delivering customer value and adapting; working faster is primarily about increasing throughput.Correct answer
- BAgility requires a fixed project plan; working faster requires continuous change.
- CAgility can be measured by story points; working faster is measured by customer satisfaction.
- DAgility means minimizing meetings; working faster means promoting innovation.
Why this is the answer
Agility is the ability to respond and deliver value. Merely increasing throughput can create waste if it does not deliver outcomes or improve responsiveness.
- Question 33Multiple Select
Which two leadership actions help avoid the local optimization pitfall?
- ADecompose goals by department to maximize local performance.
- BOptimize the full value stream instead of a single function.Correct answer
- CBalance local efficiency with the speed of the entire system.Correct answer
- DReward only the department that completes the most tasks each iteration.
Why this is the answer
Lean-Agile leaders look at end-to-end flow and enterprise value. Department-level incentives encourage silo behavior and local optimization.
- Question 34Interactive
Using the exhibit, select the observation that most strongly indicates agility is being mistaken for working faster.
- AStory points per sprint increased by 18%.
- BCycle time decreased by 11%.
- CProgress is evaluated by speed metrics while customer value is absent.Correct answer
- DProduction incidents increased by 20%.
Why this is the answer
Velocity and cycle time are throughput measures. Treating them as progress without measuring customer value and quality is the 'working faster' trap.
- Question 35Single Choice
Which definition best describes Business Agility in SAFe?
- AThe ability of an enterprise to adapt quickly to market change and deliver innovative solutions.Correct answer
- BThe practice of conducting daily stand-up meetings in all teams.
- CThe discipline of increasing the amount of output in each sprint.
- DThe use of a centralized project office to coordinate all work.
Why this is the answer
Business Agility is the enterprise-wide ability to respond to change and thrive by delivering customer-centered value. Team Scrum, output, and project offices are not the definition.
- Question 36Multiple Select
Which two statements explain why team agility alone is insufficient for business agility?
- ABusiness agility requires portfolio strategy and customer responsiveness across the whole enterprise.Correct answer
- BTeam-level Scrum is sufficient if teams release frequently.
- CTeam agility does not guarantee that the enterprise can quickly shift investments and direction.Correct answer
- DImproving engineering practices can replace enterprise-level business agility.
Why this is the answer
Business agility extends beyond teams to the portfolio, customers, and enterprise strategy. Frequent releases and strong engineering practices are necessary but not sufficient.
- Question 37Interactive
Review the exhibit and choose the scenario that best illustrates the local optimization pitfall.
- ADepartment A shipped 40% more items per month.
- BDepartment B experienced 35% more rework.
- CDepartment A improved local throughput while overall value stayed the same.Correct answer
- DTotal customer value remained unchanged.
Why this is the answer
Gains in one department did not improve customer value and created waste upstream. This is a classic local optimization pitfall.
- Question 38Single Choice
Why is increasing velocity by itself an inadequate indicator of business agility?
- AVelocity does not measure customer value and may hide poor quality or lack of adaptability.Correct answer
- BVelocity cannot be used in a Lean-Agile organization.
- CVelocity is a portfolio metric with no team-level meaning.
- DVelocity is a financial indicator reported once a quarter.
Why this is the answer
Velocity only measures output. Business agility requires value, quality, and the ability to respond to change, none of which are captured by velocity.
- Question 39Multiple Select
Which two behaviors are consistent with Lean-Agile Leadership?
- AReviewing only department-level performance metrics.
- BEncouraging teams to adapt to customer feedback.Correct answer
- CLeading relentless improvement across the entire value stream.Correct answer
- DKeeping annual plans fixed regardless of market signals.
Why this is the answer
Lean-Agile Leaders promote customer-centricity and continuous improvement across value streams. Department-only metrics and fixed plans reinforce silos and rigidity.
- Question 40Interactive
Use the exhibit to identify the gap that is most likely to cause the organization to confuse team agility with business agility.
- AAll 20 teams completed Scrum training.
- BTeam Scrum exists, but portfolio flow and strategy-to-execution connection are missing.Correct answer
- CThere are 20 software teams.
- DA project management office was not created.
Why this is the answer
Business agility requires strategy, portfolio flow, and customer insight. Completing Scrum training at team level cannot close that gap.
Team and Technical Agility
3 questions in this domain
- Question 41Single Choice
In the Scaled Agile Framework, what is the primary difference between Business Agility and Team Agility?
- AWhole-enterprise agilityCorrect answer
- BSingle-team agility
- CIT-department agility
- DIncreased speed
Why this is the answer
Business Agility means the entire organization can respond to change; Team Agility applies only at team level.
- Question 42Multiple Select
According to SAFe, which of the following choices are recognized common traps when assessing organizational agility?
- AConfusing Business Agility with Team AgilityCorrect answer
- BOptimizing one department at the whole's expenseCorrect answer
- CMistaking agility for working fasterCorrect answer
- DPrioritizing value stream flow
Why this is the answer
The common traps are confusing enterprise agility with team-level Scrum, optimizing a local silo, and treating speed as agility. Value stream flow is a goal, not a trap.
- Question 43Interactive
Which agility traps are represented by the organization state in the code block? Select all that apply.
- AConfusing Business Agility with Team AgilityCorrect answer
- BLocal OptimizationCorrect answer
- CMistaking Agility for Working FasterCorrect answer
- DFocusing on Customer Value
Why this is the answer
The code block shows Scrum without business agility, departmental speed without total flow, and increased velocity without value. These represent three common agility traps.
Frequently asked questions
Everything about the SAFe Agilist (SA) question bank and how to use it.