AZ400-Q: place load testing in delivery
A service change may affect checkout throughput. The team needs realistic load evidence before broad production rollout without making every pull request take an hour. What is the best design?
- A) Skip load tests because unit tests pass.
- B) Run full load tests on every editor save.
- C) Run load tests only after a customer reports slowness.
- D) Run fast tests on pull requests, then run representative load tests in a controlled preproduction/release stage with defined promotion criteria. ✓
Answer: D. Layered testing balances fast feedback with realistic performance validation before wider exposure.
Why not the others: Skipping/postponing performance evidence is risky; every-save load tests are usually wasteful.
Related
pipeline-integration-tests · compliance-gate · deployment-environment