Scaled Agile SAFe Practice Consultant SPC (6.0) SAFe-SPC Exam Practice Test
Page: 1 / 14 Total 179 questions
Want more questions? Get Premium Access. ()
Question 1
Multiple ARTs in a Value Stream typically require coordination at the Value Stream Level.
Answer : A
In SAFe, when a solution requires more capacity than a single ART (Agile Release Train) can provide, multiple ARTs are grouped into a Solution Train. These ARTs work together within a Value Stream. The Value Stream level provides coordination, additional roles, and artifacts to align the multiple ARTs toward delivering larger, complex solutions.
''When multiple ARTs collaborate to build a solution, coordination at the Value Stream level is required. The Solution Train roles and events support alignment and integration of the work across ARTs and Suppliers.''
SAFe 6.0 Framework: Solution Train and Value Stream Level
SAFe 6.0 SPC Guide: ''Establishing Team and Technical Agility'' module
Question 2
SAFe assumes that programs commit to the key priorities within the current PI and provide a forecast for a few subsequent PIs.
Answer : A
During PI Planning, ARTs (programs) commit to the PI Objectives for the current Program Increment (PI) and, when possible, provide a forecast for the next few PIs. This is a key part of SAFe's planning and transparency practices.
''During PI Planning, teams commit to the objectives for the current PI and may provide a forecast for future PIs to aid in longer-term planning and alignment.''
(Source: SAFe 6.0 Framework: PI Planning; SPC 6.0 Guide, ''Coaching ART Execution'')
===========
Question 3
(Select 2) What steps in the Portfolio Kanban are most appropriate for running research spikes?
Answer : A, C
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 Kanban
SPC 6.0 Guide: ''Spikes are often run during the Funnel and Analysis steps to clarify scope, feasibility, and business case.''
===========
Question 4
The teams on the ART just finished the second Iteration in the PI and have nothing to demonstrate at the System Demo. What steps should be taken next?
Answer : B
SAFe recommends immediately integrating and testing the system when there is nothing to demonstrate, rather than continuing with new work. This helps surface integration issues early and allows for scope adjustment based on the learnings, supporting the principle of ''integrating frequently'' and ''demonstrating working software.''
SAFe 6.0, ''System Demo'' and ''PI Execution'' articles
SPC 6.0 Guide, ''Coaching ART Execution''
===========
Question 5
(Select 3) Which of the following have acceptance criteria?
Answer : A, D, F
A . Business Capabilities: In SAFe, Capabilities (including Business Capabilities) are large solution behaviors that have acceptance criteria to ensure they are fully defined and testable.
D . Enabler Features: All Features, including Enabler Features, require acceptance criteria to clarify when the Feature is done.
F . Program Epics: Epics require acceptance criteria to define the conditions for completion and evaluation.
Portfolio Enabler Epics (B) have a higher-level definition and are not typically assigned granular acceptance criteria. Strategic Themes (C) and Spikes (E) do not have acceptance criteria; Spikes are research items.
SAFe 6.0 Website: Features and Capabilities
SPC 6.0 Guide: ''Each Feature, Capability, and Epic should have clear acceptance criteria.''
===========
Question 6
The first SAFe Lean-Agile Principle includes 'Agile economics' and what else?
Answer : B
SAFe Lean-Agile Principle #1 is: ''Take an economic view.'' This principle incorporates both ''Agile economics'' and ''Apply systems thinking'' to optimize decision-making, value delivery, and overall outcomes by considering the entire system and focusing on economic impact.
WSJF is recommended for prioritizing the Team Backlog.
Answer : B
WSJF (Weighted Shortest Job First) is a prioritization method recommended by SAFe for use at the Program and Portfolio levels, especially for prioritizing Features and Epics. At the Team level, backlog items (Stories) are generally prioritized based on local context, dependencies, and feedback, not through WSJF.
''WSJF is the recommended approach for prioritizing the Program Backlog (Features). It is generally not used for the Team Backlog (Stories), which are usually prioritized in collaboration with the Product Owner based on iteration goals, dependencies, and value.''
(Source: SAFe 6.0 SPC Guide, 'Establishing Team and Technical Agility' module; Team Backlog section.)
All Official Question Types