What is a primary benefit of trunk-based development?

It allows multiple release versions to be maintained simultaneously without any coordination.

It reduces merge conflicts and supports continuous integration by keeping branches short-lived.

It eliminates the need for automated testing because changes are small and frequent.

It ensures that no code is merged until it has been reviewed by at least two developers.

A team wants to enforce a pull request workflow where all changes to the main branch require a successful build and at least one approval from a code owner. However, they also want to allow urgent hotfixes to be merged with only a build check, bypassing the code owner approval, but only for a designated group of 'Hotfix Responders'. What is the best way to configure this?

Use a single branch policy on main that requires code owner approval but allows the Hotfix Responders to override it manually.

Use branch policies that require build validation and code owner review, and configure a separate branch policy for a 'hotfix' branch that has relaxed review requirements for the Hotfix Responders group.

Remove the code owner review requirement from the main branch policy and rely on the build check only.

Create a separate repository for hotfixes and merge them into main via a pull request with relaxed policies.

A startup with a small team wants to adopt trunk-based development. They want to keep the main branch always deployable and ensure that all changes are integrated quickly. They also want to enforce code review without slowing down the integration process. What is the most appropriate approach?

Allow all developers to push directly to main without any review or build checks.

Create a release branch for every developer and merge to main only during release time.

Use long-lived feature branches that are merged to main only after all features are complete.

Use short-lived feature branches that are merged to main via pull requests with a lightweight review policy and automated build checks.

What is the purpose of branch policies in Azure Repos?

To limit the number of commits a developer can make in a single day.

To enforce requirements such as code reviews and successful builds before changes are merged into a branch.

To rename branches based on naming conventions.

To automatically create a new branch for every developer in the organization.

Which practice is typical in a feature branch workflow?

Using a single long-lived branch that all developers push to without any isolation.

Creating a branch from the main branch for each new feature and merging it back after completion.

Committing directly to the main branch for all changes, regardless of feature scope.

Creating a branch for each environment (dev, test, prod) and promoting code through them.

Microsoft Certified:DevOps Engineer Expert

Domain 2Objective 1

Design and Implement Branching Strategies for the Source Code AZ-400 Practice Questions (Page 5)

Part of the Design and implement a source control strategy domain, which makes up ~10% of our current practice bank. Microsoft does not publish an official question count, but from its 140-minute exam (~55–95 total, ~6–10 in this domain), expect 3–5 from this objective — we provide 31 practice questions to prepare you well beyond it. (estimate)

31questions here

7free pages

7concepts

Questions 21–25

21foundation · easy
What is a primary benefit of trunk-based development?
Select an answer first
22expert · hard
A team wants to enforce a pull request workflow where all changes to the main branch require a successful build and at least one approval from a code owner. However, they also want to allow urgent hotfixes to be merged with only a build check, bypassing the code owner approval, but only for a designated group of 'Hotfix Responders'. What is the best way to configure this?
Select an answer first
23application · medium
A startup with a small team wants to adopt trunk-based development. They want to keep the main branch always deployable and ensure that all changes are integrated quickly. They also want to enforce code review without slowing down the integration process. What is the most appropriate approach?
Select an answer first
24foundation · easy
What is the purpose of branch policies in Azure Repos?
Select an answer first
25foundation · easy
Which practice is typical in a feature branch workflow?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to AZ-400

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Microsoft. “AZ-400” is a trademark of its owner, used for identification only.