Microsoft DevOps Engineer Expert AZ-400 Practice Question
Your organization has 20 developers working on a single Azure Repos Git repository for an internal microservice. The microservice is deployed to production multiple times per day via a fully automated pipeline. Management reports that long-lived feature branches being merged at the end of each sprint often cause complex merge conflicts and delay releases. You need to redesign the branching strategy to reduce integration pain while still allowing developers to experiment in isolation for a few hours. Which branching approach should you recommend?
Require each developer to work in a personal fork and submit periodic patches directly to the main branch without pull-request validation.
Adopt trunk-based development by requiring every change to merge into the main branch within 24 hours through short-lived feature branches and mandatory pull requests.
Switch to a GitFlow model with permanent develop and release branches, merging feature branches only after user acceptance testing.
Continue using feature branches but extend branch lifetimes to the full release cycle and freeze the main branch except for hotfixes.
Trunk-based development encourages very short-lived branches that are merged back into the main (trunk) branch at least daily, which keeps the integration surface small and prevents the accumulation of merge debt. Pull-request policies can still be applied so that developers can work in isolation for a few hours, submit a PR, and integrate quickly. Extending the lifetime of feature branches or adding permanent develop and release branches does the opposite-it increases divergence and makes later merges riskier. Requiring personal forks without PR validation makes integration even less frequent and would undermine continuous delivery.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is trunk-based development?
Open an interactive chat with Bash
Why do long-lived branches result in merge conflicts?
Open an interactive chat with Bash
How does trunk-based development improve continuous delivery?
Open an interactive chat with Bash
What is trunk-based development?
Open an interactive chat with Bash
Why are long-lived feature branches problematic?
Open an interactive chat with Bash
How do pull requests work with trunk-based development?
Open an interactive chat with Bash
Microsoft DevOps Engineer Expert AZ-400
Design and implement a source control strategy
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
Pass with Confidence.
IT & Cybersecurity Package
You have hit the limits of our free tier, become a Premium Member today for unlimited access.
Military, Healthcare worker, Gov. employee or Teacher? See if you qualify for a Community Discount.
Monthly
$19.99
$19.99/mo
Billed monthly, Cancel any time.
3 Month Pass
$44.99
$14.99/mo
One time purchase of $44.99, Does not auto-renew.
MOST POPULAR
Annual Pass
$119.99
$9.99/mo
One time purchase of $119.99, Does not auto-renew.
BEST DEAL
Lifetime Pass
$189.99
One time purchase, Good for life.
What You Get
All IT & Cybersecurity Package plans include the following perks and exams .