SAFe Continuous Delivery Pipeline and DevOps 2

Question 1

What is a 'Definition of Done (DoD)' at the ART level in SAFe?

Accepted Answer

The criteria that must be met for a Feature or PI Increment to be considered complete and releasable

Answer

The completion criteria for individual user stories

Answer

The exit criteria for the PI Planning event

Answer

The quality gate for deploying to staging only

Question 2

What is 'Test-Driven Development (TDD)' in the context of SAFe Built-in Quality?

Accepted Answer

Writing automated tests before writing the code, using tests to drive the design and validate correctness

Answer

Having the QA team write all test cases

Answer

Testing in production to reduce pre-release testing overhead

Answer

Using AI tools to generate test cases automatically

Question 3

What is 'Behavior-Driven Development (BDD)' in SAFe?

Accepted Answer

A collaborative technique using Given-When-Then scenarios to define and verify behavior from the customer's perspective

Answer

A method for analyzing team member behavior

Answer

A performance management approach

Answer

A UI/UX design methodology

Question 4

What does the SAFe 'Test Automation Pyramid' recommend?

Accepted Answer

A large base of fast unit tests, fewer integration tests, and minimal UI/end-to-end tests — to maximize speed and reliability

Answer

More manual tests than automated tests

Answer

Equal distribution of test types

Answer

Prioritizing end-to-end tests as the most valuable

Question 5

What is 'Pair Work' in the context of SAFe Built-in Quality?

Accepted Answer

Two practitioners collaborating in real time on a single task to improve quality, share knowledge, and catch errors

Answer

Assigning two developers to the same task to double productivity

Answer

A code review process performed after completion

Answer

Pairing team members with external consultants

Question 6

What is a 'Non-Functional Requirement (NFR)' and how is it handled in SAFe?

Accepted Answer

A system quality attribute (e.g., performance, security, scalability) that constrains how the system must work

Answer

A feature request from a non-technical stakeholder

Answer

A requirement that was rejected from the backlog

Answer

A requirement that applies only to UI components