An IoT company has sensor modules worldwide that send MQTT data to on-premises MQTT brokers at hardcoded public IP addresses. After migrating the brokers to EC2 in AWS, the company must avoid reconfiguring deployed hardware and minimize latency for global customers. What should the company do next?

The correct solution uses Global Accelerator with BYOIP and an NLB. Global Accelerator provides static Anycast IP addresses, allowing you to use your existing public IP addresses (BYOIP) and route traffic to the nearest AWS edge location, minimizing latency for global customers without reconfiguring hardware. An NLB is suitable for MQTT (TCP) traffic and supports the high throughput required. The first incorrect option lacks Global Accelerator, meaning traffic won't be routed to the nearest edge location, increasing latency for global users. The third option uses an Application Load Balancer (ALB), which is designed for HTTP/HTTPS traffic, not raw TCP like MQTT. The fourth option uses CloudFront, a Content Delivery Network (CDN) primarily for caching web content, not for direct MQTT broker connections.