AZ-400 domain - 13% of the exam

Design and Implement Processes and Communications

Design and Implement Processes and Communications is 13% of the AZ-400 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

37
Practice questions
3
Objectives
37
Medium

Where people go wrong

  • Picking a DORA measure of the wrong shape

    The wrong answers pick a DORA measure of the wrong shape. Cycle time runs from a developer's first commit to production, while lead time starts earlier, when the request is created in the backlog, so it includes queue and triage delay. Deployment frequency is a throughput count of production deployments per window, not an elapsed duration. Time to restore service times recovery from an incident, while change failure rate is the share of deployments that cause a production failure.

    See it in a sample question
  • Writing a plain hash where Azure Boards needs AB#

    The wrong answers use a bare hash reference, a Fixes trailer with a bare number, a git note or a web hook and expect Azure Boards to link a GitHub commit. A plain hash such as #1453 points at a GitHub issue, and the Azure Boards app does not scan git notes or bare-number trailers. The Azure Boards app for GitHub reads the AB# mention in commits and pull requests.

    See it in a sample question
  • Picking a dashboard widget that answers a different question

    Burndown, velocity, lead time and capacity widgets get offered for questions they do not answer. Burndown shows remaining work inside one sprint, and velocity shows completed story points per sprint for forecasting. Neither shows where items accumulate. The cumulative flow diagram stacks daily counts per state, so a widening band marks the bottleneck. The cycle time widget charts how long completed items spent in active development.

    See it in a sample question
  • Treating a point-in-time query as trend reporting

    A WIQL query or export, the work items batch REST endpoint and an exported board filter all return current field values or a static snapshot with no history. The REST route also needs a custom script, and an exported file cannot refresh. Trend and aggregation reports come from the Analytics service through its OData endpoint. For Power BI, an Analytics view gives a curated dataset that the Data Connector refreshes on a schedule, with no OData expressions written by hand.

    See it in a sample question
  • Building custom glue where a first-party app exists

    The wrong answers post raw event JSON to a channel email, call Microsoft Graph from a pipeline task, wire an incoming webhook, or script a custom GitHub Actions step, when a first-party app already does the job. In Microsoft Teams, the Azure Pipelines app subscribes a channel to failed runs, the Azure Repos app to pull request events and the Azure Boards app to work item assignment. In GitHub, the Azure Boards app moves a work item to Done from Fixes AB# on merge.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleDesign and Implement Processes and Communicationsmedium

Leadership asks for a single DORA metric that answers how often the team delivers value to users, reported as a throughput count over a window rather than as any elapsed duration, so they can compare release cadence against an industry benchmark. Which metric should the team report?

  • ALead time, calculated from when a change is requested until it reaches production, which reports the elapsed duration a single change takes to travel through the delivery pipeline.
  • BChange failure rate, calculated as the share of deployments that cause a production failure needing remediation, which reports how risky the team's releases are to ship.
  • CCycle time, calculated from a developer's first commit until the change reaches production, which reports how long active development and delivery take for a single item.
  • DDeployment frequency, calculated as the number of successful production deployments completed in a window, which reports how often the team releases value as a throughput count. Correct
Recognise deployment frequency as the DORA flow metric reporting release cadence as a throughput count, distinct from elapsed-time measures. DORA expresses delivery throughput as deployment frequency, a count of successful production deployments per window, and delivery speed as lead time, an elapsed duration. Because leadership asked for a cadence count rather than a duration, deployment frequency is the metric, and the elapsed-time measures cycle time and lead time do not fit.

Why A is wrong: Lead time is a DORA flow metric but expresses an elapsed duration per change, not a throughput count of how often the team ships, so it answers the wrong shape of question.

Why B is wrong: Change failure rate is a DORA stability metric about release quality, not a count of how often the team deploys, so it does not express delivery cadence.

Why C is wrong: Cycle time is an elapsed-duration measure for one item's active development, so it cannot serve as the throughput count of releases per window leadership wants.

Why D is correct: Deployment frequency is the DORA flow metric expressed as a count of production deployments per window, which is exactly the cadence throughput figure leadership asked to benchmark.

Free sampleDesign and Implement Processes and Communicationsmedium

A repository is hosted on "GitHub" while the team plans work in "Azure Boards" with the Azure Boards app for GitHub installed. The team wants both automatic linking of code to work items and automatic state transitions driven from GitHub. Which TWO things must contributors include in their GitHub commits or pull requests to achieve linking and an automatic Done transition? Select TWO.

  • AAn "AB#" mention such as "AB#1453" in a commit message or pull request description to link that commit or pull request to the work item. Correct
  • BA state transition keyword alongside the mention, such as "Fixes AB#1453", so merging the pull request moves the work item to its Done state. Correct
  • CA "#1453" GitHub issue reference, which the app maps to the matching Azure Boards work item identifier and transitions it.
  • DA repository web hook posting to the Azure Boards REST API on merge, which the app requires contributors to add per pull request.
Use the AB number mention for linking and a transition keyword to drive an automatic work item state change from GitHub. With the Azure Boards app for GitHub installed, an AB number mention in a commit or pull request creates the work item link, and a supported transition keyword such as Fixes in front of that mention moves the linked work item to Done when the pull request merges; GitHub issue hash references and manual web hooks are not the mechanism.

Why A is correct: The Azure Boards app for GitHub recognises the AB number syntax in commits and pull request text and creates the development link to the referenced work item automatically.

Why B is correct: Supported transition keywords like Fixes or Closes paired with the AB mention tell the app to advance the linked work item to its completed state when the pull request merges.

Why C is wrong: A plain hash reference targets a GitHub issue, not an Azure Boards work item; the app does not treat GitHub issue numbers as Azure Boards ids, so no board link or transition is created.

Why D is wrong: This is tempting because web hooks underpin integrations, but the installed app already handles delivery, and contributors never wire a per pull request web hook to the REST API to make linking work.

Free sampleDesign and Implement Processes and Communicationsmedium

A delivery manager wants a dashboard widget that surfaces how long completed user stories spent in active development, from entering an active state to closing, so the team can track and reduce cycle time. Which "Azure DevOps" dashboard widget is purpose-built to show this?

  • AThe burndown widget, which plots remaining work against time within a sprint so the team can judge whether they are on track to finish the committed scope.
  • BThe query results widget, which lists the work items returned by a saved query so the manager can read the individual stories that have recently been closed.
  • CThe velocity widget, which reports how many story points the team completed each sprint so the manager can forecast the capacity of upcoming iterations.
  • DThe cycle time widget, which charts how long completed work items took from entering an active state to closure so the team can track that duration. Correct
Select the cycle time widget to visualise active-development duration of completed items and identify slow board states. The Analytics-backed cycle time widget measures the elapsed time each completed work item spent from entering an active state to closing. This lets a team track and reduce cycle time for completed items, which a burndown, velocity, or query results tile does not provide.

Why A is wrong: A burndown shows remaining work over a sprint, useful for scope tracking, but it does not measure how long completed items took from active start to closure.

Why B is wrong: A query results tile lists items but performs no cycle time aggregation, so it cannot reveal how long completed stories spent in active development.

Why C is wrong: Velocity reports completed points per sprint for capacity planning and carries no cycle time measure, so it cannot show active-development duration.

Why D is correct: The cycle time widget is built to chart active-development duration for completed items, directly surfacing the cycle time the manager wants to track and reduce.

Free sampleDesign and Implement Processes and Communicationsmedium

A team needs a metrics report that aggregates work item counts and durations over time and groups them by area path, and they want to refresh it in a reporting tool that consumes a queryable analytics endpoint. Which querying approach over "Azure DevOps" data best fits this aggregation and trend reporting need?

  • AQuery the Analytics service through its OData endpoint, since OData exposes aggregated, time-aware work item data that reporting tools can consume and refresh for trend reports. Correct
  • BWrite a Work Item Query Language query in the boards query editor, since WIQL returns matching work items and the editor can group them for time-based aggregate reporting.
  • CCall the REST work items batch endpoint on a schedule, since it returns current field values that a script can total and chart for the area paths in the report.
  • DUse a saved board filter exported as a comma-separated file, since filtering by area path and opening the file in a reporting tool gives the grouped counts the report needs.
Choose the Analytics OData endpoint for aggregated, time-aware metrics reporting that external tools can refresh. The Analytics service exposes an OData endpoint that serves pre-aggregated, historically tracked work item data, which reporting tools can query and refresh on a schedule. WIQL and the work items REST endpoints return current-state records without trend aggregation, so they cannot drive grouped over-time metrics the way Analytics OData can.

Why A is correct: The Analytics OData endpoint is designed for aggregation and historical trend queries and is consumable by reporting tools, matching the grouped, time-aware reporting requirement.

Why B is wrong: WIQL returns flat lists of current work items and lacks historical aggregation, so it cannot produce the over-time grouped trend report the team requires.

Why C is wrong: The work items batch REST endpoint returns point-in-time field values without trend aggregation, forcing custom code and still missing the analytics-endpoint refresh the team wants.

Why D is wrong: An exported board filter is a static snapshot that cannot refresh from a queryable endpoint or carry historical trend data, so it fails the live reporting requirement.

Free sampleDesign and Implement Processes and Communicationsmedium

With the Azure Boards app for "GitHub" installed, a team wants a work item to move to its Done state automatically when a pull request that links it is merged, without anyone touching the board. Which addition to the pull request makes the merge transition the linked work item?

  • AA reviewer comment reading "close 2210" on the pull request, so the Azure Boards app reads the comment thread and closes work item 2210 when the merge happens.
  • BA GitHub Actions step that runs on merge and calls the board's REST API to set work item 2210 to Done, configured once in the repository workflow.
  • CA branch policy requiring work item 2210 to be linked, so completing the pull request flips the linked work item to Done as the policy is satisfied.
  • DThe text "Fixes AB#2210" in the pull request description, so the Azure Boards app transitions the linked work item to Done when the pull request merges. Correct
Use a closing keyword with the AB mention in a pull request so the Azure Boards app transitions the work item on merge. The Azure Boards app for GitHub honours closing keywords such as "Fixes" paired with the "AB#<id>" mention in pull request text. When the pull request merges, the app transitions the referenced work item to a closed state, so the board updates without manual action.

Why A is wrong: A free-text comment is tempting because GitHub surfaces it, but the Azure Boards app does not parse review comments for closing instructions, so no transition occurs.

Why B is wrong: A custom Actions step could update the work item, but it is extra code to build and maintain when the app already supports a mention keyword, so it is not the intended path.

Why C is wrong: A linked-work-item policy enforces the link at merge but performs no state change, so it looks related yet never moves the work item to Done by itself.

Why D is correct: The Azure Boards app recognises a closing keyword combined with the AB mention in a pull request, and on merge it transitions the referenced work item to its closed state automatically.

Other domains in this exam

See also the AZ-400 cert hub, the study guide, and the cheat sheet.

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