SAFe-Agilist Establishing Team and Technical Agility Practice Question
An Agile Team is struggling with frequent integration issues because team members work on long-lived feature branches and merge infrequently. The team wants to improve its continuous integration practice. What is the most effective action to take?
⚠ Common exam trap
The trap here is thinking that increasing merge frequency or adding manual oversight solves integration problems, when the real solution is to eliminate long-lived branches through trunk-based development and automated validation.
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
✓
Adopt trunk-based development where team members commit to a shared mainline at least daily and use automated tests to validate each integration.
The most effective action is to adopt trunk-based development with daily commits to a shared mainline and automated tests. This practice minimizes integration risk, provides rapid feedback, and keeps the codebase in a potentially shippable state. It directly addresses the root cause of long-lived branches and aligns with SAFe's emphasis on continuous integration as a foundation for 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.
- ✓
Adopt trunk-based development where team members commit to a shared mainline at least daily and use automated tests to validate each integration.
Why this is correct
Trunk-based development with daily commits to a shared mainline and automated testing is a core practice for continuous integration in SAFe. It minimizes integration risk, provides fast feedback, and ensures the codebase is always in a potentially shippable state. This directly addresses the root cause of long-lived branches and fosters team and technical agility.
- ✗
Implement a code freeze two days before the end of the Iteration to allow time for integration.
Why it's wrong here
Code freezes are a sign of poor continuous integration practices and reduce flow. They delay feedback and do not prevent integration issues; they merely postpone them. SAFe promotes continuous integration and delivery, where code is integrated and tested continuously, not frozen. This approach would undermine the team's ability to deliver value incrementally.
- ✗
Increase the frequency of merging by requiring team members to merge their branches at least once per week.
Why it's wrong here
Merging weekly still allows significant divergence and integration problems to accumulate. Continuous integration in SAFe implies integrating code changes at least daily, if not more frequently. Weekly merges do not address the root cause of long-lived branches and may still result in complex merge conflicts and delayed feedback, failing to establish true technical agility.
- ✗
Assign a dedicated integration manager to manually merge all branches at the end of each Iteration.
Why it's wrong here
A dedicated integration manager creates a bottleneck and does not solve the underlying issue of delayed integration. Manual merging at the end of an Iteration leads to large, risky merges and late feedback. This approach contradicts SAFe's principle of built-in quality and continuous integration, where the team collectively owns integration and automates it.
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.