SAFe-Agilist Establishing Team and Technical Agility Practice Question
An Agile Team consistently meets its Iteration Goals, but the features it delivers frequently fail in the staging environment because unit tests pass while end-to-end behavior is broken. The team's Definition of Done currently stops at code review and unit tests. What is the most effective next step to improve Built-in Quality?
⚠ Common exam trap
The trap here is assuming that because unit tests pass and Iteration Goals are met, quality is adequate, when the real gap is that the Definition of Done omits end-to-end verification.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Extend the Definition of Done to require automated acceptance tests that verify end-to-end behavior in the pipeline before a story is considered complete.
The gap is that the Definition of Done stops short of verifying end-to-end behavior, so defects escape to staging. Adding automated acceptance tests that run in the pipeline extends the Definition of Done to cover real user flows and gives fast, repeatable feedback. Manual passes, design reviews, and scope reduction do not create the automated verification the team needs.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Add a manual regression test pass by a separate quality assurance specialist before each feature is declared done.
Why it's wrong here
Adding a manual regression pass by a separate specialist reintroduces a handoff and delays feedback, which lengthens the time between defect creation and detection. It also moves quality ownership away from the developers. While manual exploratory testing has value, making it the primary gate does not build the automated verification the team needs to catch end-to-end breakage early.
- ✗
Reduce the scope of each Iteration so the team has more time to test manually before the end of the Iteration.
Why it's wrong here
Reducing scope to allow more manual testing treats the symptom and sacrifices delivered value without building a durable capability. Manual testing does not scale and still leaves end-to-end behavior unverified between releases. The team already meets its Iteration Goals, so the issue is not capacity but the absence of automated end-to-end verification in the Definition of Done.
- ✓
Extend the Definition of Done to require automated acceptance tests that verify end-to-end behavior in the pipeline before a story is considered complete.
Why this is correct
Extending the Definition of Done to include automated acceptance tests that exercise end-to-end behavior closes the gap between passing unit tests and working features. Because the tests run in the pipeline, the team gets fast, repeatable feedback and defects are caught before staging. This directly strengthens Built-in Quality and makes the team's definition of done reflect what customers actually need.
- ✗
Ask the System Architect to review each feature design before development begins so defects are prevented upstream.
Why it's wrong here
Design review may reduce some defects, but the observed failures are integration and end-to-end behavior issues that a design review cannot reliably catch. It also creates a dependency on an external approver and slows the team's flow. The gap is in verification coverage within the Definition of Done, not in design intent, so upstream review does not address the root cause.
About these practice questions
Courseiva writes every SAFe-Agilist question from scratch — 315 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Scaled Agile exam blueprint
This SAFe-Agilist practice question is part of Courseiva's free Scaled Agile certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAFe-Agilist exam.