AZ-400 Practice Question: Design and implement a source control strategy
Which THREE are common Git branching strategies used by development teams? (Select THREE.)
⚠ Common exam trap
Test-takers frequently confuse repository management strategies (like monorepo) or version control system types (like centralized VCS) with actual Git branching strategies, leading candidates to select options that describe storage or system architecture rather than branch workflows.
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
✓
GitFlow
GitFlow is a common branching strategy that uses a main branch (master/main) alongside develop, feature, release, and hotfix branches. It provides a structured model for managing releases, hotfixes, and parallel development, making it suitable for projects with scheduled release cycles.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
GitFlow
Why this is correct
GitFlow is a branching model that maintains a long-lived develop branch alongside main, with feature branches for new work, release branches for staging, and hotfix branches for urgent fixes, providing strict release management and clear role separation.
- ✓
Trunk-based development
Why this is correct
Trunk-based development is a strategy where developers integrate small, short-lived branches into a single shared trunk (main) multiple times per day, often using feature toggles to keep the main branch always in a releasable state, reducing merge complexity.
- ✓
Feature branching
Why this is correct
Feature branching is a technique that isolates each new feature in its own branch, enabling parallel development and pull request review, but branches can become long-lived and require disciplined integration to avoid merge conflicts and stale code.
- ✗
Monorepo
Why it's wrong here
A monorepo is a single repository that houses multiple projects or services, which is a source-control organizational pattern rather than a branching strategy; it can be used in conjunction with any branching model like GitFlow or trunk-based development.
- ✗
Centralized version control
Why it's wrong here
Centralized version control is a VCS model (e.g., TFVC) that relies on a central server and file locking, contrasting with Git's distributed branching and merging capabilities; therefore it is not a Git branching strategy and does not answer the question.
Go deeper
Related to this question
Learn chapter
Source Control Strategy Design
Key term
Git
Git is a version control system that tracks changes to files so multiple people can work on the same project without overwriting each other's work.
Key term
Branch
A branch is a pointer to a specific commit in a version control system that allows you to work on features or fixes in isolation from the main codebase.
About these practice questions
Courseiva writes every AZ-400 question from scratch — 823 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 by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.