
Can You Manage Merge Conflicts in Azure DevOps Services?
Part of Azure DevOps Topic: Azure
Access
StationX Infrastructure Labs — 3 attempts per lab
🔒 Add StationX Infrastructure Labs — $149 / year · 3 attempts per lab
Already have access? Sign in.
New to this? Try a free practice lab — a scripted hacking challenge in your browser, no account needed.
What you'll do
In this lab, you will add large file support to an Azure DevOps Git repository and manage conflicts between users.
- Create a new Azure DevOps Git repository and clone it to your development machine
- Initialize the project
- Set up a feature branch structure for branches for your Git repo in Azure DevOps
- Install git-lfs on the dev environments for your primary user
- Check in and commit a ZIP file for the project from the primary account
- Add a secondary user to your project, set up their large file support, and commit a new version of the ZIP file to the repo
- Attempt to check in a new version of the file as the primary user, resulting in a merge conflict
- Resolve the merge conflict
- Create a merge request to the master branch as the primary user and approve it as the secondary user
Note: Once you begin the lab, you will not be able to pause, save, or return to your lab. Please ensure that you have set aside enough time to complete the lab before you start.
- ⏱ About 45 minutes
- Counts towards: Designing and Implementing Microsoft DevOps Solutions (exam AZ-400) · CompTIA Cloud+ (exam CV0-004)
Roadmaps that use this lab
- CompTIA Cloud+ (CV0-004) — step 4: DevOps fundamentals

