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

Design and implement appropriate metrics, queries, and dashboards for DevOps, including cycle time, lead time, and time to recovery.

Define DORA metrics - deployment frequency, lead time for changes, change failure rate, and time to recovery - and understand how cycle time and lead time expose bottlenecks. Configure Azure DevOps dashboards and analytics queries to surface these indicators so teams can measure and improve delivery performance.

DORA metricscycle timelead timeAzure DevOps dashboardsanalytics queries

Practice question for this objective

Free sampleDesign and Implement Processes and Communicationsmedium

An engineering manager is assembling a balanced DevOps scorecard and wants the four metrics that the DORA research programme identifies, two describing delivery throughput and speed and two describing stability of releases. Which set of four metrics matches the DORA framework?

AVelocity, sprint burndown, story point throughput, and team capacity, pairing planning forecasts with execution tracking to describe how predictably the team delivers committed scope.
BDeployment frequency, lead time for changes, change failure rate, and time to restore service, pairing two flow measures of throughput and speed with two stability measures of release reliability. Correct
CDeployment frequency, lead time for changes, mean time between failures, and code coverage percentage, pairing two flow measures with two reliability indicators drawn from testing and operations.
DCycle time, escaped defect count, change failure rate, and time to restore service, pairing a flow measure and a quality count with two stability measures of how releases behave in production.

Recall the four DORA metrics as deployment frequency, lead time, change failure rate, and time to restore service. The DORA programme defines four key metrics: two flow measures, deployment frequency and lead time for changes, and two stability measures, change failure rate and time to restore service. Recognising this exact set distinguishes DORA from Agile planning measures such as velocity and from unrelated quality indicators such as code coverage.

Why A is wrong: These are Agile planning and tracking measures rather than the DORA set, so they describe sprint predictability instead of delivery throughput, speed, and release stability.

Why B is correct: These four are exactly the DORA metrics, with deployment frequency and lead time describing flow and change failure rate and time to restore service describing stability, matching the scorecard the manager wants.

Why C is wrong: Two of these belong to DORA, but mean time between failures and code coverage are not DORA stability metrics, so the set mixes in measures from other disciplines.

Why D is wrong: Cycle time and escaped defect count are not the named DORA flow metrics, so although two stability measures are correct the flow side of the set is wrong.

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.

Compose an OData analytics query expression by hand for each report, paste its endpoint address into Power BI as a web data source, and maintain the expressions as reporting needs change.
Why it is wrong: Raw OData queries do work against the Analytics service but require authoring and maintaining query expressions per report, which is the manual effort the team explicitly wants to avoid.
Lead time, measured from the moment a customer raises the request in the backlog until the corresponding change is running in production for that customer to use.
Why it is wrong: Lead time is a real DORA measure and sounds close, but it starts at request creation rather than first commit, so it captures queue and triage time the team did not ask to include.
Cycle time, measured from a developer's first commit on the item until the change is deployed to production, so it counts only the duration of active development and delivery work.
Why it is wrong: Cycle time is a real DORA flow measure but begins at the first commit, so it excludes the backlog and triage delay the leader explicitly wants the figure to include.

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