What is the primary purpose of a release branch in a branching strategy?

To track individual developer contributions for performance reviews.

To store the final production code permanently and prevent any further changes.

To provide a sandbox for developers to experiment with new technologies without affecting the main codebase.

To allow ongoing feature development to continue while a specific release is stabilized and prepared for deployment.

A team wants to enforce a pull request workflow where every change to the main branch requires at least two approvals and a successful build. They also want to prevent contributors from merging their own pull requests. Which combination of branch policies should they set on main?

Use a branch protection rule that only allows the repository admin to merge.

Require pull request reviews with a minimum of two reviewers, check for comment resolution, and require a successful build.

Require a successful build and allow the PR author to approve their own changes.

Require two reviewers but do not require a build.

In a feature branch strategy, what is the primary purpose of creating a feature branch?

To provide a permanent home for each developer's personal changes.

To track changes made by external contributors who do not have write access.

To store release artifacts and binaries for deployment.

To isolate new feature development from the main codebase until it is ready to integrate.

A team wants to ensure that every pull request to the main branch includes a linked work item and passes the required automated tests. They also want to prevent the pull request from being completed until the build succeeds. Which combination of settings should they use in the branch policy?

Enable the 'automatically include reviewers' setting and require a successful merge commit.

Require linked work items, require status checks to pass, and set the policy on the main branch.

Use a build validation policy that runs after the pull request is completed.

Require a minimum number of reviewers and set the policy on the feature branches.

Which action is typically restricted by branch protection rules?

Cloning the repository to a local machine.

Creating new branches from the protected branch.

Viewing the commit history of the branch.

Directly pushing commits to the protected branch.

Microsoft Certified:DevOps Engineer Expert

Domain 2Objective 1

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

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 26–30

26foundation · easy
What is the primary purpose of a release branch in a branching strategy?
Select an answer first
27application · medium
A team wants to enforce a pull request workflow where every change to the main branch requires at least two approvals and a successful build. They also want to prevent contributors from merging their own pull requests. Which combination of branch policies should they set on main?
Select an answer first
28foundation · easy
In a feature branch strategy, what is the primary purpose of creating a feature branch?
Select an answer first
29application · medium
A team wants to ensure that every pull request to the main branch includes a linked work item and passes the required automated tests. They also want to prevent the pull request from being completed until the build succeeds. Which combination of settings should they use in the branch policy?
Select an answer first
30foundation · easy
Which action is typically restricted by branch protection rules?
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.