Download SAFe Release Train Engineer.SAFe-SPC.Pass4Success.2026-03-30.47q.tqb

Enterprise Architects focus on cross-ART and cross-Value Stream strategy and technical alignment. Defining Solution design for Agile Release Trains (C) is the responsibility of Solution/System Architects at the ART or Solution Train level, not Enterprise Architects.''Enterprise Architects define and communicate a shared technical and architectural vision for the enterprise. Solution and System Architects design at the ART/Solution Train level.''(Source: SAFe 6.0 Framework: Enterprise Architect, Solution Architect)===========

The Architectural Runway in SAFe consists of the existing code, components, and technical infrastructure necessary to support the implementation of prioritized, near-term Features without excessive redesign and delay. Its importance is twofold:It supports a stable velocity (A): Teams need sufficient architectural runway to maintain a predictable velocity and reduce technical debt. As stated in SAFe, ''Architectural Runway enables teams to build features quickly and efficiently, thus maintaining stable velocity.''It iteratively evolves the architecture to meet changing needs (C): SAFe recommends an incremental and emergent architectural approach. The runway is not static; it evolves to meet the emerging business and technical requirements, ''just enough, just in time.''Incorrect options:B is incorrect---while documentation may be produced, the runway itself is not documentation but actual working infrastructure.D is incorrect---runway specifically supports technical changes, not nontechnical ones.SAFe 6.0 Website: Architectural RunwaySPC 6.0 Guide: 'The runway must be continually maintained and extended to provide the foundation for developing Features and Capabilities at a sustainable pace.'===========

SAFe provides multiple coordination mechanisms across Value Streams:Establishing Enterprise architecture (B): Ensures consistency and alignment of technical direction across Value Streams.Applying cadence and synchronization (D): Aligns events, releases, and activities, improving predictability and coordination.Creating a Portfolio Vision and Roadmap (F): Aligns multiple Value Streams around shared business outcomes and direction.Moving teams between Value Streams is discouraged as it disrupts team stability. The Portfolio is funded as a collection of Value Streams, not instead of them. The Value Stream Engineer role does not exist in SAFe.''SAFe coordinates across Value Streams through enterprise architecture, synchronization, and a common Portfolio Vision and Roadmap.''(Source: SAFe 6.0 Framework: Coordination across Value Streams; SPC 6.0 Guide, ''Reaching the SAFe Tipping Point'')===========

Program Portfolio Management (now commonly referred to as Lean Portfolio Management in SAFe 6.0) is accountable for:Strategy and Investment Funding: Ensuring the portfolio's investments align with the enterprise's business strategy.Agile Portfolio Operations (Program Management): Supporting program execution, including coordination and support across value streams.Governance: Assuring compliance, monitoring progress, and evaluating outcomes.SAFe 6.0 documentation emphasizes these three pillars as the core responsibilities of LPM/PPM.Option D omits program management, while B and C list activities or deliverables but not the full scope of responsibilities.SAFe 6.0 Website: Lean Portfolio ManagementSPC 6.0 Guide: 'Strategy and Investment Funding, Agile Portfolio Operations, and Lean Governance are the primary responsibilities of Lean Portfolio Management.'===========

Addressing bottlenecks is a flow accelerator in SAFe that directly focuses on increasing the effective throughput of value in the system. By identifying and resolving bottlenecks, teams and ARTs can deliver more value, faster.SAFe 6.0, ''Eight Flow Accelerators'' articleSPC 6.0 Guide, ''Accelerating to Business Agility''===========

Organizing around hierarchical functions often creates communication barriers, silos, and delays in decision-making. SAFe emphasizes organizing around value and cross-functional teams to address the communication and collaboration challenges inherent in traditional functional hierarchies.SAFe 6.0, ''Organize Around Value''SPC 6.0 Guide, ''Reaching the SAFe Tipping Point''===========

During PI Planning, there are two main team breakout sessions. In team breakout #2, teams address issues identified in the management review, rework their plans as needed, and finalize their PI Objectives and plans. This second breakout is specifically dedicated to refining and finalizing the team plans before the confidence vote.SAFe 6.0, ''PI Planning'' (Team Breakout Sessions)SPC 6.0 Guide, ''Launching an Agile Release Train''===========

A: During the Analysis step, research spikes (time-boxed investigations) are used to clarify feasibility, identify unknowns, and gather data for decision making.C: In the Funnel step, early research or spikes help determine if the Epic is even worth advancing, especially for innovations or high-risk items.Portfolio Backlog (D) is for items already accepted for future implementation; it's generally too late for basic research spikes. Implementing (B) is for execution, not discovery.SAFe 6.0 Website: Portfolio KanbanSPC 6.0 Guide: ''Spikes are often run during the Funnel and Analysis steps to clarify scope, feasibility, and business case.''===========