Design and Implement Appropriate Metrics and Queries for DevOps AZ-400 Practice Questions (Page 4)

Questions 16–20

1. 16expert · hard

   A team deploys to production multiple times per day. They want to measure the reliability of their delivery process, but they are concerned that a simple change failure rate (percentage of deployments causing incidents) is too coarse because some failures are minor and do not affect users. Which refinement to the change failure rate metric would give them a more nuanced view?

   • AClassify failures by severity (e.g., critical, major, minor) and track the percentage of deployments in each category
   • BTrack only deployments that cause a rollback
   • CTrack the percentage of deployments that are delayed
   • DTrack the number of deployments per day
   Reveal Solution Discussion Select an answer first
2. 17foundation · easy

   Which metric is used to evaluate the effectiveness of a testing process by measuring the percentage of defects that are caught by the test suite before release?

   • ATest coverage
   • BMean time to detect (MTTD)
   • CDefect detection percentage (DDP)
   • DDefect escape rate
   Reveal Solution Discussion Select an answer first
4. 18expert · hard

   An operations team wants to improve the reliability of their application. They have been tracking availability and MTTR, but the SLO is still not met. An analysis shows that most downtime occurs during peak traffic hours, and the team suspects that scaling is too slow. Which metric should they add to their monitoring to confirm this hypothesis?

   • AMemory usage at peak traffic
   • BNumber of scaling events per day
   • CCPU usage average over the last 24 hours
   • DTime to scale: the time between a scaling trigger and the new instance becoming ready
   Reveal Solution Discussion Select an answer first
5. 19expert · hard · select all that apply

   A DevOps team wants to create a dashboard for executives that shows the overall health of their software delivery process. They have data on lead time, cycle time, deployment frequency, change failure rate, and MTTR. They want to show a balanced view that includes both speed and stability. Which two widgets should they include? (Select all that apply.)

   • AA cumulative flow diagram.
   • BA trend chart of lead time for changes.
   • CA chart of MTTR for incidents.
   • DA trend chart of change failure rate.
   Check answers Discussion Select an answer first
6. 20expert · hard

   A team uses Azure Boards with a custom workflow: New -> In Progress -> In Review -> Done. They want to reduce the time work items spend in the In Review state, which they suspect is a bottleneck. They have a query that calculates the average time in the In Review state for completed items. However, the average is skewed by a few items that were blocked for weeks. The team wants a metric that is not skewed by outliers and that they can use to set a realistic improvement target. Which approach should they use?

   • AUse the median time in the In Review state instead of the average
   • BUse the 95th percentile of time in the In Review state
   • CRemove all items that took longer than one week from the query
   • DCalculate the average time in the In Review state for only the last 30 days
   Reveal Solution Discussion Select an answer first