A development team wants to protect the main branch from unauthorized changes. They want to ensure that only users with the 'Maintain' permission can push directly to main, while all other developers must use pull requests. They also want to prevent force pushes and branch deletion. What should they configure?

Use a pre-receive hook on the server to reject force pushes and deletions.

Enable branch protection on main that restricts direct pushes to users with Maintain permission, and disables force pushes and branch deletion.

Set the repository to read-only for all developers except the repository admin.

Create a new branch named 'protected-main' and ask developers to use it instead of main.

A team uses a feature branch strategy. They want to ensure that feature branches are kept up to date with the main branch to reduce merge conflicts. They also want to prevent feature branches from being merged if they are behind the main branch by more than a certain number of commits. What should they do?

Ask developers to manually merge main into their feature branches before creating a pull request.

Set the repository to automatically delete feature branches after they are merged.

Use a build validation that fails if the feature branch is more than 10 commits behind main.

Configure a branch policy on the main branch that requires the source branch to be up to date before merging.

A software company maintains a production version that is actively used by customers. They want to continue adding new features to the main branch while also being able to apply critical bug fixes to the production version without including unfinished features. Which branching strategy should they adopt?

Use a single long-lived branch for both development and production, tagging commits for releases.

Create a separate feature branch for each bug fix and merge directly to production without going through main.

Create a release branch from main for each production release. Apply only bug fixes to the release branch and merge them back to main.

Develop all new features directly on the main branch and deploy from main to production whenever a feature is complete.

A team uses a release branch for an upcoming version. They want to ensure that only bug fixes are merged into the release branch, and that all changes are reviewed by the release manager. They also want to prevent accidental merges from feature branches that are not yet approved. What should they implement?

Apply a branch policy on the release branch that requires a specific reviewer (release manager) and restricts merge sources to approved branches.

Ask all developers to manually verify that their changes are bug fixes before merging.

Delete the release branch after each bug fix and recreate it from main.

Use a naming convention for bug fix branches and rely on the CI pipeline to reject feature branches.

A 15-person development team is adopting trunk-based development. They want to keep the main branch always releasable and ensure every change is reviewed. They also want to avoid long-lived branches. Which workflow should they implement?

Use long-lived feature branches that are merged only at the end of each sprint.

Commit directly to main and rely on post-merge CI to catch issues.

Develop on short-lived feature branches and merge to main via pull requests with required reviewers and CI checks.

Create a release branch from main and do all development there.

Microsoft Certified:DevOps Engineer Expert

Domain 2Objective 1

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

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 6–10

6application · medium
A development team wants to protect the main branch from unauthorized changes. They want to ensure that only users with the 'Maintain' permission can push directly to main, while all other developers must use pull requests. They also want to prevent force pushes and branch deletion. What should they configure?
Select an answer first
7application · medium
A team uses a feature branch strategy. They want to ensure that feature branches are kept up to date with the main branch to reduce merge conflicts. They also want to prevent feature branches from being merged if they are behind the main branch by more than a certain number of commits. What should they do?
Select an answer first
8application · medium
A software company maintains a production version that is actively used by customers. They want to continue adding new features to the main branch while also being able to apply critical bug fixes to the production version without including unfinished features. Which branching strategy should they adopt?
Select an answer first
9application · medium
A team uses a release branch for an upcoming version. They want to ensure that only bug fixes are merged into the release branch, and that all changes are reviewed by the release manager. They also want to prevent accidental merges from feature branches that are not yet approved. What should they implement?
Select an answer first
10application · medium
A 15-person development team is adopting trunk-based development. They want to keep the main branch always releasable and ensure every change is reviewed. They also want to avoid long-lived branches. Which workflow should they implement?
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.

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

Questions 6–10

A 15-person development team is adopting trunk-based development. They want to keep the main branch always releasable and ensure every change is reviewed. They also want to avoid long-lived branches. Which workflow should they implement?

Keep studying — Design and implement a source control strategy