Design and implement processes and communications — AZ-400 Practice Quiz

Question 1

Your team runs automated tests in an Azure Pipelines build that publishes test results to Azure DevOps. Leadership wants a dashboard widget that shows the trend of automated test pass rate over the last 12 weeks so they can spot regressions in test quality across sprints. The data must reflect historical results, not just the latest run. Which dashboard widget should you configure to meet this requirement?

Accepted Answer

The Test Results Trend (Advanced) widget backed by the Analytics service, filtered by pipeline and grouped by outcome over the last 12 weeks

Answer

The Deployment Status widget scoped to the release pipeline

Answer

The Query Results widget bound to a work item query for Test Case work items

Answer

The Build History widget pinned to the CI pipeline definition

Question 2

Your team lead wants a dashboard that answers a single question: 'Once a developer starts actively working on a work item, how long does it take on average to reach the Done state?' The team uses Azure Boards with a Kanban board whose columns map to the states New, Active, Resolved, and Closed (mapped to Done). Management is NOT interested in how long items sat in the backlog before work began. Which Azure Boards analytics widget should you add to the dashboard to answer this question?

Accepted Answer

Cycle Time widget, configured to measure from the first Active state to the Closed/Done state

Answer

Lead Time widget, configured to measure from work item creation to the Closed/Done state

Answer

Cumulative Flow Diagram widget showing counts of items in each board column over time

Answer

Velocity widget showing completed story points per iteration

Question 3

Your team develops in a GitHub repository and tracks work in Azure Boards. Developers want commits and pull requests in GitHub to automatically link to Azure Boards work items so that the deployment/development section of each work item shows the related code changes. You have already installed the Azure Boards app for GitHub and connected the repository. What must developers do in their commit messages or PR descriptions to create these links?

Accepted Answer

Reference the work item using the syntax AB#123 in the commit message or PR title/description.

Answer

Reference the work item using the syntax #123, matching GitHub's native issue-linking syntax.

Answer

Add a GitHub label named azure-boards-123 to the pull request.

Answer

Include the full work item URL in a commit trailer prefixed with Fixes:.

Question 4

Your team uses GitHub for source control and Azure Boards for planning. Developers follow GitHub Flow, creating short-lived feature branches merged via pull requests. The product owner complains that when a work item is marked 'Done' in Azure Boards, there is no visibility into whether the code implementing that work item has actually reached production. You need to design a feedback cycle that surfaces the real deployment state of each work item back to the board with minimal custom development. Which approach best achieves this?

Accepted Answer

Configure the Azure Boards-GitHub integration to link commits and PRs, and use Azure Pipelines deployment jobs targeting environments so that Deployment records automatically appear on the linked work items' Development section.

Answer

Add a custom 'Deployed' state to the work item workflow and require developers to manually update it after each production release.

Answer

Create a dashboard cycle time widget filtered to the Done state so stakeholders can infer deployment timing from the average duration.

Answer

Enable branch policies requiring linked work items on every pull request so the board reflects merge status as the deployment indicator.

Question 5

Your team uses GitHub for source control and Azure Boards for work tracking. Leadership wants full end-to-end traceability so that anyone viewing a work item can see which pull requests implemented it and whether the associated build succeeded, without leaving Azure Boards. Developers already reference work items in commit messages using AB#123 syntax. What must you configure to satisfy this requirement with the least custom development?

Accepted Answer

Install the Azure Boards app from the GitHub Marketplace and connect the GitHub repository to the Azure Boards project so PRs, commits, and status appear in the Development section of work items.

Answer

Create a GitHub Actions workflow that calls the Azure DevOps REST API on each PR to append a comment to the linked work item with the build result.

Answer

Enable a service hook in Azure DevOps that posts to a GitHub webhook whenever a work item state changes so GitHub stores the traceability link.

Answer

Configure branch policies in Azure Repos requiring linked work items, then mirror the GitHub repository into Azure Repos on a schedule.

Question 6

Your organization stores code in GitHub and manages sprint planning in Azure Boards. Developers work in GitHub using GitHub Flow, opening feature branches and pull requests. Product managers want work item state in Azure Boards to automatically move to 'Closed' when the linked pull request is merged, without developers manually updating boards. You have installed the Azure Boards app on the GitHub organization. Which configuration achieves automatic state transition on PR merge?

Accepted Answer

Add an 'AB#<id>' mention in the PR description or a commit message using a state-transition keyword (e.g., 'Fixes AB#123'), which the Azure Boards GitHub integration uses to close the linked work item on merge to the default branch.

Answer

Configure a branch policy in Azure Repos requiring linked work items, which will automatically close the item when the GitHub PR merges.

Answer

Enable the 'Automatically close work items' toggle in Azure Boards Project Settings > GitHub connections, then link the PR with AB# and closure happens regardless of keyword.

Answer

Create a GitHub Actions workflow triggered on 'pull_request closed' that calls the Azure DevOps REST API with a service connection to update every referenced work item state.

Question 7

Your engineering organization uses Azure Boards for backlog management and Slack for team communication. The delivery lead wants engineers to receive a Slack message in the #team-releases channel whenever a work item in the 'Delivery' area path transitions to the 'Resolved' state, but they do NOT want notifications for any other state change or area path. The solution must require minimal ongoing maintenance and avoid custom code hosting. Which approach should you implement?

Accepted Answer

Configure the Azure Boards app for Slack and create a subscription with a filter on area path and the 'work item updated' event scoped to the Resolved state.

Answer

Create an outgoing service hook in Azure DevOps that posts to a Slack incoming webhook on every 'work item updated' event, then filter messages inside Slack with a workflow rule.

Answer

Deploy an Azure Function triggered by an Azure Boards service hook that inspects each event payload and forwards only matching events to Slack.

Answer

Enable the built-in Azure DevOps email notification for the Delivery team and configure Slack to ingest the notification mailbox.

Question 8

Your engineering leadership wants a dashboard metric that measures the total elapsed time from the moment a customer feature request is created as a work item until it is marked Done, so they can quantify overall responsiveness to customer demand. The team already tracks how long items spend actively being worked. Which Azure Boards analytics metric should you add to the dashboard to satisfy leadership's request?

Accepted Answer

Lead Time, measured from work item creation to closure

Answer

Cycle Time, measured from when work becomes active to closure

Answer

Mean Time to Recovery (MTTR) for the deployment environment

Answer

Velocity, measured as completed story points per sprint

Question 9

Your operations team wants a dashboard that reports Mean Time To Detect (MTTD) alongside MTTR for production incidents. Incidents are tracked as Azure Boards work items of type 'Incident', which capture the timestamp an outage actually began (a custom field 'Impact Start') and the timestamp the incident work item was created. MTTR is already calculated from resolved date minus created date. Which approach correctly produces MTTD for the dashboard?

Accepted Answer

Build an Analytics view and Power BI measure that averages the difference between the incident's Created Date and its 'Impact Start' custom field, then pin it as a dashboard tile.

Answer

Use the built-in Azure Boards Cycle Time widget, which automatically reports MTTD for Incident work item types.

Answer

Configure a Lead Time widget filtered to the Incident work item type, since Lead Time equals detection time.

Answer

Add a Velocity chart to the dashboard and interpret the story points completed per sprint as the detection latency.

Question 10

Your team wants a dashboard widget that visualizes how many User Stories were completed each week over the last three months, grouped by the assigned team member, so the delivery manager can spot workload imbalances. You have an existing flat-list query returning all completed User Stories with their Closed Date and Assigned To fields. What is the most appropriate way to configure this visualization in Azure Boards?

Accepted Answer

Keep the flat-list query and add a Chart for Work Items widget configured as a stacked bar chart grouped by Assigned To with a date-based x-axis

Answer

Convert the query to a tree query and add a Cumulative Flow Diagram widget pointing to it

Answer

Add a Velocity widget scoped to the team and set the number of sprints to display

Answer

Add a Burndown widget bound to a shared query filtered by Closed Date

Question 11

Your team runs sprints in Azure Boards and deploys via Azure Pipelines. Product management wants an automatically generated release notes document published to the team wiki after each successful production deployment. The notes must list all completed User Stories and Bugs associated with the commits included in that release, without requiring anyone to manually curate the list. Which approach best satisfies this requirement with the least ongoing maintenance?

Accepted Answer

Add a pipeline step that uses the built-in release notes generation to collect associated work items from the build's linked commits and publish the output as a Markdown page to the wiki via the Azure DevOps REST API.

Answer

Create a shared query in Azure Boards filtered by iteration path and manually copy its results into the wiki after each deployment.

Answer

Configure a Teams channel webhook so that every work item state change posts a message, then archive the channel history as the release notes.

Answer

Enable a dashboard widget showing the sprint burndown and export it as a PDF attached to each release.

Question 12

Your team collaborates primarily in Microsoft Teams. Product owners want a dedicated Teams channel to automatically receive a notification whenever any work item in the 'Payments' area path on the Azure Boards project transitions to the 'Resolved' state, so testers can begin verification promptly. You must configure this with the least administrative effort and without writing custom code. What should you do?

Accepted Answer

Install the Azure Boards app in the Teams channel and create a subscription filtered by area path and the 'Resolved' state transition.

Answer

Create an Azure DevOps service hook that posts to an Incoming Webhook connector in the Teams channel for every work item updated event.

Answer

Configure a personal notification subscription in Azure Boards for each product owner filtered to the 'Payments' area path.

Answer

Build an Azure Logic App triggered by the Azure Boards connector that filters work items and posts an adaptive card to the channel.

Question 13

Your team wants to build a Power BI report that shows how the number of active bugs has changed week-over-week across the past 12 months, including work items that have since been closed or deleted from the backlog. The report must refresh automatically and must not be limited by the default work item query row caps. Which Azure DevOps data source should you connect Power BI to in order to satisfy these requirements with the least custom development?

Accepted Answer

An Analytics view configured with a rolling 12-month history and the required fields, connected via the Power BI Data Connector

Answer

A shared flat-list work item query saved in Azure Boards, exported to Excel and imported into Power BI

Answer

The Azure Boards REST API for Work Items, called from a custom Power BI M query on each refresh

Answer

The Cumulative Flow Diagram widget exported as an image and embedded into the Power BI report

Question 14

Your team uses Azure DevOps for source control and work tracking, but an external system running Jenkins must automatically start a build whenever code is pushed to the main branch of a specific Azure Repos Git repository. Security requires that the integration send only the relevant event data to a single HTTP endpoint, without granting Jenkins broad API access or requiring polling. What should you configure in Azure DevOps?

Accepted Answer

Create a Service Hooks subscription for the 'Code pushed' event, filtered to the repository and main branch, with a Web Hooks action pointing to the Jenkins endpoint URL.

Answer

Add a Jenkins service connection under Project Settings and reference it from a build validation branch policy on main.

Answer

Grant Jenkins a full-scope Personal Access Token and configure Jenkins to poll the Azure DevOps REST API for new commits on main.

Answer

Configure an Azure Pipelines YAML CI trigger with a path filter and a 'Publish to Jenkins' task at the end of the pipeline.

Question 15

Your team uses Azure Boards with a Kanban board configured with columns: New, Active, Code Review, Testing, and Done. Delivery has slowed and stakeholders want data-driven evidence of where work is stalling. You add a Cumulative Flow Diagram (CFD) widget to the team dashboard. When interpreting the CFD to identify a process bottleneck, which visual characteristic should you look for?

Accepted Answer

A band (column) whose vertical thickness continuously widens over time, indicating work accumulating in that state faster than it exits

Answer

A steep upward slope of the topmost band, indicating the team is completing items rapidly

Answer

A band that becomes progressively thinner over time, indicating too many items are stuck in that column

Answer

The horizontal distance between the New band's start and the Done band's start, which directly represents mean time to recovery (MTTR)

Question 16

Your Scrum team uses Azure Boards with two-week sprints. During sprint planning, the product owner wants a data-driven way to decide how many story points to commit to the upcoming sprint, based on the team's demonstrated throughput over the last several completed sprints. Which Azure Boards analytics widget should you add to the team dashboard to best support this forecasting decision?

Accepted Answer

Velocity widget configured to show completed story points across the last 6 iterations

Answer

Cumulative Flow Diagram widget scoped to the current iteration

Answer

Cycle Time widget filtered to the User Story work item type

Answer

Burndown widget for the active sprint backlog

Question 17

Your team tracks feature work in a GitHub Projects (Projects v2) board that pulls in issues and pull requests from three repositories. The team wants the board's 'Status' field to automatically move an item to 'Done' when its linked pull request is merged, and to 'In Progress' when a draft PR is marked ready for review — without any manual field edits and without maintaining custom code. What should you configure?

Accepted Answer

Enable the project's built-in workflows (automations) for 'Item closed' and 'Pull request merged' to set the Status field values

Answer

Create a GitHub Actions workflow in each repository that calls the GraphQL API to update the project item's Status field on PR events

Answer

Add branch protection rules requiring linked issues, which automatically synchronize the project Status field on merge

Answer

Configure a repository webhook that posts to an Azure Function to patch the project item field via REST

Question 18

Your team uses GitHub for source control and Microsoft Teams for collaboration. Whenever a release is published in a GitHub repository, the operations channel in Teams must receive an automated message containing the release tag and notes. You want the integration to react in real time to the specific GitHub event without polling and without granting Teams broad access to the repository. What should you configure?

Accepted Answer

Create a GitHub webhook on the repository scoped to the 'release' event that posts to a Teams incoming webhook (workflow) URL.

Answer

Add a scheduled GitHub Actions workflow that queries the Releases API every 5 minutes and posts new releases to Teams.

Answer

Install the Azure Boards app in the Teams channel and link the GitHub repository through Boards integration.

Answer

Configure a Teams outgoing webhook that subscribes to the GitHub repository's release feed.

Question 19

Your operations team wants a dashboard in Azure DevOps that surfaces Mean Time To Recovery (MTTR) for production incidents. Incidents are tracked as work items of type 'Incident' with a custom 'Detected On' date field and the standard 'Closed Date' field. Leadership wants to see the average duration between detection and resolution over the last 90 days, refreshed automatically. Which approach best delivers this metric on an Azure DevOps dashboard?

Accepted Answer

Build an Analytics view filtered to Incident work items closed in the last 90 days, then create a Power BI report calculating the average of (Closed Date − Detected On) and pin it to the dashboard, or use an Azure DevOps chart widget over that Analytics view.

Answer

Add the built-in 'Cycle Time' widget, which by definition measures the time between incident detection and closure for any work item type.

Answer

Create a flat-list work item query that returns all closed Incidents and add the 'Query Results' widget, since it automatically computes average date differences.

Answer

Use the 'Lead Time' widget scoped to the Incident work item type, because Lead Time is the standard measure of recovery duration after an outage is detected.

Question 20

Your team maintains an Azure DevOps project wiki that documents system architecture. Architects complain that the current architecture diagrams are static PNG images that quickly become outdated because updating them requires a separate diagramming tool, and the images are not reviewed alongside code changes. You want the diagrams to be authored as text, rendered natively in the wiki, and go through pull request review as part of the repository. Which approach should you implement?

Accepted Answer

Publish a code wiki (provisioned as a Git repository) and author the diagrams using Mermaid syntax inside Markdown files

Answer

Continue using the project wiki and attach exported PNG files, but store the source diagram files in Azure Repos

Answer

Embed the diagrams as inline HTML canvas elements in the project wiki pages

Answer

Link the wiki pages to an external Visio Online document stored in SharePoint

More AZ-400 practice