SAFe-Agilist Practice Test 14 — 15 Questions

Question 1

A Portfolio Manager is concerned that the LPM team is making too many decisions centrally, slowing down value delivery. Which Lean Portfolio Management principle addresses this concern?

Accepted Answer

Decentralize decision-making to the lowest possible level.. Lean Portfolio Management advocates for decentralized decision-making, where decisions are made by those closest to the work, within the guardrails set by the portfolio. This principle reduces bottlenecks, speeds up delivery, and increases team empowerment. It directly addresses the Portfolio Manager's concern about centralization slowing down value delivery.

Answer

Centralize decision-making to ensure consistency and control.

Answer

Implement a strict change control board to approve all decisions.

Answer

Focus on maximizing utilization of all resources.

Question 2

A Scrum Master on a SAFe Agile Team notices that the team often starts new user stories before finishing current ones, leading to a large number of partially completed stories at the end of the Sprint. Which SAFe principle for Product Development Flow does this behavior violate?

Accepted Answer

Visualize and limit WIP, reduce batch sizes, and manage queue lengths.. The team's behavior of starting new stories before finishing current ones is a classic WIP violation. SAFe's flow principle explicitly states to visualize and limit WIP, reduce batch sizes, and manage queue lengths. By limiting WIP, the team would finish work before starting new items, reducing partially completed stories and improving flow. This principle is foundational to achieving predictable delivery.

Answer

Decentralize decision-making.

Answer

Apply systems thinking.

Answer

Assume variability; preserve options.

Question 3

During a Lean Portfolio Management (LPM) sync, the Portfolio Manager notes that a strategic theme focused on reducing time-to-market has not resulted in any funded epics. The team reviews the Strategic Portfolio Review and discovers that the Portfolio Kanban has a large number of epics stuck in the 'Funnel' state, and no new items have moved to 'Review' in the last two Program Increments. Which LPM action best addresses this bottleneck?

Accepted Answer

Apply WIP limits to the Funnel state and prioritize the strategic theme by moving the most aligned epics to Review.. The bottleneck stems from an overfull Funnel with no movement to Review. Applying WIP limits and prioritizing based on strategic alignment directly addresses the flow problem. This ensures that only the most valuable epics consume capacity, enabling the strategic theme to progress. The other options either increase WIP, bypass governance, or remove controls, all of which worsen the situation.

Answer

Increase the number of epics in the Funnel to ensure a robust pipeline for future funding.

Answer

Escalate the issue to the Lean Portfolio Management team to override the Portfolio Kanban and force epics into implementation.

Answer

Remove all WIP limits from the Portfolio Kanban to allow epics to move freely through the states.

Question 4

An Agile Team on a SAFe train is struggling with frequent build failures that disrupt the Continuous Delivery Pipeline. The team's developers often commit code that breaks the main branch, and it takes hours to restore. The Release Train Engineer asks the team to improve its technical agility. Which practice should the team adopt to most directly reduce build failures and maintain a continuously integrable codebase?

Accepted Answer

Implement a gated commit process where automated tests must pass before code is merged to the main branch.. The most direct way to reduce build failures and maintain a continuously integrable codebase is to adopt a gated commit process that validates changes with automated tests before merging. This prevents broken code from entering the main branch and aligns with SAFe's Continuous Integration and Built-in Quality practices. Other options rely on manual discipline, batch integration, or long-lived branches, all of which delay feedback and increase the risk of build failures.

Answer

Require developers to run all tests locally before committing, and trust them to report failures.

Answer

Create a separate branch for each feature and only merge to main after the feature is fully complete and tested.

Answer

Schedule a weekly integration day where all developers merge and fix issues together.

Question 5

A SAFe Agile Team is working on improving its technical agility and wants to strengthen its Continuous Integration practices. The team's Scrum Master suggests adopting specific technical practices that support frequent integration and early defect detection. Which two practices should the team implement to directly support these goals? (Choose two.)

Accepted Answer

Test-driven development (TDD) where tests are written before code.. Trunk-based development with short-lived branches and test-driven development both directly support Continuous Integration by enabling frequent integration and early defect detection. Trunk-based development reduces merge conflicts and keeps the main branch healthy, while TDD provides a comprehensive automated test suite that validates changes quickly. The other options involve manual, delayed, or isolated practices that hinder continuous integration and early feedback.

Answer

Long-lived feature branches that isolate work until it is complete.

Answer

Manual regression testing performed at the end of each Iteration.

Answer

A dedicated integration team that merges all branches weekly.

Question 6

An Agile Team consistently meets its Iteration Goals, but the features it delivers frequently fail in the staging environment because unit tests pass while end-to-end behavior is broken. The team's Definition of Done currently stops at code review and unit tests. What is the most effective next step to improve Built-in Quality?

Accepted Answer

Extend the Definition of Done to require automated acceptance tests that verify end-to-end behavior in the pipeline before a story is considered complete.. The gap is that the Definition of Done stops short of verifying end-to-end behavior, so defects escape to staging. Adding automated acceptance tests that run in the pipeline extends the Definition of Done to cover real user flows and gives fast, repeatable feedback. Manual passes, design reviews, and scope reduction do not create the automated verification the team needs.

Answer

Add a manual regression test pass by a separate quality assurance specialist before each feature is declared done.

Answer

Reduce the scope of each Iteration so the team has more time to test manually before the end of the Iteration.

Answer

Ask the System Architect to review each feature design before development begins so defects are prevented upstream.

Question 7

Two Agile Teams on the same Agile Release Train regularly break each other's builds because they use different coding standards and inconsistent interface contracts. The Scrum Masters want to reduce integration friction without slowing either team. What should they do?

Accepted Answer

Facilitate a joint working agreement between the teams on coding standards and interface contracts, and make it visible in both teams' Definition of Done.. Broken builds caused by divergent standards and interface contracts are resolved by the teams themselves agreeing on shared technical conventions and making them visible in the Definition of Done. This keeps ownership local, preserves continuous integration, and supports Built-in Quality. Serialization, downstream repair, and top-down mandates all shift responsibility away from the teams without fixing the underlying inconsistency.

Answer

Have each team adopt its own standards and rely on the System Team to fix integration problems after the fact.

Answer

Ask the Release Train Engineer to serialize the teams' work so only one team commits to the shared codebase at a time.

Answer

Escalate to the System Architect to mandate a single coding standard and freeze interface changes for the remainder of the Program Increment.

Question 8

An Agile Release Train is striving to improve its product development flow. According to SAFe, which two actions are most effective in reducing batch sizes and thereby improving flow? (Choose two.)

Accepted Answer

Break features into smaller stories that can be completed within a single iteration.. Breaking features into smaller stories and delivering in smaller increments are two SAFe-recommended actions that directly reduce batch sizes. Smaller stories allow for faster completion and integration, while smaller releases shorten lead time and accelerate feedback. Both actions align with the principle of reducing batch sizes to improve flow and are essential for achieving continuous delivery.

Answer

Increase the number of features in the program backlog to provide more options.

Answer

Combine multiple features into a single large release to minimize deployment overhead.

Answer

Require each team to work on multiple features simultaneously to keep everyone busy.

Question 9

An Agile Team is consistently unable to complete its Iteration goals because unplanned work, such as production support and defect fixes, consumes a significant portion of its capacity. The team's Scrum Master wants to address this issue while maintaining technical agility. Which action best aligns with SAFe principles to improve the team's ability to meet its Iteration goals?

Accepted Answer

Reserve a portion of each Iteration's capacity for unplanned work and make it visible in the team's backlog.. Reserving capacity for unplanned work and making it visible in the backlog is the most effective SAFe-aligned approach. It allows the team to plan realistically, maintain a sustainable pace, and provide transparency to stakeholders about the impact of unplanned work. Other options either fail to address the root cause, disrupt the train's cadence, or rely on unsustainable practices like overtime or deferral.

Answer

Have the team work overtime to complete both planned and unplanned work.

Answer

Extend the Iteration length to three weeks to provide more time to absorb unplanned work.

Answer

Ask the Product Owner to prioritize only planned work and defer all unplanned work to the next Iteration.

Question 10

A SAFe Practitioner is analyzing a value stream and notices that work items often wait in a queue before being deployed to production. The team has automated testing and continuous integration, but deployment still requires manual approval from a change advisory board (CAB) that meets only once a week. What is the primary flow issue in this scenario?

Accepted Answer

The change advisory board (CAB) is a bottleneck that introduces a long queue and delays flow.. The weekly CAB meeting creates a queue that delays deployment, increasing lead time and disrupting flow. SAFe encourages reducing batch sizes and eliminating approval bottlenecks through automation and decentralized decision-making to achieve continuous delivery.

Answer

The deployment process is not automated, causing manual errors.

Answer

The team is not using a Program Kanban to visualize work.

Answer

The team lacks automated testing, causing delays.

Question 11

An Agile Team is consistently missing its PI objectives because unplanned work keeps interrupting their planned features. According to SAFe, what is the most effective way to improve flow and reduce the impact of unplanned work?

Accepted Answer

Reserve a portion of each iteration's capacity for unplanned work and buffer the PI plan accordingly.. Reserving capacity for unplanned work and buffering PI objectives is a SAFe recommended practice to manage variability and maintain flow. It allows teams to absorb interruptions without sacrificing commitments, leading to more predictable delivery. Other options either ignore the problem or worsen it by increasing pressure or batch size.

Answer

Extend the iteration length to provide more time to complete planned work.

Answer

Increase the team's velocity target to compensate for the unplanned work.

Answer

Ask the Product Owner to reject all unplanned work until the PI is complete.

Question 12

A SAFe Agilist is explaining the concept of 'Portfolio Vision' to a new LPM team. What is the primary purpose of the Portfolio Vision?

Accepted Answer

To describe the future state of the portfolio and align value streams toward common goals.. The Portfolio Vision communicates the future state of the portfolio, aligning value streams and stakeholders toward shared objectives. It provides strategic direction for decentralized decision-making and investment. It is not a tactical plan or budget document, but a high-level, inspirational description that guides the portfolio's evolution.

Answer

To provide a detailed list of features to be delivered in the next PI.

Answer

To outline the organizational chart and reporting structure of the portfolio.

Answer

To document the budgets allocated to each value stream for the fiscal year.

Question 13

During a PI System Demo, the Product Manager notices that a feature delivered by one team is technically complete but does not meet the intended business outcome because the team optimized for their local component rather than the full value stream. As a SAFe Agilist, what should you recommend to prevent this in the next PI?

Accepted Answer

Ensure the team's PI Objectives explicitly link to the ART's business outcomes and include cross-team dependencies in the program board.. The root cause is that the team optimized for local component completion rather than the full value stream. Aligning PI Objectives with business outcomes and making dependencies visible ensures the team understands the end-to-end impact of their work. This fosters collaboration across teams and helps the ART deliver features that achieve the intended business results, preventing technically complete but business-irrelevant deliveries.

Answer

Instruct the team to adopt a component team structure to increase specialization and delivery speed.

Answer

Require the team to demo only after all teams have completed their features to ensure a unified demo.

Answer

Ask the team to include a business owner in their daily stand-up to validate each task.

Question 14

A newly formed Lean Portfolio Management team is defining how investment funding will work across three Value Streams. Leadership wants funding to flow to persistent Value Streams rather than to individual projects, while still allowing periodic reallocation. Which approach aligns with Lean Portfolio Management's guidance on funding?

Accepted Answer

Provide persistent, largely stable funding to Value Streams, reviewed and adjusted periodically through Participatory Budgeting and the LPM team.. Lean Portfolio Management replaces project-based funding with persistent funding of Value Streams, because long-lived solutions need stable teams and predictable budgets. Stability is balanced by periodic Participatory Budgeting, where the LPM team and stakeholders review and adjust allocation. This combination lets the portfolio respond to strategy changes without forcing every initiative through a new project approval cycle.

Answer

Fund each Value Stream with a fixed lump sum for three years, with no review, to guarantee stability and eliminate overhead.

Answer

Allocate funding directly to individual Agile Teams based on their velocity, letting each team choose which epics to pursue.

Answer

Approve a fixed annual budget per project, requiring each project to submit a new business case before any scope change.

Question 15

A Release Train Engineer (RTE) notices that the ART's flow is frequently disrupted by late-breaking dependencies that are discovered during the iteration. Which SAFe practice best addresses this issue during PI Planning?

Accepted Answer

Conduct a formal dependency mapping session where teams identify and visualize cross-team dependencies on the ART board.. Formal dependency mapping during PI Planning allows teams to identify and visualize cross-team dependencies early, enabling proactive sequencing and adjustment. This SAFe practice reduces late-breaking surprises and helps maintain flow. Other options are either reactive or do not systematically address the root cause.

Answer

Allow teams to work independently and resolve dependencies as they arise during the iteration.

Answer

Increase the number of system demos to catch integration issues earlier.

Answer

Assign a dedicated integrator to each team to handle all external dependencies.