A DevOps engineer manages an AWS CodePipeline pipeline that builds and deploys a web application...

Comprehensive and Detailed Explanation From Exact Extract:

To add an automated test in AWS CodePipeline that checks the HTTP response code of a deployed application, the most straightforward and operationally efficient method is to create an AWS Lambda function that makes an HTTP request to the application URL, checks the response code, and then reports success or failure back to CodePipeline.

The Lambda function can be invoked as an action in the pipeline stage.

If the response code is not 200 OK, the Lambda function can return a failure, causing the pipeline stage to fail and halt further execution.

Option A’s CloudWatch synthetic canary monitors are useful for ongoing monitoring but are not natively integrated as CodePipeline actions to control pipeline flow.

Option C incorrectly uses CodeDeploy action for testing, which is not designed for this purpose.

Option D introduces unnecessary complexity by deploying API Gateway and Device Farm, which is not required for a simple HTTP status check.Therefore, option B provides a clean, simple, and fully automated way to enforce HTTP response validation within the pipeline.

Reference from AWS Official Documentation:

AWS CodePipeline Custom Actions:"You can create Lambda invoke actions in your pipeline stages to run custom validation or testing functions."(AWS CodePipeline User Guide - Lambda Actions)

AWS Lambda Function for Health Checks:"Lambda functions can be used to perform health checks or API response validations and report results back to invoking services."(AWS Lambda Developer Guide)