AZ-400 Question 55
Select 2Your organization stores code in GitHub but uses Azure Boards for work item tracking. You want to automatically link pull requests and commits to their respective Azure Boards work items whenever a commit message references an Azure Boards work item ID. Which two steps must you perform to successfully configure this integration?
- A
Install the Azure Boards app for GitHub in the target GitHub repository or organization.
- B
Use the AB#
syntax in your commit messages or pull requests. - C
Enable ephemeral personal access tokens for the repository� GitHub webhook.
- D
Create a new branch that includes the work item ID in its name to automatically link commits.
- E
Require an approval policy from Azure DevOps before merging any pull request in GitHub.
Show answer and explanation
Correct answers: A, B
Explanation
To configure Azure Boards and GitHub integration, you must install the Azure Boards app in the relevant GitHub repository (or organization) and use the AB#
- A. Correct.
Correct: Installing the Azure Boards app for GitHub is essential since it allows GitHub to communicate with Azure Boards. Once installed, references to work item IDs can be automatically tracked in Azure Boards.
- B. Correct.
Correct: The AB#
notation in commits, pull requests, or issue links is the required syntax for Azure Boards to recognize and link the related work items. - C. Incorrect.
Incorrect: Enabling ephemeral personal access tokens is neither a standard nor a required step for configuring Azure Boards with GitHub. The integration is handled by the Azure Boards GitHub app rather than a webhook that requires ephemeral tokens.
- D. Incorrect.
Incorrect: Merely naming the branch after the work item ID does not create links between commits and work items. The AB#
syntax is required in commit messages or PR descriptions for automatic linkage. - E. Incorrect.
Incorrect: While organizations may implement approval policies for pull requests, it's not required for the Azure Boards�GitHub integration to function. The integration focuses on linking work items and code changes, not enforcing approvals.