ANS-C01 · Question #172
An IoT company collects data from thousands of sensors that are deployed in the Unites States and South Asia. The sensors use a proprietary communication protocol that is built on UDP to send the…
The correct answer is A. Use AWS Global Accelerator with the existing NLB. C. Create a second deployment of the EC2 instances and the NLB in the ap-south-1 Region. Use an. To address data loss for global IoT sensors connecting to an NLB-backed application, leverage AWS Global Accelerator to optimize routing for the existing deployment and deploy a second, geographically closer NLB-backed fleet, also managed by Global Accelerator, to serve sensors…
Question
An IoT company collects data from thousands of sensors that are deployed in the Unites States and South Asia. The sensors use a proprietary communication protocol that is built on UDP to send the data to a fleet of Amazon EC2 instances. The instances are in an Auto Scaling group and run behind a Network Load Balancer (NLB). The instances, Auto Scaling group, and NLB are deployed in the us-west-2 Region. Occasionally, the data from the sensors in South Asia gets lost in transit over the internet and does not reach the EC2 instances. Which solutions will resolve this issue? (Choose two.)
Options
- AUse AWS Global Accelerator with the existing NLB.
- BCreate an Amazon CloudFront distribution. Specify the existing NLB as the origin.
- CCreate a second deployment of the EC2 instances and the NLB in the ap-south-1 Region. Use an
- DCreate a second deployment of the EC2 instances and the NLB in the ap-south-1 Region. Use an
- ETurn on enhanced networking on the EC2 instances by using the most recent Elastic Network
How the community answered
(60 responses)- A55% (33)
- B25% (15)
- D13% (8)
- E7% (4)
Why each option
To address data loss for global IoT sensors connecting to an NLB-backed application, leverage AWS Global Accelerator to optimize routing for the existing deployment and deploy a second, geographically closer NLB-backed fleet, also managed by Global Accelerator, to serve sensors in South Asia.
AWS Global Accelerator improves availability and performance for global users by directing traffic to the closest healthy endpoint over the AWS global network, reducing latency and packet loss for sensors connecting to the existing NLB.
Amazon CloudFront is a Content Delivery Network (CDN) primarily for HTTP/HTTPS content, not suitable for UDP-based IoT messaging or direct backend load balancing for raw traffic.
Deploying a second fleet of EC2 instances and an NLB in a region closer to South Asia (e.g., ap-south-1) significantly reduces network latency and packet loss for local sensors, and when combined with Global Accelerator, provides optimal routing and resilience for a global user base.
This option is incomplete, but even if completed as a regional deployment, it lacks the global traffic management of Global Accelerator explicitly stated in option A, which is crucial for optimal routing between multiple regions.
Enhanced networking improves host-level network throughput and PPS performance for EC2 instances but does not address issues of data loss due to long-distance internet routing from global sensors; it's a host optimization, not a network path optimization.
Concept tested: AWS Global Accelerator and Multi-Region Deployment for Global Performance/Reliability
Source: https://aws.amazon.com/global-accelerator/
Topics
Community Discussion
No community discussion yet for this question.