DOP-C02 · Question #454
A company has a stateless web application that is deployed on Amazon EC2 instances. The EC2 instances are in a target group behind an Application Load Balancer (ALB). Amazon Route 53 manages the…
The correct answer is B. Deploy the beta version to new EC2 instances in a new target group. Associate the new target. ALB supports weighted target groups for traffic splitting between versions without DNS-level changes. By attaching multiple target groups (old & beta) to the same ALB listener rule with weights (90/10), partial traffic testing can occur seamlessly. This is the recommended…
Question
A company has a stateless web application that is deployed on Amazon EC2 instances. The EC2 instances are in a target group behind an Application Load Balancer (ALB). Amazon Route 53 manages the application domain. The company updates the application UI and develops a beta version of the application. The company wants to test the beta version on 10% of its traffic. Which solution will meet these requirements with the LEAST number of configuration changes?
Options
- ADeploy the beta version to new EC2 instances in a new target group. Associate the new target
- BDeploy the beta version to new EC2 instances in a new target group. Associate the new target
- CRefactor the application to implement a feature flag for the beta version by using AWS AppConfig.
- DContainerize and deploy the application on Amazon Elastic Container Service (Amazon ECS).
How the community answered
(30 responses)- A17% (5)
- B50% (15)
- C27% (8)
- D7% (2)
Explanation
ALB supports weighted target groups for traffic splitting between versions without DNS-level changes. By attaching multiple target groups (old & beta) to the same ALB listener rule with weights (90/10), partial traffic testing can occur seamlessly. This is the recommended least- change method per Application Load Balancer advanced request routing documentation.
Topics
Community Discussion
No community discussion yet for this question.