Free AZ-400 Exam Braindumps
Designing and Implementing Microsoft DevOps Solutions Questions 1–45 (page: 36)

Updated On: 16-Nov-2026

You have the repositories shown in the following table.

You need to migrate the contents of the GitHub repository to the Azure Repos repository. The solution must ensure that the Azure Repos repository only contains branches and history from the GitHub repository.
Which three commands should you run in sequence? To answer, move the appropriate commands from the list of commands to the answer area and arrange them in the correct order.
Select and Place:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




git clone --bare creates a bare clone of the GitHub repository, including its branches and history. After navigating to the cloned repository, git push --mirror mirrors the Git references to Azure Repos, replacing destination references so that Azure Repos matches the GitHub repository.


Reference:

https://learn.microsoft.com/en-us/azure/devops/repos/git/import-git-repository?tabs=visual-studio&view=azure-devops



You have a GitHub repository.
You need to ensure that all changes to code are validated by your company’s security department before the main branch is deployed.
Which two actions can you perform? Each correct answer presents a complete solution.
Note: Each correct selection is worth one point.

  1. Require signed commits.
  2. Create a branch protection rule for the feature branches.
  3. Create a LICENSE file.
  4. Create a branch protection rule for the main branch.
  5. Create a CODEOWNERS file.

Answer(s): D,E

Explanation:

* Create a CODEOWNERS file.
About code owners
You can use a CODEOWNERS file to define individuals or teams that are responsible for code in a repository.
Code owners are automatically requested for review when someone opens a pull request that modifies code that they own.
* Create a branch protection rule for the main branch
About protected branches
You can protect important branches by setting branch protection rules, which define whether collaborators can delete or force push to the branch and set requirements for any pushes to the branch, such as passing status checks or a linear commit history.


Reference:

https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-rep ository/about-code-owners https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protect ed-branches/about-protected-branches



You have a GitHub repository that contains multiple versions of an Azure Pipelines template.
You plan to deploy multiple pipelines that will use a template stored in the repository.
You need to ensure that you use a fixed version of the template.
What should you use to reference which version of the template repository to use?

  1. the serial
  2. the SHA-based hashes
  3. the runner
  4. the branch

Answer(s): D

Explanation:

Repositories are resolved only once, when the pipeline starts up. After that, the same resource is used for the duration of the pipeline. Only the template files are used. Once the templates are fully expanded, the final pipeline runs as if it were defined entirely in the source repo. This means that you can't use scripts from the template repo in your pipeline.
If you want to use a particular, fixed version of the template, be sure to pin to a ref. The refs are either branches (refs/heads/<name>) or tags (refs/tags/<name>). If you want to pin a specific commit, first create a tag pointing to that commit, then pin to that tag.
Note: If no ref is specified, the pipeline will default to using refs/heads/main.


Reference:

https://github.com/MicrosoftDocs/azure-devops-docs/blob/main/docs/pipelines/process/templates.md



You have an app named App1 that you release by using Azure Pipelines. App1 has the versions shown in the following table.

You complete a code change for version 3 to fix a bug that was introduced in version 3.4.3.
Which version number should you assign to the release?

  1. 3.4.4
  2. 3.4.8
  3. 3.5.0
  4. 4.0.1

Answer(s): D

Explanation:

Semantic Versioning 2.0.0
Summary
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes
MINOR version when you add functionality in a backward compatible manner
PATCH version when you make backward compatible bug fixes
Note: Semantic Versioning Specification (SemVer)
2. A normal version number MUST take the form X.Y.Z where X, Y, and Z are non-negative integers, and MUST NOT contain leading zeroes. X is the major version, Y is the minor version, and Z is the patch version. Each element MUST increase numerically. For instance: 1.9.0 -> 1.10.0 -> 1.11.0.
6. Patch version Z (x.y.Z | x > 0) MUST be incremented if only backward compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.


Reference:

https://semver.org/



View Related Case Study

DRAG DROP (Drag and Drop is not supported)
You need to replace the existing DevOps tools to support the planned changes.
What should you use? To answer, drag the appropriate tools to the correct targets. Each tool may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
Note: Each correct selection is worth one point.
Select and Place:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Azure Boards
Azure Boards can be used to track work with Kanban boards, backlogs, team dashboards, and custom reporting
You can create multiple Trello boards, which are spaces to store tasks (for different work contexts, or even private boards)
You can easily share Trello boards with another person.
Box 2: Azure Pipelines
You can use Bamboo to implement CI/CD (Continuous Integration and Continuous Delivery) for a simple Azure function app using Atlassian Bamboo. Bamboo does continuous delivery of the project from source code to deployment. It has stages including Build, Test and Deploy.
Software teams in every industry are upgrading their continuous delivery pipeline with Bamboo. Easy build import from popular open source tools, user and group import from JIRA, seamless integration with Bitbucket, and native support for Git, Hg, and SVN means you'll be building and deploying like a champ.
Box 3: GitHub repositories
Bitbucket can be used as the Git repository, but you can use any other Git repository (Like TFS Git) for source control of the code.


Reference:

https://www.trustradius.com/compare-products/azure-devops-services-vs-trello https://marketplace.visualstudio.com/items?itemName=ms-vsts.vss-services-bamboo https://www.c-sharpcorner.com/article/cicd-implementation-for-an-azure-function-app-using-atlassian-bamboo-server/



Viewing page 36 of 81
Viewing questions 176 - 180 out of 398 questions


Post your Comments and Discuss Microsoft AZ-400 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!