An IoT company sells hardware sensor modules that periodically send out temperature, humidity, pressure, and location data through the MQTT messaging…

This solution correctly addresses all the company's requirements. AWS Global Accelerator is designed to improve the performance and availability of applications for a global user base by directing traffic to the optimal endpoint over the AWS global network, thus minimizing latency. Crucially, Global Accelerator supports the Bring Your Own IP (BYOIP) feature, which allows the company to use its existing hardcoded public IP addresses in AWS, eliminating the need to reconfigure the deployed IoT sensors.

The Network Load Balancer (NLB) is the appropriate choice for handling the MQTT traffic. As a Layer 4 load balancer, it supports TCP listeners and is designed for high-throughput, low-latency workloads with long-lived connections, which is characteristic of the MQTT protocol.

A. A standalone Network Load Balancer is a regional service. It would not solve the core problem of minimizing latency for a global customer base, as all traffic would still traverse the public internet to a single region.

C. An Application Load Balancer (ALB) operates at Layer 7 (HTTP/HTTPS) and does not support generic TCP listeners required for the MQTT protocol. Therefore, it is unsuitable for this workload.

D. Amazon CloudFront is a content delivery network (CDN) optimized for caching and delivering web content (HTTP/S). It is not the appropriate service for routing stateful, non-HTTP TCP traffic like MQTT.

1. AWS Global Accelerator Documentation, "Bring your own IP addresses (BYOIP) in AWS Global Accelerator": "You can bring part or all of your public IPv4 address range from your on-premises network to your AWS account. You can continue to access these addresses, in your AWS account, with AWS Global Accelerator." This supports the use of BYOIP with Global Accelerator to meet the no-reconfiguration requirement.

2. AWS Global Accelerator Documentation, "How AWS Global Accelerator works": "Global Accelerator uses the vast, congestion-free AWS global network to route TCP and UDP traffic to a healthy application endpoint in the closest AWS Region to your user. If there's an application failure, Global Accelerator provides instant failover to the next best endpoint." This confirms its role in reducing latency for global traffic.

3. AWS Elastic Load Balancing Documentation, "User Guide for Network Load Balancers", Section: "Network Load Balancers": "A Network Load Balancer functions at the fourth layer of the Open Systems Interconnection (OSI) model. It can handle millions of requests per second. After the load balancer receives a connection request, it selects a target from the target group for the default rule. It attempts to open a TCP connection to the selected target on the port specified in the listener configuration." This confirms the NLB's suitability for TCP-based protocols like MQTT.

4. AWS Elastic Load Balancing Documentation, "User Guide for Application Load Balancers", Section: "Listeners for your Application Load Balancer": "An Application Load Balancer supports the following protocols: HTTP, HTTPS, and gRPC." This confirms that an ALB does not support the generic TCP protocol required for MQTT.