Configure processes and communications →mediumMultiple ChoiceObjective-mapped

AZ-400 Configure processes and communications Practice Question

Your team uses Azure Boards and wants to automate work item state transitions when code is merged. What should you use?

⚠ Common exam trap

Test-takers frequently confuse the 'Update work item' task in Azure Pipelines (Option A) as a direct merge-triggered automation, but it requires a pipeline run, whereas the GitHub integration provides a simpler, event-driven solution without additional pipeline overhead.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

GitHub + Azure Boards integration with automatic work item linking

GitHub + Azure Boards integration, when configured with automatic work item linking, automatically transitions work items (e.g., from 'Active' to 'Resolved') when a pull request is merged. This is achieved through the integration's ability to detect commit messages or PR descriptions containing 'AB#{ID}' or 'Fixes AB#{ID}' patterns, which trigger state changes defined in the Azure Boards project configuration.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Azure Pipelines with 'Update work item' task
Why it's wrong here
The 'Update work item' task in Azure Pipelines allows you to modify work item fields during a pipeline run, but it requires a pipeline to be explicitly triggered (e.g., by a pull request or CI) and does not inherently link work items to a merge. It is an extra, explicit step rather than the automatic linking that happens when a commit references a work item.
✗
Branch policy in Azure Repos
Why it's wrong here
Branch policies in Azure Repos enforce requirements such as minimum reviewer counts, successful builds, or linked work items before a pull request can complete. However, they do not update or transition work items themselves; they only gate whether a merge is allowed, so they cannot automate the work item status change on merge.
✓
GitHub + Azure Boards integration with automatic work item linking
Why this is correct
The GitHub + Azure Boards integration automatically links GitHub commits and pull requests to Azure Boards work items when the commit or PR title includes the work item ID (e.g., 'AB#123'). When configured, it can also transition the linked work item to a 'Done' or 'Closed' state upon the merge of the PR, providing the desired automation directly from the merge event without additional pipeline tasks or services.
✗
Power Automate with Azure DevOps connector
Why it's wrong here
Power Automate with the Azure DevOps connector can create flows that respond to webhooks or triggers and call the REST API to update work items, but this requires setting up and maintaining a separate automation service. It is not the native, built-in integration that Azure Boards offers with GitHub, making it a heavier and more indirect solution for the stated need.

Visual reference

Go deeper

AZ-400 Configure processes and communications Practice Question

Why each option matters

Option-by-option breakdown

Related to this question