Manage Source Code and Artifacts by Using Microsoft Azure DevOps Version Control MB-500 Practice Questions (Page 5)

Questions 21–25

1. 21application · medium

   A team uses Azure Repos with a 'main' branch protected by a branch policy that requires a pull request and a successful build. They want to ensure that every change merged into main is automatically built and deployed to a sandbox environment. What should they configure in Azure Pipelines?

   • AA build pipeline with a continuous integration trigger on the main branch, and a release pipeline that deploys the build artifact to the sandbox.
   • BA build pipeline triggered on pull request creation only, with a deployment job that runs after the build.
   • CA scheduled build that runs nightly and deploys to the sandbox if the build succeeds.
   • DA manual build pipeline that developers trigger after merging, with a separate manual deployment step.
   Reveal Solution Discussion Select an answer first
2. 22expert · hard

   A team uses Azure DevOps Git with a main branch and a release branch. A developer accidentally merged a feature branch into the release branch instead of the main branch. The feature branch contained changes that are not ready for release. The team needs to remove the feature changes from the release branch while preserving the release branch history. Which approach should you recommend?

   • AUse git reset --hard to remove the merge commit from the release branch.
   • BUse git cherry-pick to apply the reverse of the merge commit.
   • CUse git revert on the merge commit to undo the changes while preserving history.
   • DDelete the release branch and re-create it from main.
   Reveal Solution Discussion Select an answer first
4. 23application · easy

   A developer needs to update a documentation file that is stored in an Azure DevOps Git repository. The developer has cloned the repository locally and made the changes. What is the correct sequence of steps to make the changes available to other team members?

   • APush the changes directly to the remote main branch without committing.
   • BCommit the changes locally, push to the remote branch, and create a pull request if required.
   • CEmail the file to the team and ask them to update their local copies.
   • DCopy the file to a shared network drive for other team members to access.
   Reveal Solution Discussion Select an answer first
5. 24expert · hard

   A developer is merging a feature branch into main in Azure Repos. The merge reports a conflict in a model element file. The developer needs to understand exactly what changed on each side before deciding how to resolve the conflict. The developer also wants to ensure the resolution is reviewed by a peer before it is committed to main. What should the developer do first?

   • AUse the Azure DevOps 'Compare branches' feature to view the differences between the feature branch and main, then resolve the conflict in the merge editor.
   • BAbort the merge, delete the feature branch, and recreate it from main to avoid the conflict.
   • CAutomatically accept the version from main because main is the more stable branch.
   • DCommit the conflicted file as-is and then create a work item to fix it later.
   Reveal Solution Discussion Select an answer first
6. 25foundation · easy

   Which Azure DevOps feature is used to store and manage build artifacts, such as compiled binaries?

   • AAzure Artifacts
   • BAzure Test Plans
   • CAzure Repos
   • DAzure Boards
   Reveal Solution Discussion Select an answer first