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

Questions 26–30

1. 26foundation · easy

   In Azure DevOps, which feature is used to review code changes before they are merged into the main branch?

   • ACommit history
   • BPull request
   • CRelease pipeline
   • DBranch policy
   Reveal Solution Discussion Select an answer first
2. 27application · medium

   A developer needs to add a new class file to an existing Dynamics 365 Finance and Operations model in an Azure DevOps Git repository. The developer has the repository cloned locally. What is the correct way to add the new file to version control?

   • ACreate the file in the local workspace, use git add, commit, and push to the remote repository.
   • BUse the Dynamics 365 Finance and Operations IDE to create the file and check it in without committing.
   • CCreate the file directly in the Azure DevOps web portal and save it; it will be tracked automatically.
   • DCopy the file to the remote repository using a network share.
   Reveal Solution Discussion Select an answer first
4. 28foundation · easy

   What is a version conflict in Azure DevOps?

   • AWhen a commit is pushed
   • BWhen a file is deleted from the repository
   • CWhen a branch is created
   • DWhen two users modify the same line of code in different branches
   Reveal Solution Discussion Select an answer first
5. 29foundation · easy

   In Azure DevOps, which type of artifact is typically stored in the repository alongside source code?

   • ATest results
   • BDocumentation files
   • CBuild logs
   • DPipeline artifacts
   Reveal Solution Discussion Select an answer first
6. 30application · medium

   A developer needs to modify an existing X++ class in a Git repository in Azure Repos. The developer has cloned the repository locally. What is the correct sequence of actions to make the change and eventually get it into the main branch?

   • ACheck out the file in Azure DevOps using the 'Check Out' button, edit it online, and then check it back in.
   • BEdit the file directly on the main branch locally, commit, and push directly to main.
   • CUse the Azure DevOps web editor to edit the file on main and save, which automatically creates a pull request.
   • DCreate a feature branch, make the changes, commit locally, push the branch to Azure Repos, and create a pull request to main.
   Reveal Solution Discussion Select an answer first