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

Updated On: 10-Mar-2026

Your team uses an agile development approach.

You need to recommend a branching strategy for the team's Git repository. The strategy must meet the following requirements.

Provide the ability to work on multiple independent tasks in parallel.

Ensure that checked-in code remains in a releasable state always.

Ensure that new features can be abandoned at any time.

Encourage experimentation.

What should you recommend?

  1. a single long-running branch without forking
  2. multiple long-running branches
  3. a single fork per team member
  4. a single long-running branch with multiple short-lived feature branches

Answer(s): D

Explanation:

Topic/feature branches, however, are useful in projects of any size. A topic branch is a short-lived branch that you create and use for a single particular feature or related work. This is something you've likely never done with a VCS before because it's generally too expensive to create and merge branches. But in Git it's common to create, work on, merge, and delete branches several times a day.


Reference:

https://git-scm.com/book/en/v2/Git-Branching-Branching-Workflows



You manage a project by using Azure Boards, and you manage the project code by using GitHub repositories.

You have a work item that has an ID of 123.

You need to link a commit message in GitHub to work item 123 on the board.

What are two ways to achieve the goal? Each correct answer presents a complete solution.

Note: Each correct selection is worth one point.

  1. From the Development settings of work item 123, select Add link, and then enter the URL of the commit.
  2. Add AB#123 to the text of the commit message.
  3. Add GH-123 to the text of the commit message.
  4. From the Links settings of work item 123, select Add link, select Existing item, and then enter the URL of the commit.
  5. To work item 123, add a comment that includes the URL of the commit.

Answer(s): A,B

Explanation:

Correct:
* Add AB#123 to the text of the commit message.
* To the description of the pull request, add #AB123.
or
* In the Development section for work item 123, select Add link, and then enter the URL of the pull request.
* From the Development settings of work item 123, select Add link, and then enter the URL of the commit.
Incorrect:
* Add GH-123 to the text of the commit message.
* From the Links settings of work item 123, select Add link, select Existing item, and then enter the URL of the commit.
* From work item 123, open the Links tab, select Add link, select Existing item, and then enter the URL of the commit.
* To work item 123, add a comment that includes the URL of the commit.
* To work item 123 add a comment that includes the URL of the pull request.
Note:
Link GitHub commits, pull requests, and issues to work items in Azure Boards Once you connect your Azure Boards project with a GitHub repository, you can link work items to your GitHub commits and pull requests. You can add links using the #mention syntax familiar to GitHub users or you can add a GitHub commit or GitHub pull request link type from the Azure Boards work item.
* Add AB#123 to the text of the commit message.
* To the description of the pull request, add #AB123.
Method 1: Use AB# to link from GitHub to Azure Boards work items From a GitHub commit, pull request or issue, use the following syntax to create a link to your Azure Boards work item. Enter the AB#ID within the text of a commit message. Or, for a pull request or issue, enter the AB#ID within the title or description (not a comment).
AB#{ID}
For example, AB#125 links to work item ID 125.
* In the Development section for work item 123, select Add link, and then enter the URL of the pull request.
* From the Development settings of work item 123, select Add link, and then enter the URL of the commit.

Method 2: Add link from a work item to a GitHub commit, pull request, or issue Add link from a work item to a GitHub commit, pull request, or issue
1. To link to a commit or pull request, open the work item and choose Add link under the Development section.



To link to an issue, choose the Links tab, and then choose Add Link>Existing item.



2. From the Add link dialog, select one of the GitHub link types, enter the URL to the commit, pull request, or issue and then choose OK.
Here, we add a link to a GitHub pull request.



* From work item 123, open the Links tab, select Add link, select Existing item, and then enter the URL of the commit.


Reference:

https://learn.microsoft.com/en-us/azure/devops/boards/github/link-to-from-github



You have a project in Azure DevOps that uses an Azure Boards board and stores code in a GitHub repository.
The repository contains a file named README.md.

You need to ensure that README.md includes the status of the work items on the board. The solution must minimize administrative effort.

What should you do first?

  1. Create a GitHub personal access token (PAT).
  2. Enable GitHub annotations for the board.
  3. Install the Azure Boards app for GitHub.
  4. Select Allow anonymous users to access the status badge.

Answer(s): C

Explanation:

Azure DevOps, Azure Boards, Link GitHub commits, pull requests, and issues to work items in Azure Boards Once you connect your Azure Boards project with a GitHub repository, you can link work items to your GitHub commits and pull requests. You can add links using the #mention syntax familiar to GitHub users or you can add a GitHub commit or GitHub pull request link type from the Azure Boards work item.
Prerequisites
* You must be a Contributor to Azure Boards project and to the GitHub repository.
*-> Your Azure Boards project must be connected to the GitHub repository where the commits and pull requests you want to link to/from exist.
Integrate Azure Boards and GitHub
Azure Boards and Azure DevOps support integration with GitHub.com and GitHub Enterprise Server repositories.
--> Important
We recommend that you use the Azure Boards app for GitHub to configure and manage your connections to GitHub.com. The app provides a more streamlined configuration experience and has the advantage of authenticating and operating as the app rather than an individual. Once you're connected, you can manage the repositories either from Azure Boards or GitHub.com.


Reference:

https://learn.microsoft.com/en-us/azure/devops/boards/github/ https://learn.microsoft.com/en-us/azure/devops/boards/github/link-to-from-github



You manage a project by using Azure Boards, and you manage the project code by using Azure Repos.

You have a bug work item that has an ID of 123.

You need to set the work item state to Resolved.

What should you add to the commit message?

  1. #123 fixed
  2. #123 Resolved-
  3. Verifies #123-
  4. Resolves #123-

Answer(s): A

Explanation:

Correct:
* #123 fixed
* Fixes #123
Incorrect:
* #123 completes
* #123 Resolved
* Completed #123
* Resolves #AB-123
* Verifies #123
Note: Resolve work items on commit
Close work items by mentioning keywords in commit messages.
When you mention a work item in a commit that makes it to the default branch via one of the supported workflows, we will attempt to resolve that work item.
Keywords
The three supported keywords to trigger a resolution mention are fix, fixes, and fixed (case insensitive).
Optionally, a colon can follow the keyword. Most forms of punctuation can precede or proceed the resolution mention, excluding another pound sign (#).
Examples
Fixes #123
This fixed #123!
Change behavior to fix: #123
Fixes #123 and fixes #124


Reference:

https://learn.microsoft.com/en-us/azure/devops/repos/git/resolution-mentions



SIMULATION

You need to create a new team dashboard named Dashboard1 for the default project team of Project1.

The dashboard must display the members of the team.

  1. See Explanation section for answer.

Answer(s): A

Explanation:

Add dashboards in Azure DevOps
Add a dashboard
Add a new dashboard as needed to support your team's needs. You can also edit and rename any existing dashboards associated with your team.

Step 1: From the Dashboards directory, select New Dashboard. Or, when viewing a dashboard, open the selector and select the New Dashboard option.



Step 2: Enter the name of the dashboard and other information you want to capture. [Enter Dashboard1]

Step 2a: Select Team dashboard.

Step 2b: Select: Automatically refresh the dashboard every 5 minutes.



Step 3: Select Create.


Reference:

https://learn.microsoft.com/en-us/azure/devops/report/dashboards/dashboards



Viewing page 36 of 72
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!