Question 479 of 823
AZ-400 Practice Question: Design and implement a source control strategy
Your team uses Git with a trunk-based development strategy. They want to ensure that all code changes are integrated into the main branch at least once a day, and that branch lifetimes are short. Which practice best supports this?
⚠ Common exam trap
Many exam-takers confuse GitFlow (option A) with trunk-based development, but GitFlow's long-lived develop and feature branches directly contradict the requirement for daily integration into main and short branch lifetimes.
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
✓
Developers work on short-lived feature branches (less than a day) and merge to main via pull requests after successful CI.
Trunk-based development emphasizes short-lived feature branches (typically less than a day) that are merged into the main branch via pull requests after passing continuous integration (CI) checks. This ensures all code changes are integrated at least daily, keeping branch lifetimes short and reducing merge conflicts.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Developers use GitFlow with develop and feature branches, merging to develop daily and to main at release.
Why it's wrong here
GitFlow is a release-centric branching model that relies on long-lived develop and feature branches; even merging daily to develop and only syncing main at release creates delayed integration and diverges from trunk-based development's principle of a single, always-releasable main branch.
- ✗
Developers commit directly to a release branch, and then the release branch is merged to main at the end of the sprint.
Why it's wrong here
This describes a release branch strategy where integration occurs at sprint boundaries rather than continuously; the long-lived release branch defers merging to main and prevents the short feedback loop and frequent integration that are essential to trunk-based development.
- ✗
Developers work on long-lived feature branches and merge to main only after all features are complete.
Why it's wrong here
Long-lived feature branches postpone integration until the end, causing large, conflict-prone merges and delayed feedback; this batch approach undermines trunk-based development, which demands small, incremental changes merged to main continuously to keep the codebase in a deployable state.
- ✓
Developers work on short-lived feature branches (less than a day) and merge to main via pull requests after successful CI.
Why this is correct
Trunk-based development relies on short-lived feature branches that are typically less than a day old, with developers merging to main via pull requests only after successful continuous integration; this keeps main in a releasable state and enables rapid, small-batch integration.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 25, 2026
This AZ-400 practice question is part of Courseiva's free Microsoft 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 AZ-400 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.