A company’s application receives UDP data from thousands of geographically dispersed remote devices, processes it immediately, and may send a reply. No data is stored. The solution must minimize transmission latency and provide rapid failover to another AWS Region. Which solution meets these requirements?

The correct solution uses AWS Global Accelerator, which provides static IP addresses and leverages the AWS global network to reduce latency for geographically dispersed users, making it ideal for minimizing transmission latency. It also offers rapid failover between regions. Network Load Balancers (NLBs) support UDP traffic, which is required by the application. Amazon ECS with Fargate provides a scalable, serverless compute environment to process the data immediately. Incorrect options: Route 53 failover routing relies on DNS propagation, which is slower for failover than Global Accelerator's direct health checks and routing. NLBs are correct for UDP, but Lambda has limitations on UDP event sources without additional services. Using an Application Load Balancer (ALB) is incorrect because ALBs do not natively support UDP traffic. This option combines the slower failover of Route 53 with the incorrect choice of an ALB for UDP traffic.