SAFe-Agilist Practice Question: Building a Foundation with Mindset, Values and Principles
Exhibit
System Architecture Team Policy: 1. Architecture Runway is treated as an optional backlog item. 2. Decisions are deferred until the PI Planning event. 3. Developers must seek approval for all design changes. 4. Refactoring is only permitted during the Innovation and Planning iteration.
Refer to the exhibit. Which SAFe Lean-Agile Principle is most severely undermined by the Architecture Team's current policy?
⚠ Common exam trap
Candidates often confuse centralized architecture governance with Principle 9, incorrectly assuming that standardizing enterprise architecture requires centralized command and control rather than decentralized, guideline-based autonomous decision-making.
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
✓
Principle 9: Decentralize decision-making
The policy violates Principle 9, 'Decentralize decision-making.' By requiring approval for all design changes and deferring architecture decisions to a centralized PI event, the policy stifles team autonomy and slows delivery. This matters because bottlenecking design decisions prevents teams from reacting to local technical discoveries. In SAFe, successful scaling relies on empowering those closest to the work to make technical choices, ensuring the system remains agile and responsive to changing requirements.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Principle 1: Take an economic view
Why it's wrong here
While bottlenecking decisions does have economic consequences like increased cost of delay, the primary failure here is organizational governance. The policy creates a centralized control structure that prevents rapid local decision-making, which is a specific violation of the principle regarding how and where decisions should be made in organizations.
- ✓
Principle 9: Decentralize decision-making
Why this is correct
The policy requires centralized approval for design changes and restricts architectural evolution to specific time boxes. This directly contradicts the principle of decentralization, which encourages teams to own their local design decisions. By removing autonomy, the architecture team creates a massive bottleneck that hinders the agility of the entire release train.
- ✗
Principle 5: Base milestones on objective evaluation
Why it's wrong here
The policy mentions PI planning, which is a milestone, but the error is not about the evaluation of progress. The issue is the restriction of authority and technical flow. While poor architecture hampers evaluation, the root cause is the centralized control model that denies teams the authority to make technical trade-offs.
- ✗
Principle 2: Apply systems thinking
Why it's wrong here
Systems thinking focuses on the flow of value through the whole system. While this policy creates a bottleneck, it is specifically a failure of decision-making authority. Decentralizing decision-making is the specific tool SAFe uses to ensure that systems thinking can be applied effectively by the people actually doing the work.
About these practice questions
One of 315 original SAFe-Agilist practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.