AWS Certified Solutions Architect - Associate
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A company provides a Voice over Internet Protocol (VoIP) service that uses UDP connections. The service consists of Amazon EC2 instances that run in an Auto Scaling group. The company has deployments across multiple AWS Regions.
The company needs to route users to the Region with the lowest latency. The company also needs automated failover between Regions.
Which solution will meet these requirements?
Other
Community
UAnonymous
A
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.
B
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.
C
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.
D
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.
Explanation:
Explanation
Correct Answer: A
Why Option A is correct:
- VoIP service uses UDP connections - Network Load Balancer (NLB) supports Layer 4 (TCP/UDP) traffic, while Application Load Balancer (ALB) only supports Layer 7 (HTTP/HTTPS) traffic. Since VoIP typically uses UDP for real-time communication, NLB is required.
- Lowest latency routing - AWS Global Accelerator provides automatic routing to the AWS endpoint with the lowest latency based on real-time network conditions.
- Automated failover between Regions - Global Accelerator provides automatic failover between endpoints in different Regions when health checks detect issues.
- Architecture - Deploying NLB in each Region with Auto Scaling groups, then using those NLBs as Global Accelerator endpoints provides both low-latency routing and cross-Region failover.
Why other options are incorrect:
Option B: ALB only supports HTTP/HTTPS traffic, not UDP which is required for VoIP services.
Option C: While NLB is correct for UDP traffic, using Route 53 latency routing with CloudFront is not optimal because:
- Route 53 latency routing is DNS-based, which doesn't provide real-time network condition adjustments
- CloudFront is designed for HTTP/HTTPS content delivery, not UDP-based VoIP traffic
- This solution lacks automated failover capabilities between Regions
Option D: ALB is incorrect for UDP traffic, and weighted routing in Route 53 doesn't provide latency-based routing. CloudFront is also not suitable for UDP traffic.
Key AWS Services:
- Network Load Balancer (NLB): Layer 4 load balancer that supports TCP/UDP traffic
- AWS Global Accelerator: Provides static IP addresses and routes traffic to optimal AWS endpoints based on latency and health
- Auto Scaling Groups: Ensures high availability within each Region
- Target Groups: Used to route traffic to registered targets (EC2 instances in Auto Scaling groups)
Comments
Loading comments...