SIMULATION Initialize the default main branch, if it does not exist already. For Project1, you need to implement branch merging restrictions to enable squash merge for all changes merged into the main

Submitted by mike_84· Mar 6, 2026Configure repositories and branch policies in Azure DevOps to implement source control best practices and enforce merge strategy restrictions (AZ-400: Design and Implement Source Control)

Question

SIMULATION Initialize the default main branch, if it does not exist already. For Project1, you need to implement branch merging restrictions to enable squash merge for all changes merged into the main branch. Answer:

Exhibit

Explanation

The correct answer requires navigating to Repos > Branches in Azure DevOps, locating the main branch for Project1, and accessing Branch Policies to configure Merge Strategies. By enabling only 'Squash merge' in the Merge Strategies section, all pull requests merging into main will be required to use squash commits, compressing the source branch history into a single commit on the target branch. This is the proper Azure DevOps workflow because branch policies are the designated mechanism for enforcing merge strategy restrictions at the repository level.

Topics

#Azure DevOps Branch Policies#Merge Strategies#Repository Management#Azure Repos

Community Discussion

No community discussion yet for this question.

Full AZ-400 Practice