Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might h

Question

Options

• AYes
• BNo

• A
  75% (51)
• B
  25% (17)

Explanation

Option A (Yes) is correct because Azure DevOps's flaky test management feature is specifically designed to handle tests that fail intermittently without being related to code changes or environmental issues - exactly the scenario described. When enabled, flaky test management automatically detects and marks unreliable tests as "flaky," preventing them from blocking the pipeline and reducing the need for manual investigation each time they fail. This directly minimizes troubleshooting effort by surfacing the known flaky behavior rather than treating each failure as a new defect.

There are no other distractors in this Yes/No question, but the temptation is to choose "No" if you're unfamiliar with Azure's flaky test management feature or confuse it with other solutions like re-running failed tests, adjusting test timeouts, or quarantining tests manually - none of which are as targeted or automated for this specific problem.

Memory Tip: Think of "flaky" as the key word - if a test fails randomly and without code changes, it's a flaky test, and Azure DevOps has a feature named exactly after that problem. Match the problem name to the feature name: flaky problem = flaky test management. If you see intermittent, non-reproducible failures unrelated to code, always think of this feature first.

No community discussion yet for this question.