DOP-C02 · Question #389
A company is developing an ecommerce application on AWS. The company wants to make sure that the application can handle sudden increases in traffic. The company uses AWS CodePipeline for its CI/CD…
The correct answer is D. Use AWS CodeBuild to run tools for load tests, store the test artifacts in Amazon S3, and. By using AWS CodeBuild as a pipeline stage to run your load‑test toolchain, you leverage a fully managed build environment with zero servers to manage. CodeBuild artifacts (logs, reports) land in S3 automatically, and you can emit custom CloudWatch metrics from your tests to…
Question
A company is developing an ecommerce application on AWS. The company wants to make sure that the application can handle sudden increases in traffic. The company uses AWS CodePipeline for its CI/CD process. The company must implement a solution to integrate automated load testing into the CI/CD pipeline to validate the application's performance. The solution must perform production deployment only if the performance exceeds a threshold. Which solution will meet these requirements with the LEAST operational overhead?
Options
- ADeploy the application by using AWS Elastic Beanstalk. Enable load balancing. Use Elastic
- BImplement AWS Fargate tasks to run tools for load tests. Use Amazon Elastic container Service
- CLaunch Amazon EC2 instances to run tools for load tests. Store test scripts in a GitHub
- DUse AWS CodeBuild to run tools for load tests, store the test artifacts in Amazon S3, and
How the community answered
(39 responses)- A8% (3)
- B18% (7)
- C31% (12)
- D44% (17)
Explanation
By using AWS CodeBuild as a pipeline stage to run your load‑test toolchain, you leverage a fully managed build environment with zero servers to manage. CodeBuild artifacts (logs, reports) land in S3 automatically, and you can emit custom CloudWatch metrics from your tests to flag breaches of your performance SLA. A lightweight Lambda invoked via a CodePipeline custom action can inspect those alarms or metrics and return success or failure to gate the production deploy. This approach reuses native CI/CD services end-to-end, minimizes custom infrastructure, and adds virtually no operational overhead.
Topics
Community Discussion
No community discussion yet for this question.