Answer-first summary for fast verification
Answer: Use AWS Global Accelerator. Create a Network Load Balancer (NLB) in each of the two Regions as an endpoint. Create an Amazon Elastic Container Service (Amazon ECS) cluster with the Fargate launch type. Create an ECS service on the cluster. Set the ECS service as the target for the NLB. Process the data in Amazon ECS.
## Explanation **Correct Answer: B** **Key Requirements Analysis:** 1. **UDP protocol support** - The application receives data from devices using UDP 2. **Minimizes latency** - For geographically dispersed devices 3. **Rapid failover to another AWS Region** - Fast regional failover capability 4. **Real-time processing** - Processes data immediately and sends responses back **Why Option B is Correct:** 1. **AWS Global Accelerator** provides optimal routing and minimizes latency by: - Using AWS global network infrastructure - Providing static anycast IP addresses that route to the nearest healthy endpoint - Automatically routing traffic to the closest healthy endpoint 2. **Network Load Balancer (NLB)** is required because: - NLB supports Layer 4 (TCP/UDP) load balancing - The application uses UDP protocol (mentioned in the question) - NLB preserves source IP addresses, which is important for sending responses back to devices 3. **Rapid Regional Failover**: - Global Accelerator provides automatic health checks and failover between regions - Failover typically occurs within seconds (1-2 minutes) - Much faster than Route 53 DNS-based failover which depends on DNS TTL 4. **ECS with Fargate** provides: - Containerized processing environment - Serverless compute for processing data - Scalability to handle thousands of devices **Why Other Options are Incorrect:** **Option A (Route 53 + NLB + Lambda):** - Route 53 failover routing is DNS-based and depends on DNS TTL (typically 60+ seconds) - Not as rapid as Global Accelerator's failover - Lambda can process data but may have cold start latency **Option C (Global Accelerator + ALB + ECS):** - ALB operates at Layer 7 (HTTP/HTTPS) only - ALB does not support UDP protocol - The application uses UDP, so ALB is not suitable **Option D (Route 53 + ALB + ECS):** - Route 53 has slower failover than Global Accelerator - ALB does not support UDP protocol - Double disadvantage: slower failover + wrong load balancer type **Key Technical Points:** - **UDP vs TCP**: UDP is connectionless and used for real-time applications where speed is critical - **NLB vs ALB**: NLB works at Layer 4 (TCP/UDP), ALB works at Layer 7 (HTTP/HTTPS only) - **Global Accelerator vs Route 53**: Global Accelerator provides faster failover and better latency optimization for real-time applications - **Health Checks**: Global Accelerator performs continuous health checks on endpoints for rapid failover detection **Best Practice Recommendation:** For real-time UDP applications with geographically dispersed devices requiring minimal latency and rapid regional failover, AWS Global Accelerator with NLB endpoints is the optimal architecture.
Ultimate access to all questions.
No comments yet.
Author: LeetQuiz Editorial Team
A company runs an application that receives data from thousands of geographically dispersed remote devices that use UDP. The application processes the data immediately and sends a message back to the device if necessary. No data is stored.
The company needs a solution that minimizes latency for the data transmission from the devices. The solution also must provide rapid failover to another AWS Region.
Which solution will meet these requirements?
A
Configure an Amazon Route 53 failover routing policy. Create a Network Load Balancer (NLB) in each of the two Regions. Configure the NLB to invoke an AWS Lambda function to process the data.
B
Use AWS Global Accelerator. Create a Network Load Balancer (NLB) in each of the two Regions as an endpoint. Create an Amazon Elastic Container Service (Amazon ECS) cluster with the Fargate launch type. Create an ECS service on the cluster. Set the ECS service as the target for the NLB. Process the data in Amazon ECS.
C
Use AWS Global Accelerator. Create an Application Load Balancer (ALB) in each of the two Regions as an endpoint. Create an Amazon Elastic Container Service (Amazon ECS) cluster with the Fargate launch type. Create an ECS service on the cluster. Set the ECS service as the target for the ALB. Process the data in Amazon ECS.
D
Configure an Amazon Route 53 failover routing policy. Create an Application Load Balancer (ALB) in each of the two Regions. Create an Amazon Elastic Container Service (Amazon ECS) cluster with the Fargate launch type. Create an ECS service on the cluster. Set the ECS service as the target for the ALB. Process the data in Amazon ECS.