SAFe-Agilist Practice Question: Building a Foundation with Mindset, Values and Principles
A SAFe Release Train Engineer (RTE) notices that teams are frequently waiting for approvals from a centralized architecture board before starting any design work. This delay causes the Program Increment (PI) objectives to slip. Which SAFe Lean-Agile Principle is most directly violated by this approval process?
⚠ Common exam trap
The trap here is focusing on the visible queue and selecting 'Visualize and limit WIP' instead of recognizing that the root cause is the centralized decision-making that creates the queue.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Decentralize decision-making
The centralized architecture board creates a bottleneck that contradicts the SAFe principle of decentralizing decision-making. This principle requires pushing decisions to the lowest level to enable fast flow and innovation. By forcing teams to wait for approvals, the organization slows down delivery and fails to empower teams, directly undermining the principle.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Apply cadence, synchronize with cross-domain planning
Why it's wrong here
Cadence and synchronization help manage variability and dependencies, but the core issue here is the bottleneck created by centralized approvals. While the delay disrupts cadence, the principle most directly violated is the need to decentralize decision-making to enable flow. The approval board creates a queue that impedes fast, local decisions.
- ✗
Visualize and limit WIP, reduce batch sizes, and manage queue lengths
Why it's wrong here
This principle addresses flow efficiency by limiting work in process and reducing queues. While the approval process creates a queue, the root cause is the centralized decision-making that creates the wait. The principle of decentralizing decision-making is more directly violated because it targets the authority structure causing the bottleneck.
- ✓
Decentralize decision-making
Why this is correct
This principle advocates pushing decisions to the lowest level possible to enable fast flow and innovation. The centralized architecture board creates a bottleneck, forcing teams to wait for approvals, which slows down delivery and violates the principle. By decentralizing design decisions, teams can proceed autonomously, reducing delays and aligning with the principle.
- ✗
Assume variability; preserve options
Why it's wrong here
This principle encourages keeping options open to manage uncertainty. The approval process does not directly limit options; it delays decisions. The primary violation is the lack of decentralized authority, which prevents teams from making timely design choices. Thus, this principle is not the most directly undermined.
About these practice questions
Courseiva writes every SAFe-Agilist question from scratch — 315 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Scaled Agile exam blueprint
This SAFe-Agilist practice question is part of Courseiva's free Scaled Agile certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAFe-Agilist exam.