AZ-400 Question 204
Select 2You manage an Azure DevOps pipeline that has a high failure rate, takes longer than expected to complete, and includes multiple tests that pass or fail inconsistently across different runs. Which two actions can help you monitor and improve the pipeline� reliability over time?
- A
Implement pipeline dashboards in Azure DevOps to visualize overall build duration trends, pass/fail rates, and regularly review analytics for signs of flaky tests.
- B
Leverage Flaky Test Management features in Azure Test Plans (or supported extensions) to identify and track intermittent test failures, then prioritize fixes.
- C
Completely remove all integration tests from the pipeline to reduce the chance of test-related failures and accelerate build times.
- D
Disable all code coverage checks to avoid failing the pipeline when coverage thresholds are not met, thereby reducing overall failure rates.
Show answer and explanation
Correct answers: A, B
Explanation
Monitoring pipeline health in Azure DevOps involves tracking build duration, identifying intermittent or flaky tests, and understanding overall failure trends to improve reliability. Dashboards and analytics provide visual insights into pipeline behavior, while tooling for flaky test detection helps isolate and resolve unreliable tests. For additional guidance, refer to Microsoft documentation on monitoring build pipelines and managing flaky tests at https://learn.microsoft.com/azure/devops.
- A. Correct.
Explanation for Option 1: Implementing pipeline dashboards and analytics is a recommended approach. Dashboards help you track trends, duration, and failure rates over time, making it easier to isolate when failures spike or when runs take longer. This data can pinpoint performance bottlenecks and guide targeted improvements.
- B. Correct.
Explanation for Option 2: Leveraging Flaky Test Management (or extensions that detect intermittent test failures) is key to improving reliability. Identifying tests that fail sporadically saves time spent debugging inconsistent issues, and fixing these tests contributes significantly to stabilizing builds.
- C. Incorrect.
Explanation for Option 3: Removing all integration tests might reduce pipeline time, but it also removes a critical layer of quality checks. This approach might temporarily lower failures, but it does not address the underlying causes of flaky or failing tests and compromises overall product quality.
- D. Incorrect.
Explanation for Option 4: Disabling coverage checks may reduce the number of failures, but it doesn't address instability or flakiness. Code coverage is an important metric for ensuring comprehensive testing. Removing it eliminates a key indicator of test quality without solving underlying test reliability issues.