SAFe® 5 DevOps Certification Agile Testing and Quality

Question 1

What does 'shift-left testing' mean in the context of SAFe DevOps?

Accepted Answer

Moving testing activities earlier in the development process

Answer

Shifting test responsibilities entirely from developers to QA specialists

Answer

Moving production monitoring dashboards to the left panel

Answer

Delaying testing until after every deployment

Question 2

In SAFe DevOps, which practice most directly implements shift-left testing?

Accepted Answer

Writing tests before or alongside code development using TDD or BDD

Answer

Post-deployment manual exploratory testing

Answer

Quarterly security penetration audits

Answer

Annual architecture and code review sessions

Question 3

What is the primary business benefit of shift-left testing in a SAFe DevOps environment?

Accepted Answer

It reduces the cost of fixing defects by finding them much earlier in development

Answer

It eliminates the business need for a dedicated QA team

Answer

It directly speeds up every deployment to production

Answer

It replaces all automated testing with manual testing

Question 4

Which SAFe built-in quality practice best aligns with shift-left testing by making quality everyone's responsibility from the start?

Accepted Answer

'Build quality in' — embedding quality practices throughout all development activities

Answer

Test-last development phases at end of sprint

Answer

Dedicated end-of-sprint testing phases

Answer

Quarterly code quality audits by external reviewers

Question 5

In SAFe DevOps, who holds responsibility for shift-left testing activities?

Accepted Answer

The entire Agile team, with developers writing automated tests as part of development

Answer

Only dedicated QA engineers assigned to the team

Answer

Only the developers who wrote the code being tested

Answer

External audit and compliance teams only

Question 6

What does the 'test pyramid' model recommend about the distribution of test types in a SAFe DevOps pipeline?

Accepted Answer

A large base of fast unit tests, fewer integration tests, and minimal end-to-end tests

Answer

Most tests should be slow, comprehensive manual UI tests at the top layer

Answer

An equal distribution of unit, integration, and UI tests across all layers

Answer

Only integration tests are needed in a mature continuous delivery pipeline