A team runs an "Azure Load Testing" test as a step in a release pipeline and wants the pipeline to fail automatically when the load run shows the API's 95th percentile response time exceeding 800 milliseconds, so a slow build never promotes to production. The load test already runs and reports metrics, but a breach currently leaves the pipeline green. What should the team configure so the breach fails the run?
- AAdd a manual approval check on the production environment so a reviewer inspects the "Azure Load Testing" dashboard after the run and rejects the deployment when the response time looks too high.
- BLower the configured number of virtual users in the load test so the API is pushed less hard and the 95th percentile response time stays under the target during the run.
- CAdd an "Application Insights" smart detection rule on response time so an anomaly alert is raised after deployment and the on-call engineer rolls the release back when it fires.
- DDefine a pass or fail criterion in the load test that fails the test when the 95th percentile response time metric exceeds 800 milliseconds, so the failing test fails the pipeline step. Correct
Why A is wrong: A manual approval relies on a person reading the dashboard, which is neither automatic nor a property of the load run, so it does not make the breach itself fail the pipeline.
Why B is wrong: Reducing the load hides the problem by easing the test rather than enforcing a limit, so a genuinely slow build would still pass and reach production.
Why C is wrong: Smart detection alerts on live telemetry after release rather than gating the load run, so the build still promotes before anyone reacts to the alert.
Why D is correct: A pass or fail criterion evaluates the chosen metric against the threshold and marks the load test failed when breached, and a failed test fails the pipeline step automatically without human action.