Which solution will meet these requirements?
Deploy a Network Load Balancer (NLB) and an associated target group. Associate the target group with the Auto Scaling group. Use the NLB as an AWS Global Accelerator endpoint in each Region.
Deploy an Application Load Balancer (ALB) and an associated target group. Associate the target group with the Auto Scaling group. Use the ALB as an AWS Global Accelerator endpoint in each Region.
Deploy a Network Load Balancer (NLB) and an associated target group. Associate the target group with the Auto Scaling group. Create an Amazon Route 53 latency record that points to aliases for each NLB. Create an Amazon CloudFront distribution that uses the latency record as an origin.
Deploy an Application Load Balancer (ALB) and an associated target group. Associate the target group with the Auto Scaling group. Create an Amazon Route 53 weighted record that points to aliases for each ALB. Deploy an Amazon CloudFront distribution that uses the weighted record as an origin.
Explanations:
Using a Network Load Balancer (NLB) with AWS Global Accelerator in each Region provides low latency routing and automated failover. Global Accelerator routes users to the Region with the lowest latency and provides automatic failover in case of a Region failure. NLB supports UDP, which is suitable for VoIP traffic.
While an Application Load Balancer (ALB) with AWS Global Accelerator can handle multi-Region routing, ALB primarily supports HTTP/HTTPS, making it unsuitable for UDP-based VoIP traffic. NLB is the appropriate choice for UDP.
A Network Load Balancer with Route 53 latency records offers low-latency routing but lacks the automatic failover capabilities provided by Global Accelerator. Also, CloudFront does not support UDP, making this option incompatible with VoIP UDP requirements.
An Application Load Balancer with weighted Route 53 records does not provide latency-based routing or support UDP, making it unsuitable for a UDP-based VoIP service that requires latency-based routing and failover.