Q91 — AWS SAA-C03 Ch.16

Question 91 of 100 | ← Chapter 16

Q1291. A company asks a solutions architect to review the architecture for its messaging application. The application uses TCP and UDP traffic. The company is planning to deploy a new VoIP feature, but its 10 test users in other countries are reporting poor call quality.The VoIP application runs on an Amazon EC2 instance with more than enough resources. The HTTP portion of the company's application behind an Application Load Balancer has no issues.What should the solutions architect recommend for the company to do to address the VoIP performance issues?

Correct Answer: A. Use AWS Global Accelerator.

Explanation

The correct solution must improve VoIP call quality for international test users while handling TCP and UDP traffic efficiently. The key issues are likely network latency, jitter, or packet loss affecting real-time communication.Correct Answer: A. Use AWS Global Accelerator.Why Option A is Best:Optimizes Real-Time Traffic (VoIP):AWS Global Accelerator uses Anycast IP addresses and AWS's global network backbone to reduce latency and improve packet delivery for TCP/UDP traffic.Critical for VoIP, where low latency and jitter are essential for good call quality.Handles Both TCP and UDP:Unlike Application Load Balancers (ALB) (which only support TCP/HTTP/HTTPS), Global Accelerator supports UDP (used by many VoIP protocols like SIP, RTP).Improves International User Experience:Routes traffic through the nearest AWS edge location, reducing hops and improving speed for users in other countries.Why Other Options Fail:B. Implement Amazon CloudFront into the architecture.Not designed for real-time communication:CloudFront is a CDN for static content (images, videos, APIs)--not for low-latency VoIP traffic.Does not support UDP (required for many VoIP protocols).C. Use an Amazon Route 53 geoproximity routing policy.Only affects DNS resolution:Geoproximity routing can direct users to the nearest region, but does not optimize packet routing after the initial connection.Does not handle UDP or improve real-time performance like Global Accelerator. D. Migrate from Application Load Balancers to Network Load Balancers. NLB improves TCP/UDP performance but doesn't solve global latency:Network Load Balancer (NLB) is better than ALB for low-latency TCP/UDP traffic, but it does not reduce internet routing inefficiencies for international users.Global Accelerator + NLB would be ideal, but Option A alone is sufficient for the given scenario.Key Comparison:RequirementOption A (Global Accelerator)Other OptionsSupports UDP (VoIP protocols) (B: CloudFront; C: Route 53; D: NLB alone doesn't address global routing) Reduces latency for international users(Uses AWS global network) (B: CDN for static content; C: DNS- only; D: No global optimization)Improves real-time performance (jitter, packet loss) (B/C: Not designed for it; D: Only local TCP/UDP optimization)Works with existing EC2 setup(No migration needed) (D: Requires ALB NLB migration)How Option A Works in Practice:Create an AWS Global Accelerator and assign Anycast IP addresses. Configure listeners for TCP/UDP ports used by VoIP (e.g., 5060 for SIP, 16384-32768 for RTP). Point traffic to the existing EC2 instance (or an NLB if scaling is needed later). Users connect to the nearest edge location, reducing latency and improving call quality.Conclusion:AWS Global Accelerator is the best choice to improve VoIP performance for international users by optimizing TCP/UDP routing over AWS's low-latency global network.Final Answer: A