AZ-400 Question 17
Select 3You are designing metrics for a new microservice-based architecture running in Azure. Your leadership team wants to track the microservice� performance, specifically focusing on average request latency, error rates, and how often builds fail or get canceled in the CI/CD pipeline. Which three metrics or queries should you implement to fulfill these requirements?
- A
An Azure Monitor metrics alert measuring CPU usage across all VMs with a 30-minute aggregation interval
- B
An Azure Monitor metrics query measuring average request latency for the microservice
- C
An Application Insights log query counting the total number of user sign-ups
- D
An Azure DevOps Analytics query tracking the frequency of failed or canceled builds
- E
An Application Insights log query measuring the error rate for the microservice
Show answer and explanation
Correct answers: B, D, E
Explanation
In DevOps, focusing on metrics that reveal the microservice's end-to-end health and deployment reliability is key. Average request latency (Option 2) and error rate (Option 5) provide clear indicators for application performance. Meanwhile, tracking build failures (Option 4) addresses CI/CD pipeline stability. Microsoft� DevOps best practices and Azure documentation recommend using Azure Monitor, Application Insights, and Azure DevOps Analytics to capture these metrics. By regularly reviewing these metrics, teams can quickly detect and address critical issues, ensuring faster feedback loops and higher quality releases.
- A. Incorrect.
Option 1: Although monitoring CPU usage is helpful for infrastructure health, it does not directly measure the microservice� performance in terms of latency, error rates, or build failures. The 30-minute aggregation interval may also be too coarse to quickly detect issues.
- B. Correct.
Option 2 (Correct): Measuring average request latency with Azure Monitor metrics is essential for evaluating microservice performance. It provides insight into response times and helps identify if code changes or infrastructure problems are causing latency spikes.
- C. Incorrect.
Option 3: Tracking the total number of user sign-ups is a valuable business metric but does not directly reflect the microservice� reliability or CI/CD health. It does not address latency or error rates.
- D. Correct.
Option 4 (Correct): An Azure DevOps Analytics query is the right approach to track how frequently builds fail or get canceled. This metric helps teams gauge the stability of their CI/CD process and detect issues quickly.
- E. Correct.
Option 5 (Correct): Monitoring the microservice� error rate with Application Insights is a core DevOps practice. High error rates can indicate deployment issues or code regressions that need immediate attention.