AZ-400 Question 115
Select 2You are designing a DevOps pipeline for a microservices-based e-commerce platform deployed to Azure. The development team wants to include local developer testing, automated unit tests in the build, integration tests against a dedicated test environment, and load tests for performance validation in a staging environment prior to production release. Which two actions should you include in your strategy to align with best practices?
- A
Run integration tests only for major releases to reduce pipeline overhead.
- B
Run local unit tests before each commit, then automate unit tests in the build pipeline.
- C
Execute load tests immediately on developer machines to quickly identify performance regressions.
- D
Configure integration tests to run on a test environment that closely mirrors production after a successful build.
- E
Skip integration tests in pre-production and rely on production monitoring for final validation.
Show answer and explanation
Correct answers: B, D
Explanation
A comprehensive testing strategy in Azure DevOps involves shifting testing as far left as possible to detect issues early. Local tests and automated unit tests validate new code quickly, while integration tests in a production-like test environment catch compatibility issues between services. Load testing in a staging or fully representative environment ensures that the application can handle expected workloads before going live. For more details, refer to Microsoft's official documentation on integrating automated tests in your Azure pipelines (https://learn.microsoft.com/azure/devops/pipelines/test).
- A. Incorrect.
Option 1: Incorrect. Running integration tests only for major releases is risky because issues introduced in minor releases or regular commits can go undetected for too long. Best practices recommend running integration tests frequently to catch defects early in the development cycle.
- B. Correct.
Option 2: Correct. Running unit tests locally before committing code helps identify issues early (shift-left approach), and automating unit tests in the build pipeline provides continuous validation of the codebase. This aligns with common CI/CD best practices in Azure DevOps.
- C. Incorrect.
Option 3: Incorrect. While it� possible to run performance tests locally, load tests are typically done on a staging environment that can simulate production-scale traffic. Developer machines generally lack the resources and realistic environment configuration necessary for accurate load testing results.
- D. Correct.
Option 4: Correct. Integration tests should be run in an environment that closely matches production, ensuring realistic testing conditions. Performing these tests immediately after a successful build allows you to detect service-to-service communication and configuration issues before they reach production.
- E. Incorrect.
Option 5: Incorrect. Skipping pre-production integration tests significantly increases the risk of undiscovered defects being deployed to production. Adhering to a robust testing strategy with thorough integration tests in a test environment is recommended best practice.