Case Study 2 - Contoso, Ltd Background Contoso, Ltd. is a manufacturing company that has a main office in Chicago. Contoso plans to improve its IT development and operations processes by implementing

This hotspot question tests knowledge of Azure DevOps branching strategies and fork policies for enabling isolated team development while maintaining build policy enforcement on Project2.

Submitted by priya_blr· Mar 6, 2026Design and implement source control

Question

Case Study 2 - Contoso, Ltd Background Contoso, Ltd. is a manufacturing company that has a main office in Chicago. Contoso plans to improve its IT development and operations processes by implementing Azure DevOps principles. Contoso has an Azure subscription and creates an Azure DevOps organization. The Azure DevOps organization includes: The Docker extension A deployment pool named Pool7 that contains 10 Azure virtual machines that run Windows Server 2016 The Azure subscription contains an Azure Automation account. Contoso plans to create projects in Azure DevOps as shown in the following table. Technical requirements Contoso identifies the following technical requirements: Implement build agents for Project1. Whenever possible, use Azure resources. Avoid using deprecated technologies. Implement a code flow strategy for Project2 that will: - Enable Team2 to submit pull requests for Project2. - Enable Team2 to work independently on changes to a copy of Project2. - Ensure that any intermediary changes performed by Team2 on a copy of Project2 will be subject to the same restrictions as the ones defined in the build policy of Project2. Whenever possible implement automation and minimize administrative effort. Implement Project3, Project5, Project6, and Project7 based on the planned changes Implement Project4 and configure the project to push Docker images to Azure Container Registry. Hotspot Question How should you configure the filters for the Project5 trigger? To answer, select the appropriate option in the answer area. NOTE: Each correct selection is worth one point. Answer:

Exhibits

Answer Area

Set a ... /folder1.
branch filter to excludebranch filter to includepath filter to excludepath filter to include
Set a ... /.
branch filter to excludebranch filter to includepath filter to excludepath filter to include

Explanation

This hotspot question tests knowledge of Azure DevOps branching strategies and fork policies for enabling isolated team development while maintaining build policy enforcement on Project2.

Approach. The correct code flow strategy for Project2 involves using a Fork-based workflow. Team2 should fork the Project2 repository, which creates an independent copy they can work on freely. When Team2 submits pull requests back to the main Project2 repository, those PRs are subject to the same branch policies (build policies) defined on the target branch. This satisfies all three requirements: Team2 can submit pull requests, work independently on their fork, and any intermediary changes on the fork that are submitted via PR will be validated against Project2's build policies. A fork is preferred over a branch in this scenario because the team needs to work independently on a copy - forks provide repository-level isolation while still enforcing policies at the PR merge point.

Concept tested. Azure DevOps Fork-based branching strategy - understanding when to use forks versus branches, and how fork pull requests inherit and are subject to the build/branch policies of the upstream (target) repository.

Reference. https://learn.microsoft.com/en-us/azure/devops/repos/git/forks?view=azure-devops

Topics

#Azure DevOps#pipeline triggers#branch filters#path filters

Community Discussion

No community discussion yet for this question.

Full AZ-400 Practice