AZ-400 Configure processes and communications Practice Question

Answer analysis

Option-by-option breakdown

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

• ✗

  Create a custom tool using Azure Functions to parse commit messages and link work items. Use the built-in Charts feature in Azure Boards to create velocity charts.

  Why it's wrong here

  Building a custom Azure Functions-based parser to extract work item IDs from commit messages is redundant because Azure DevOps already provides native automatic linking of commits to work items. The custom tool introduces ongoing maintenance and failure points without enforcing that developers link work items at pull request time. In addition, the out-of-the-box Azure Boards Charts offer only fixed, preconfigured views; they lack the customizable trend analysis and filtering capabilities provided by Analytics views, so the velocity tracking requirement is only partially met.

• ✓

  Configure branch policies on the main branch to require linking work items. Set up the repository to automatically link commits to work items. Then create an Analytics view in Azure Boards to track velocity and work item trends.

  Why this is correct

  This is the correct approach because Azure DevOps branch policies on the main branch can enforce that every pull request links to at least one work item, ensuring traceability at merge time. Enabling the repository setting to automatically link commits to work items (under Project Settings > Repositories > your repo > Policies > Automatically link work items) further links commits made directly to branches, covering both commit and PR scenarios. Creating an Analytics view in Azure Boards (via the Analytics tab or Power BI) provides customizable, trend-capable data on velocity and work item flow, which is more robust than built-in charts for tracking trends over time.

• ✗

  Instruct developers to manually add work item IDs in commit messages and pull request descriptions. Create a custom dashboard using Power BI connected to Azure Boards.

  Why it's wrong here

  Relying on developers to manually type work item IDs in commit messages and PR descriptions is unenforceable and highly error-prone; a typo or omission breaks traceability without any automated guard. While Power BI can connect to Azure Boards via the Analytics OData endpoint, building and maintaining a custom dashboard is a significant extra step that duplicates functionality already available through Analytics views in the Boards UI. Because the requirement calls for a controlled, auditable linking process, branch policies that require work item links at merge time are the correct enforcement mechanism.

• ✗

  Enable the setting 'Automatically link work items' in the repository settings. Configure a service hook to post commit details to a Teams channel for visibility.

  Why it's wrong here

  This option is incomplete and does not satisfy the requirements. The 'Automatically link work items' repository setting only links commits to work items; it does not enforce linking at pull request time, so developers could bypass the link requirement. A service hook to Teams provides visibility but no dashboard or analytics for tracking velocity and work item trends, which is a key requirement. Branch policies and Analytics views are needed to enforce and visualize the data.