Scaled Agile SAFe Practice Consultant SPC (6.0) SAFe-SPC Exam Questions

Page: 1 / 14
Total 179 questions
Question 1

Who is part of the development Value Stream?



Answer : B

A development Value Stream is defined as ''the people and processes that develop solutions used by customers, whether internal or external.'' In SAFe, it's everyone who is involved in building, evolving, and delivering Solutions---this includes business and technical roles, not just engineering.


SAFe 6.0, ''Value Streams'' article

SPC 6.0 Guide, ''Building Solutions with Agile Product Delivery''

===========

Question 2

What is the primary purpose of the management meeting at the end of Day 1 of PI Planning?



Answer : B

At the end of Day 1 of PI Planning, managers and key stakeholders meet to review program risks, PI Objectives, and dependency issues raised by teams. The primary purpose is to make adjustments to scope, resolve challenges, and provide guidance for Day 2 planning.


SAFe 6.0 Website: PI Planning

SPC 6.0 Guide: ''Management meets to review progress, address challenges, and adjust scope as needed.''

===========

Question 3

Which basic Agile quality practice ensures consistent quality measures for each work product?



Answer : A

The ''Definition of Done'' and established quality standards are basic Agile practices that ensure every work product meets agreed-upon quality criteria before it is considered complete. This approach drives consistency, transparency, and reliable outcomes across teams and ARTs.


SAFe 6.0, ''Built-In Quality'' article

SPC 6.0 Practice Guide, ''Establishing Team and Technical Agility''

===========

Question 4

(Select 2) What are the right scenarios for using SAFe Foundations Training Materials?



Answer : B, D

SAFe Foundations Training Materials are designed for broad awareness and initial education, especially for:

B: Making an initial presentation on SAFe to the organization.

D: Familiarizing executives and leaders with the basics of SAFe.

Detailed role-based and process training (A, C, E) is better addressed through role-specific courses (e.g., ''SAFe for Teams,'' ''SAFe Scrum Master,'' ''SAFe Release Train Engineer'').


SAFe 6.0 Website: SAFe Foundations

SPC 6.0 Guide: ''Foundations materials are ideal for executive briefings and initial organizational awareness.''

===========

Question 5

What is NOT a SAFe-recommended practice for DevOps?



Answer : F

SAFe recommends feature branching only when necessary and encourages frequent integration to avoid the overhead and risk associated with long-lived branches. ''Continuously synchronize all Feature and team branches'' implies maintaining multiple long-lived branches, which is contrary to SAFe's DevOps and continuous integration best practices.

''Minimize branching and integrate frequently. Long-lived branches and excessive synchronization are discouraged as they increase complexity and risk.''

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

===========


Question 6

Test automation is typically included in the Definition of Done (DoD).



Answer : A

Test automation is a best practice in SAFe and is typically included in the Definition of Done (DoD). The DoD ensures that all work is tested and validated before being considered complete. Including test automation in the DoD supports continuous integration, reduces manual testing effort, and increases the reliability of every increment.


SAFe 6.0 Website: Built-in Quality

SPC 6.0 Guide: ''Definition of Done includes automated testing to ensure built-in quality.''

Question 7

(Select 2) What are the ways to evolve the Solution Intent from variable to fixed scope?



Answer : B, D

Solution Intent captures the ''single source of truth'' regarding the current and intended behavior of the solution. As solutions evolve, so does the Solution Intent---from variable (unknown, undecided) to fixed (known, decided). Ways to evolve the Solution Intent include:

Modeling: Documenting aspects of the solution using models helps clarify and fix certain elements.

Building prototypes: Prototypes allow for validation and learning, which in turn help evolve the intent from exploratory (variable) to more defined (fixed).

Creating work breakdown structures is not a recommended SAFe practice for evolving Solution Intent. Adapting WIP limits pertains to flow, not directly to Solution Intent.


SAFe 6.0 Framework: Solution Intent

SAFe 6.0 SPC Guide: ''Building Solutions with Agile Product Delivery'' module

Page:    1 / 14   
Total 179 questions