AZ400-Q: isolate integration-test dependencies
Integration tests need a database but must not share mutable data between parallel runs. What should the pipeline use?
- A) One permanent shared production-like database for all branches.
- B) A developer’s local database.
- C) Per-run isolated test dependencies, such as disposable containers or uniquely provisioned test resources, with cleanup. ✓
- D) No integration tests.
Answer: C. Isolation prevents cross-run interference and makes tests repeatable; cleanup controls cost and residue.
Why not the others: Shared/local/no testing produces flakiness, risk, or missing confidence.
Related
pipeline-integration-tests · self-hosted-agent · pipeline-maintenance