
Ultimate access to all questions.
A startup's application team is deploying a new multi-tier application in the AWS Cloud, hosted on Amazon EC2 instances within an Auto Scaling group behind a publicly accessible Network Load Balancer (NLB). The application handles both UDP and TCP traffic. Initially, the application will serve users in a single geographic location, but the team plans to expand globally by deploying the application across multiple AWS Regions to reduce latency for end users. The team also aims to control traffic distribution across Regions during new version rollouts while minimizing first-byte latency and jitter. How should the application team design the network architecture to meet these requirements?
A
Create an Amazon CloudFront distribution to align to each Regional deployment. Set the NLB for each Region as the origin for each CloudFront distribution. Use an Amazon Route 53 weighted routing policy to control traffic to the newer Regional deployments.
B
Create an AWS Global Accelerator accelerator and listeners for the required ports. Configure endpoint groups for each Region. Configure a traffic dial for the endpoint groups to control traffic to the newer Regional deployments. Register the NLBs with the endpoint groups.
C
Use Amazon S3 Transfer Acceleration for the application in each Region. Adjust the amount of traffic that each Region receives from the Transfer Acceleration endpoints to the Regional NLBs.
D
Create an Amazon CloudFront distribution that includes an origin group. Set the NLB for each Region as the origins for the origin group. Use an Amazon Route 53 latency routing policy to control traffic to the new Regional deployments.