An image-storage web app runs on EC2 instances in an Auto Scaling group behind an ALB. Images are stored in S3. The company wants a new feature where test requests are routed to a separate target group hosting a beta version of the app. Which approach accomplishes this with the least effort?

The correct approach leverages the Application Load Balancer's (ALB) content-based routing capabilities. By creating a new target group and Auto Scaling group for the beta app, and then configuring an ALB rule to route requests containing a specific cookie ("version=beta") to this new target group, you achieve the desired outcome with minimal overhead. The test system simply needs to include this cookie in its requests. Incorrect options: Creating a new ALB and Route 53 record adds unnecessary infrastructure and management complexity for a simple A/B test or beta deployment. Using CloudFront with Lambda@Edge to route to a new ALB is overly complex and expensive for this scenario, introducing more components than needed. Using CloudFront with Lambda@Edge to add a cookie is also an over-engineered solution. The test system can directly send the cookie, making Lambda@Edge redundant.