Answer-first summary for fast verification
Answer: Place the EC2 instances behind a Network Load Balancer (NLB). Configure TCP listeners. Create an AWS Global Accelerator accelerator in front of the NLB. Use Bring Your Own IP (BYOIP) from the on-premises network with Global Accelerator.
To meet the requirements of minimizing latency and not reconfiguring the hardware sensor modules, the company should use AWS Global Accelerator in front of a Network Load Balancer (NLB). AWS Global Accelerator improves the availability and performance of your applications with local or global users. It provides static IP addresses that act as a fixed entry point to your application endpoints in a single or multiple AWS Regions. This setup allows the company to use the same IP addresses (BYOIP) that were hardcoded into the hardware sensor modules, ensuring no reconfiguration is needed. The NLB is chosen over ALB because MQTT uses TCP, and NLB is optimized for TCP traffic. CloudFront is not suitable for this scenario as it is designed for content delivery and not for TCP-based protocols like MQTT.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
An IoT company with globally deployed hardware sensor modules sends temperature, humidity, pressure, and location data via the MQTT protocol to on-premises MQTT brokers running on Linux servers behind a load balancer. The sensor modules are hardcoded with public IP addresses to connect to the brokers. Due to global expansion, the current solution faces scalability issues and increased latency. The company plans to migrate its infrastructure to AWS without reconfiguring the deployed sensor modules and aims to minimize latency. After migrating the MQTT brokers to Amazon EC2 instances, what steps should the company take next to fulfill these requirements?
A
Place the EC2 instances behind a Network Load Balancer (NLB). Configure TCP listeners. Use Bring Your Own IP (BYOIP) from the on-premises network with the NLB.
B
Place the EC2 instances behind a Network Load Balancer (NLB). Configure TCP listeners. Create an AWS Global Accelerator accelerator in front of the NLB. Use Bring Your Own IP (BYOIP) from the on-premises network with Global Accelerator.
C
Place the EC2 instances behind an Application Load Balancer (ALB). Configure TCP listeners. Create an AWS Global Accelerator accelerator in front of the ALB. Use Bring Your Own IP (BYOIP) from the on-premises network with Global Accelerator.
D
Place the EC2 instances behind an Amazon CloudFront distribution. Use Bring Your Own IP (BYOIP) from the on-premises network with CloudFront.