SAFe-Agilist Practice Test 13 — 15 Questions

Question 1

A SAFe Portfolio is struggling with slow decision-making and misalignment between strategy and execution. The Lean Portfolio Management (LPM) group decides to adopt Participatory Budgeting to improve agility. Which two statements accurately describe the purpose and mechanics of Participatory Budgeting in SAFe? (Choose two.)

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

It is a time-boxed event where stakeholders collectively decide how to allocate the portfolio budget to the most valuable epics.. Participatory Budgeting is a collaborative, time-boxed event that enables stakeholders to collectively allocate the portfolio budget to the most valuable epics, typically on a quarterly cadence aligned with the Portfolio Sync. This approach fosters alignment, agility, and shared ownership of funding decisions.

Answer

It focuses solely on reducing costs by cutting funding for all but the highest-priority initiatives.

Answer

It eliminates the need for any budgeting process by allowing teams to spend freely as long as they deliver value.

Answer

It requires the Portfolio Manager to unilaterally set the budget for each value stream based on historical spending.

Question 2

A SAFe Agile Team is preparing for its first Program Increment (PI) and wants to establish a solid foundation of technical agility. The team's Scrum Master suggests focusing on Built-in Quality practices. Which action best exemplifies applying Built-in Quality at the team level?

Accepted Answer

Defining a clear Definition of Done that includes automated testing and continuous integration criteria.. Built-in Quality in SAFe means quality is embedded in every step, not inspected at the end. A Definition of Done that includes automated testing and continuous integration ensures that every increment meets a consistent standard and that defects are prevented. Other options represent late-stage inspections or add handoffs and manual effort, which do not build quality into the product and can delay feedback.

Answer

Conducting a thorough manual code review after all development is complete for the Iteration.

Answer

Increasing the number of story points allocated to testing tasks in each Iteration.

Answer

Assigning a dedicated quality assurance specialist to test all features before the System Demo.

Question 3

A SAFe Portfolio is experiencing frequent changes in strategic direction, causing confusion among Agile Teams. The LPM group wants to ensure that teams understand the portfolio's strategic intent and can align their work accordingly. Which artifact should the LPM group use to communicate the portfolio's strategic themes and investment horizons?

Accepted Answer

Portfolio Vision. The Portfolio Vision is the primary artifact for communicating the portfolio's strategic themes, investment horizons, and future direction. It provides a shared understanding that guides teams in aligning their work with the portfolio's strategic intent, ensuring coherence and focus across all value streams.

Answer

Lean Business Case

Answer

Portfolio Kanban

Answer

Program Board

Question 4

An Agile Team is struggling with frequent integration issues because team members work on long-lived feature branches and merge infrequently. The team wants to improve its continuous integration practice. What is the most effective action to take?

Accepted Answer

Adopt trunk-based development where team members commit to a shared mainline at least daily and use automated tests to validate each integration.. The most effective action is to adopt trunk-based development with daily commits to a shared mainline and automated tests. This practice minimizes integration risk, provides rapid feedback, and keeps the codebase in a potentially shippable state. It directly addresses the root cause of long-lived branches and aligns with SAFe's emphasis on continuous integration as a foundation for technical agility.

Answer

Implement a code freeze two days before the end of the Iteration to allow time for integration.

Answer

Increase the frequency of merging by requiring team members to merge their branches at least once per week.

Answer

Assign a dedicated integration manager to manually merge all branches at the end of each Iteration.

Question 5

A large enterprise has established a Lean Portfolio Management (LPM) function. The Chief Technology Officer wants to ensure that funding decisions are made with the most current information and that teams can respond quickly to emerging opportunities. Which approach should the LPM function adopt to enable this?

Accepted Answer

Approve funding for epics on a cadence through the Portfolio Kanban, using Lean business cases and lightweight guardrails.. Lean Portfolio Management replaces annual, project-based funding with dynamic funding of epics through the Portfolio Kanban. Lean business cases and lightweight guardrails allow funding decisions to be made on a cadence, using the latest evidence. This enables fast reallocation of investment toward emerging opportunities while maintaining strategic alignment and oversight.

Answer

Fund value streams with fixed annual budgets and require detailed quarterly variance reports.

Answer

Create a separate funding committee that meets annually to allocate the entire portfolio budget.

Answer

Delegate all funding decisions to the Agile teams and let them self-organize their own budgets.

Question 6

A Release Train Engineer (RTE) notices that the ART consistently meets its PI Objectives, yet stakeholders complain about long delays between feature ideation and delivery. The RTE reviews the Value Stream and finds that features frequently wait in a 'ready' queue for weeks before development begins, even though teams are not fully utilized. Which action best addresses this situation according to SAFe's Product Development Flow principles?

Accepted Answer

Apply WIP limits to the 'ready' queue and pull features into development only when capacity is available.. The scenario describes a classic queueing problem: excessive WIP in the 'ready' state causing long lead times despite teams not being fully utilized. SAFe's Product Development Flow principle advocates limiting WIP and using a pull system to match demand with capacity. Applying WIP limits to the ready queue reduces the number of items waiting, thereby shortening wait times and improving overall flow efficiency.

Answer

Implement a new tool to track features more accurately in the ready queue.

Answer

Ask teams to work overtime to clear the ready queue faster.

Answer

Increase the number of features in the Program Backlog to keep teams busy and reduce idle time.

Question 7

A SAFe Agile Release Train (ART) is experiencing high variability in the arrival of new features, leading to uneven flow and frequent context switching. The RTE wants to apply Product Development Flow principles to stabilize the system. Which TWO actions should the RTE take? (Choose two.)

Accepted Answer

Use a Kanban board to visualize the workflow and explicitly manage queue sizes.. High variability in feature arrival disrupts flow. SAFe recommends implementing a pull system with WIP limits to cap work in process and using a Kanban board to visualize and manage queues. These practices reduce context switching, prevent overload, and create a more predictable flow. They directly address the root cause of uneven flow by controlling the amount of work entering the system and making bottlenecks visible.

Answer

Increase the batch size of features to reduce the number of handoffs.

Answer

Eliminate all buffers and slack time to maximize utilization.

Answer

Mandate that all teams work on the same feature simultaneously to synchronize delivery.

Question 8

A SAFe portfolio is transitioning from traditional project-based funding to Lean Portfolio Management. The Lean-Agile Center of Excellence (LACE) is coaching the LPM team on how to define and use 'guardrails' for the portfolio. Which statement best describes the purpose of portfolio guardrails?

Accepted Answer

They define the boundaries within which decentralized decisions can be made, aligning teams with strategy without prescribing solutions.. Portfolio guardrails are lightweight constraints that define the boundaries for decentralized decision-making. They include elements like strategic themes, investment horizons, and capacity allocation. By setting these boundaries, LPM ensures that teams can make fast, local decisions while remaining aligned with enterprise strategy, without prescribing specific solutions or technologies.

Answer

They specify the exact technologies and tools that teams must use for all epics.

Answer

They provide detailed instructions for teams on how to implement each epic.

Answer

They are mandatory policies that must be enforced by the Portfolio Manager to ensure compliance.

Question 9

An Agile Team is adopting SAFe and wants to ensure its work is integrated with other teams on the Agile Release Train. Which approach best supports continuous integration at the ART level?

Accepted Answer

Teams use a shared version control repository and integrate their code at least daily, with automated builds and tests.. The best approach is for teams to use a shared version control repository and integrate their code at least daily, supported by automated builds and tests. This practice enables early detection of integration issues, aligns with the ART's system-level Definition of Done, and ensures the solution is always in a potentially shippable state. It is a cornerstone of continuous integration and team and technical agility.

Answer

The Release Train Engineer coordinates a monthly integration event where all teams merge their code.

Answer

Each team maintains its own separate code repository and integrates only at the end of the Program Increment.

Answer

Each team integrates its code with the main branch only when a feature is fully complete and tested.

Question 10

A Lean Portfolio Management team is defining its investment strategy for the upcoming fiscal year. They want to allocate funding to value streams based on expected outcomes rather than traditional project-based budgets. Which SAFe approach best supports this?

Accepted Answer

The LPM team uses Participatory Budgeting to allocate a fixed budget to each value stream, which then decides how to invest it.. Participatory Budgeting is a key LPM practice that shifts funding from projects to value streams. It involves stakeholders in deciding how to allocate the portfolio budget, ensuring alignment with strategy and giving value streams autonomy to deliver outcomes. This approach supports decentralized decision-making and long-term funding for teams.

Answer

Epic Owners submit detailed business cases for each initiative, and the Portfolio Manager approves them individually.

Answer

The LPM team creates a detailed annual plan with specific features and delivery dates for each value stream.

Answer

Each value stream submits a request for funding to the PMO, which prioritizes based on ROI.

Question 11

A Lean Portfolio Management (LPM) team is implementing Participatory Budgeting. They have decided to allocate a fixed budget to each value stream based on historical spending. However, after two Program Increments, they notice that some value streams are consistently underspending while others are overspending, leading to unbalanced flow. What is the most likely cause of this issue?

Accepted Answer

The LPM team did not adjust budgets based on actual value delivery and changing strategic priorities.. Participatory Budgeting is not a one-time event; it requires ongoing adjustment based on value delivery and strategic changes. Fixed budgets based on historical spending ignore current realities, leading to misalignment and flow imbalances. The LPM team must regularly revisit and reallocate budgets through a participatory process to ensure that funding follows value and strategy, which is a core principle of Lean Portfolio Management.

Answer

The LPM team did not include the System Architect in the Participatory Budgeting process.

Answer

The value streams are not using the Portfolio Kanban to manage their epics.

Answer

The value streams are not using the SAFe Lean Budget Guardrails correctly.

Question 12

During an Iteration, an Agile Team discovers that a planned feature will require more effort than estimated due to unexpected complexity. The team wants to maintain their Iteration Goals and avoid accumulating technical debt. What is the most appropriate action?

Accepted Answer

Collaborate with the Product Owner to adjust the scope of the Iteration while maintaining the Iteration Goal.. When facing unexpected complexity, the team should collaborate with the Product Owner to adjust scope while preserving the Iteration Goal. This allows the team to deliver a high-quality Increment without overcommitting or accumulating technical debt. The Product Owner can reprioritize backlog items to ensure the most valuable work is completed. This approach reflects SAFe's emphasis on adaptability and decentralized decision-making.

Answer

Continue with the original plan and address any technical debt in the next Iteration.

Answer

Reduce the Definition of Done for this feature to complete it faster.

Answer

Work overtime to complete all planned work and meet the original commitment.

Question 13

An Agile Team on a SAFe Agile Release Train has been delivering usable increments every two weeks, but the System Demo frequently reveals that the increment does not work end-to-end with other teams' components. The Release Train Engineer asks the team to strengthen its contribution to the Continuous Delivery Pipeline. Which approach best helps the team ensure its increment is integrated and demonstrable at the System Demo?

Accepted Answer

Adopt trunk-based development with frequent commits to the main branch and automated tests that run on every commit.. The team needs to strengthen its Continuous Delivery Pipeline by integrating more frequently and automatically validating changes. Trunk-based development with frequent commits and automated tests on every commit reduces integration risk and ensures the increment is demonstrable. Other options either delay integration, add manual steps, or create bottlenecks, all of which fail to address the root cause of end-to-end integration problems.

Answer

Increase the length of the Iteration to three weeks to allow more time for manual integration and testing.

Answer

Assign a single integrator to combine all team members' work manually before the System Demo.

Answer

Have each developer work on a separate feature branch and merge all branches at the end of the Iteration.

Question 14

During a Program Increment, an Agile Team's Continuous Integration pipeline takes over four hours to run, so developers batch their commits and merge only at the end of the day. Integration failures now surface late, and the team misses several Iteration Goals. Which action best addresses the root cause while preserving the team's ability to deliver value each Iteration?

Accepted Answer

Split the pipeline into a fast commit stage that runs in minutes and a slower comprehensive stage that runs in parallel, so developers get rapid feedback.. The root cause is a slow feedback loop that forces batching. Splitting the pipeline into a fast commit stage and a slower parallel comprehensive stage lets developers integrate small changes frequently and learn about failures in minutes. More environments, local full runs, or nightly centralized testing all preserve the long feedback delay and therefore keep the batching behavior intact.

Answer

Move integration testing to the System Team and have them run the full pipeline nightly after all teams have merged their work.

Answer

Require developers to run the full pipeline locally before every commit and block merges until each developer reports a green run.

Answer

Increase the number of integration environments so multiple developers can run the full pipeline simultaneously.

Question 15

A SAFe portfolio is preparing for its first Participatory Budgeting event. The LPM team wants to ensure the event is effective. What is the primary purpose of Participatory Budgeting in Lean Portfolio Management?

Accepted Answer

To engage a broad set of stakeholders in deciding how to invest the portfolio's budget to best achieve strategic objectives.. Participatory Budgeting is a collaborative event where a broad set of stakeholders decide how to invest the portfolio's budget to achieve strategic objectives. It aligns funding with strategic themes and investment horizons, ensures transparency, and builds buy-in. It is not a simple vote, an annual historical budget, or an executive-only decision.

Answer

To give executives the final say on all funding decisions after teams present their ideas.

Answer

To allow teams to vote on which projects they want to work on next.

Answer

To approve the annual budget for each department based on historical spending.