Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 29 discussion

agree with A, Global Accelerator has automatic failover and is perfect for this scenario with VoIP https://aws.amazon.com/global-accelerator/faqs/

CloudFront uses Edge Locations to cache content while Global Accelerator uses Edge Locations to find an optimal pathway to the nearest regional endpoint. CloudFront is designed to handle HTTP protocol meanwhile Global Accelerator is best used for both HTTP and non-HTTP protocols such as TCP and UDP. so i think A is a better answer

UDP - User Datagram Protocol (UDP) is a transport layer protocol used for sending messages (datagrams) between applications over a network. UDP is part of the Internet Protocol (IP) suite and is defined by Internet Engineering Task Force (IETF) standards in RFC 768.

C is not correct, because Network Loadbalancer is already integrated with Route 53.

i full understand this is a use case for global accelerator but can anyone tell me why you need a NLB over an ALB here?

The Nature of the application VoIP needs NLB and Global Accelerator + an auto scalling

cloudfront doenst provide autoatic failover

NLB is suitable for UDP and global accelerator is also suitable for UDP.

The correct answer is 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. Key reasons: NLB supports UDP protocol (required for VoIP), while ALB only handles HTTP/HTTPS Global Accelerator provides: Automatic routing to lowest latency region Built-in cross-region failover Optimized network performance via AWS global network

Cloudfront is not support UDP Protocol. So maybe C answer isnt correct.

I think this is not a very well written one. What we need: 1, Network Service that handles latency based policy and cross region failover -> Route53 2, A component that route traffic to ASG that are compatible with UDP -> Network Load Balancer.

Aws GA is most suitable for https.

A : UDP so NLB and Global Accelerator reduces the number of hops by providing packets to travel over congestion free AWS global network. Global Accelerator supported end point : ALB,NLB,EC2 & Elastic IP address

you can configure a Network Load Balancer (NLB) in each AWS Region to address your on-premises endpoints. Then you can register the NLBs as endpoints in your AWS Global Accelerator configuration. https://aws.amazon.com/global-accelerator/faqs/

UDP Connection :- So NLB Routing to region having lowest latency and also with Automated failover, Also non-HTTP use cases, such as gaming (UDP), or Voice over IP - Global Accelerator

A is correct because Accelerator endpoint usefull more than route53

Correct as Global accelerator is most preferred for TCP and UDP