Get Scaled Agile SAFe-SPC Exam Practice Questions - Real and Updated

Answer : B, E

Transparency (B) and servant leadership (E) are explicit SAFe core values and practices that foster trust. Transparency provides visibility into goals, progress, and problems. Servant leadership builds trust through support and empowerment.

Decentralization of control (A) supports autonomy, but transparency and servant leadership are directly linked to trust. Reporting (C) and U-curve optimization (D) are not primary drivers of trust in SAFe.

SAFe 6.0 Website: Core Values

SPC 6.0 Guide: ''Trust is established through transparency and servant leadership.''

Answer : B

SAFe differentiates backlogs from traditional queues. Backlogs are ordered lists of work items and are actively managed and prioritized by Product Owners or Product Management. They are not unmanaged queues where work simply accumulates. Backlogs support flow by ensuring the most valuable items are always ready for selection.

''Backlogs are not queues. They are actively managed, prioritized, and refined so that they contain ready work for teams to select. In contrast, queues are unmanaged holding areas that create delays and waste.''

(Source: SAFe 6.0 Framework: Backlog; SPC 6.0 Guide ''Building Solutions with Agile Product Delivery'')

===========

Answer : C

The ROAM technique (Resolved, Owned, Accepted, Mitigated) is used during Planning Interval (PI) Planning to manage and categorize ART PI Risks. In the PI Planning session, all identified risks are discussed and then categorized using the ROAM framework, which helps teams and stakeholders clarify ownership, mitigation strategies, and acceptance of each risk. According to the SAFe 6.0 official guidance:

'During PI Planning, teams identify program risks and then use the ROAM technique to classify each risk as Resolved, Owned, Accepted, or Mitigated. This collaborative activity ensures transparency and allows teams to address significant risks before proceeding.'

This activity does not take place during backlog refinement, ART syncs, or general team management; it is specific to the PI Planning event.

SAFe 6.0 Website: PI Planning and ROAM

SAFe Practice Consultant SPC (6.0) Training Guide --- 'Launching an Agile Release Train' Module

New Terminology: 'Program PI Risks' are now referred to as 'ART PI Risks'

Answer : A

Features in SAFe should be right-sized, delivering value and being small enough for incremental delivery within a PI. If the current backlog items are too large (''big tasks''), the best technique is to split them into smaller, more manageable Features. This enables meaningful WSJF prioritization and supports flow-based delivery.

SAFe 6.0 Website: Features and Capabilities

SPC 6.0 Guide: ''Right-size Features to fit within a PI for effective prioritization and delivery.''

===========

Answer : C

SAFe recommends a Program Predictability Measure target of 80--100%. This range is considered healthy for Agile Release Trains, demonstrating that teams are reliably delivering on their committed PI Objectives while still allowing for adaptation and innovation.

SAFe 6.0 Website: Program Predictability Measure

SPC 6.0 Guide: ''The predictability measure is healthy when it is consistently between 80% and 100%.''

===========