Ultimate access to all questions.
A company operates an application on the AWS Cloud, where the core business logic is executed on a set of EC2 instances within an Auto Scaling group. Traffic to these instances is managed by an Application Load Balancer (ALB), and the Route 53 DNS record 'api.example.com' directs traffic to this ALB. The development team is introducing significant updates to the business logic. To adhere to company policy, during deployment, only 10% of customers should initially experience the new logic in a controlled testing phase, with each customer consistently receiving the same version of the logic throughout this period. What is the most appropriate method for deploying these updates to satisfy these conditions?
A
Establish a secondary ALB and deploy the updated logic to a new set of EC2 instances in a separate Auto Scaling group. Configure this new ALB to handle traffic to the EC2 instances. Modify the Route 53 record to implement weighted routing, directing it to both ALBs.
B
Form a new target group linked to the existing ALB. Deploy the updated logic to EC2 instances within this target group. Adjust the ALB listener rules to incorporate weighted target groups. Implement ALB target group stickiness to ensure session consistency.
C
Develop a fresh launch configuration for the Auto Scaling group, utilizing the AutoScalingRollingUpdate policy with a MaxBatchSize of 10. Replace the current launch configuration in the Auto Scaling group and proceed with the deployment of the updates.
D
Create an additional Auto Scaling group associated with the ALB. Deploy the updated logic to a new set of EC2 instances in this group. Modify the ALB's routing algorithm to use the least outstanding requests (LOR) method. Enable ALB session stickiness to maintain session integrity.