AZ-400 - Design and Implement Processes and Communications (13% of the exam) - Section 1.1

Design and implement traceability and flow of work, including GitHub Flow, work tracking integration, and source, bug, and quality traceability.

Describe GitHub Flow and how work items in Azure Boards and GitHub Issues link commits, pull requests, and releases into an end-to-end traceability chain. Distinguish the integration points that connect source changes to bug and quality tracking so reviewers can follow work from requirement to deployed code.

GitHub FlowAzure BoardsGitHub Issueswork item integrationend-to-end traceability

Practice question for this objective

Free sampleDesign and Implement Processes and Communicationsmedium

An organisation keeps its repositories on "GitHub" but plans and tracks work in "Azure Boards". They want GitHub commits and pull requests to link to Azure Boards work items so the board shows development progress against each story. What is the recommended way to establish this cross-product linking?

AMirror each GitHub repository into Azure Repos with a scheduled import so the existing Azure Repos work item linking parses the imported commits and updates the board.
BAdd a personal access token as a pipeline secret and run a scheduled script that reads the GitHub commit feed and posts updates onto matching Azure Boards work items.
CInstall the "Azure Boards" app for GitHub, connect the repositories to the project, and reference work items in commits and pull requests using the "AB#" mention syntax. Correct
DEnable GitHub Advanced Security on the repositories so its code scanning results are forwarded to Azure Boards and attached to the related stories as development links.

Use the Azure Boards app for GitHub with the AB-hash mention syntax to link GitHub commits and pull requests to work items. The Azure Boards app for GitHub establishes a connection between named GitHub repositories and an Azure Boards project. Once connected, an "AB#" mention in a commit message, pull request, or issue is recognised and a development link is written to the referenced work item, so the board reflects GitHub activity without migrating the source.

Why A is wrong: Mirroring duplicates the source of truth and adds sync overhead, and the team wants to keep developing on GitHub rather than migrate the repositories into Azure Repos.

Why B is wrong: A bespoke script with a long-lived token is fragile and adds operational burden when a supported integration already performs the linking natively.

Why C is correct: The Azure Boards app connects GitHub repositories to a board, and the AB-hash mention in commits and pull requests creates the supported development link on each work item.

Why D is wrong: GitHub Advanced Security scans code for vulnerabilities and secrets and does not create work item links, so it solves a different problem than cross-product traceability.

See more AZ-400 practice questions, answers explained.

Exam traps in Design and Implement Processes and Communications

Answers that look right on this material and are not. Each one is a distractor from a different question in the AZ-400 bank for this domain.

Add the work item title as a tag on the pull request so the boards service can match the wording and attach the commit to the matching story automatically.
Why it is wrong: Matching on free-text titles is unreliable and is not how the boards link is formed, so a tag would not create the development link on the work item.
The Discussion section, which lists every comment posted on the item and embeds any hyperlinks reviewers have pasted to the related branches and builds.
Why it is wrong: The Discussion section holds free-text comments and pasted links rather than tracked development artefacts, so it does not present the linked branches, pull requests and builds as a governed view.
A branch policy on the default branch that requires a linked work item, which advances that item to Resolved automatically each time a qualifying pull request merges.
Why it is wrong: GitHub branch protection can require a linked item but never transitions work item state, so it cannot move the item to Resolved on merge as the requirement asks.

Examworthy is not affiliated with or endorsed by Microsoft. Original, blueprint-aligned practice material only.