AZ-400 Question 116
Select 3You support a microservices-based application hosted in Azure. The development team wants rapid feedback during coding, so they run local tests on their machines. You�ve also set up automated pipelines in Azure DevOps to build, test, and deploy updates. To ensure comprehensive quality control, you need to incorporate local, unit, integration, and load tests. Which of the following approaches should you adopt? (Choose three.)
- A
Encourage developers to run local tests and mock external dependencies before committing code changes.
- B
Include unit tests in your continuous integration (CI) pipeline and fail the build on any test failures.
- C
Run integration tests only in production to capture data from real users in live scenarios.
- D
Perform load tests in a closely matched staging environment and schedule them to identify performance bottlenecks before production.
Show answer and explanation
Correct answers: A, B, D
Explanation
A robust testing strategy involves multiple layers of validation: developers should first run tests locally to ensure quick feedback. Unit tests should be part of the CI pipeline to catch breaking changes early. Integration tests are best run in a dedicated or staging environment rather than in production. Finally, load tests in a production-like environment help identify performance and scalability issues without risking user disruption. Refer to Microsoft documentation and DevOps best practices for recommended architectures and pipeline configurations.
- A. Correct.
Correct. Running local tests helps catch issues early and mocks (or stubs) allow developers to replicate external dependencies without waiting for shared services to be available.
- B. Correct.
Correct. Integrating automated unit tests in the CI pipeline ensures that all code changes are tested for defects as soon as they�re committed. Failing the build on test failures maintains code quality.
- C. Incorrect.
Incorrect. While some organizations might test in production under controlled circumstances (e.g., canary releases), it� generally risky to run full integration tests on live user data because it can disrupt the user experience and make debugging more difficult.
- D. Correct.
Correct. Load testing in a staging or performance-testing environment that mirrors production settings helps reveal bottlenecks before changes affect real users. Scheduling these tests during off-peak times avoids conflicts with active testing or deployments.