Answer: Configure AWS Global Accelerator to forward requests to a Network Load Balancer. Use Amazon EC2 instances for the application in an EC2 Auto Scaling group.

## Explanation **Correct Answer: C** **Why Option C is correct:** 1. **UDP-based traffic requirement**: The application supports only UDP-based traffic. AWS Global Accelerator supports both TCP and UDP traffic, while Application Load Balancers (ALB) only support TCP/HTTP/HTTPS. Network Load Balancers (NLB) support both TCP and UDP traffic. 2. **Low latency and nearest edge location routing**: AWS Global Accelerator uses the AWS global network to route traffic to the nearest edge location, providing low latency and improved performance for global users. 3. **Static IP addresses**: AWS Global Accelerator provides static IP addresses (anycast IPs) that don't change, which is important for gaming applications that may have firewall rules or DNS caching requirements. 4. **Modified Linux kernel requirement**: The application runs on a modified Linux kernel, which requires EC2 instances (not Lambda) since Lambda doesn't allow custom kernels. **Why other options are incorrect:** - **Option A**: Route 53 is DNS-based and doesn't provide static IP addresses or UDP support. Application Load Balancer doesn't support UDP traffic. - **Option B**: CloudFront is a CDN optimized for HTTP/HTTPS traffic, not UDP. Lambda doesn't support custom kernels. - **Option D**: API Gateway is for REST/WebSocket APIs (HTTP-based), not UDP traffic. Application Load Balancer doesn't support UDP. **Key AWS Services:** - **AWS Global Accelerator**: Provides static IP addresses, routes traffic to nearest edge location, supports UDP/TCP - **Network Load Balancer**: Supports UDP traffic, works at Layer 4 - **EC2 Auto Scaling**: Allows custom kernels and provides compute resources for the modified Linux kernel application

Author: LeetQuiz Editorial Team