SAFe® 5 DevOps Certification Agile Testing and Quality 1 — Questions and Answers
Question 1: What does 'shift-left testing' mean in the context of SAFe DevOps?
- Moving testing activities earlier in the development process (Correct answer)
- Shifting test responsibilities entirely from developers to QA specialists
- Moving production monitoring dashboards to the left panel
- Delaying testing until after every deployment
Correct answer: Moving testing activities earlier in the development process
Shift-left testing means performing testing activities as early as possible in the development lifecycle to catch defects sooner when they are cheapest to fix.
Question 2: In SAFe DevOps, which practice most directly implements shift-left testing?
- Post-deployment manual exploratory testing
- Writing tests before or alongside code development using TDD or BDD (Correct answer)
- Quarterly security penetration audits
- Annual architecture and code review sessions
Correct answer: Writing tests before or alongside code development using TDD or BDD
TDD and BDD are the primary practices implementing shift-left testing by integrating automated test creation as early as possible in development.
Question 3: What is the primary business benefit of shift-left testing in a SAFe DevOps environment?
- It eliminates the business need for a dedicated QA team
- It reduces the cost of fixing defects by finding them much earlier in development (Correct answer)
- It directly speeds up every deployment to production
- It replaces all automated testing with manual testing
Correct answer: It reduces the cost of fixing defects by finding them much earlier in development
Defects found earlier in development are significantly cheaper to fix than those found in production, making shift-left testing highly cost-effective.
Question 4: Which SAFe built-in quality practice best aligns with shift-left testing by making quality everyone's responsibility from the start?
- Test-last development phases at end of sprint
- 'Build quality in' — embedding quality practices throughout all development activities (Correct answer)
- Dedicated end-of-sprint testing phases
- Quarterly code quality audits by external reviewers
Correct answer: 'Build quality in' — embedding quality practices throughout all development activities
SAFe's 'build quality in' principle means every team member is responsible for quality throughout development, not just QA at the end.
Question 5: In SAFe DevOps, who holds responsibility for shift-left testing activities?
- Only dedicated QA engineers assigned to the team
- Only the developers who wrote the code being tested
- The entire Agile team, with developers writing automated tests as part of development (Correct answer)
- External audit and compliance teams only
Correct answer: The entire Agile team, with developers writing automated tests as part of development
Shift-left testing is a whole-team responsibility in SAFe — developers, testers, and product owners all contribute to quality from the beginning of work.
Question 6: What does the 'test pyramid' model recommend about the distribution of test types in a SAFe DevOps pipeline?
- Most tests should be slow, comprehensive manual UI tests at the top layer
- A large base of fast unit tests, fewer integration tests, and minimal end-to-end tests (Correct answer)
- An equal distribution of unit, integration, and UI tests across all layers
- Only integration tests are needed in a mature continuous delivery pipeline
Correct answer: A large base of fast unit tests, fewer integration tests, and minimal end-to-end tests
The test pyramid recommends many fast, cheap unit tests at the base, fewer integration tests in the middle, and minimal slow end-to-end tests at the top.
SAFe® 5 DevOps Certification Agile Testing and Quality 1
What does 'shift-left testing' mean in the context of SAFe DevOps?