SAFe-Agilist Establishing Team and Technical Agility Practice Question
An Agile Team is adopting SAFe and wants to ensure its work is integrated with other teams on the Agile Release Train. Which approach best supports continuous integration at the ART level?
⚠ Common exam trap
The trap here is assuming that periodic integration events or end-of-PI integration are sufficient, when SAFe requires daily integration into a shared mainline to achieve true continuous integration.
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
✓
Teams use a shared version control repository and integrate their code at least daily, with automated builds and tests.
The best approach is for teams to use a shared version control repository and integrate their code at least daily, supported by automated builds and tests. This practice enables early detection of integration issues, aligns with the ART's system-level Definition of Done, and ensures the solution is always in a potentially shippable state. It is a cornerstone of continuous integration and team and technical agility.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Teams use a shared version control repository and integrate their code at least daily, with automated builds and tests.
Why this is correct
Using a shared version control repository and integrating code at least daily with automated builds and tests is a foundational practice for continuous integration in SAFe. It enables early detection of integration issues, supports the ART's system-level Definition of Done, and ensures that the solution is always in a potentially shippable state. This approach directly supports team and technical agility.
- ✗
The Release Train Engineer coordinates a monthly integration event where all teams merge their code.
Why it's wrong here
Monthly integration events are too infrequent for continuous integration. SAFe promotes daily integration to catch issues early and maintain a working system. A monthly event would allow defects and integration problems to accumulate, making them harder to resolve. The Release Train Engineer should facilitate the adoption of continuous integration practices, not schedule periodic integration.
- ✗
Each team maintains its own separate code repository and integrates only at the end of the Program Increment.
Why it's wrong here
Separate code repositories and end-of-PI integration lead to integration hell and delayed feedback. SAFe emphasizes continuous integration across the ART to ensure that all teams' work integrates smoothly and frequently. Waiting until the end of the PI to integrate increases risk and makes it difficult to demonstrate a working system at the System Demo.
- ✗
Each team integrates its code with the main branch only when a feature is fully complete and tested.
Why it's wrong here
Integrating only when a feature is fully complete leads to long-lived branches and delayed integration, which contradicts continuous integration. SAFe recommends frequent integration, even for partially complete features, using techniques like feature toggles. This ensures that integration issues are discovered early and the codebase remains healthy, supporting the ART's ability to deliver value continuously.
About these practice questions
One of 315 original SAFe-Agilist practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.