ANS-C01 practice question 4 of 35

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

Full set: 291 questions
An IoT company sells hardware sensor modules that periodically send out temperature, humidity, pressure, and location data through the MQTT messaging protocol. The hardware sensor modules send this data to the company's on-premises MQTT brokers that run on Linux servers behind a load balancer. The hardware sensor modules have been hardcoded with public IP addresses to reach the brokers. The company is growing and is acquiring customers across the world. The existing solution can no longer scale and is introducing additional latency because of the company's global presence. As a result, the company decides to migrate its entire infrastructure from on premises to the AWS Cloud. The company needs to migrate without reconfiguring the hardware sensor modules that are already deployed across the world. The solution also must minimize latency. The company migrates the MQTT brokers to run on Amazon EC2 instances. What should the company do next to meet these requirements?
Answer options
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 NLUse Bring Your Own IP (BYOIP) from the on- premises network with Global Accelerator. Correct answer
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.
Correct Answer:
B. Place the EC2 instances behind a Network Load Balancer (NLB). Configure TCP listeners. Create an AWS Global Accelerator accelerator in front of the NLUse Bring Your Own IP (BYOIP) from the on- premises network with Global Accelerator.
Explanation

This solution addresses all requirements. A Network Load Balancer (NLB) operates at Layer 4 (TCP/UDP) and is suitable for forwarding MQTT traffic to the EC2 instances. AWS Global Accelerator provides static IP addresses and uses the AWS global network to route traffic from users to the optimal AWS endpoint, minimizing latency for a global customer base. The Bring Your Own IP (BYOIP) feature allows the company to use its existing on-premises public IP addresses with Global Accelerator. This is critical because it avoids the need to reconfigure the hardcoded hardware sensor modules.

Why Incorrect

A. Using only an NLB with BYOIP would create a single-region endpoint, failing to provide the low-latency global routing required for customers across the world.
C. An Application Load Balancer (ALB) operates at Layer 7 and is designed for HTTP/S traffic; it is not suitable for a generic TCP protocol like MQTT.
D. Amazon CloudFront is a content delivery network (CDN) optimized for caching web content (HTTP/S), not for persistent, bi-directional TCP connections required by MQTT.

References

1. AWS Documentation, "Bring your own IP addresses (BYOIP) in AWS Global Accelerator". It states, "BYOIP lets you use your own public IPv4 addresses with Global Accelerator... You can continue to use IP addresses that are known to your customers' client applications."

2. AWS Documentation, "How AWS Global Accelerator works". It explains that Global Accelerator directs traffic to the "optimal endpoint based on performance, routing traffic over the congestion-free and redundant AWS global network."

3. AWS Documentation, "Listeners for your Network Load Balancer". It confirms that NLBs support TCP listeners, which are required for the MQTT protocol.

4. AWS Documentation, "Endpoints in AWS Global Accelerator". This page lists Network Load Balancers as a supported endpoint type for a Global Accelerator standard accelerator.

Scroll to Top