Match each requirement to the AWS service or feature that meets it best.
Match each item to the right option.
- 1. Route HTTP requests to different target groups based on the URL path
- 2. Handle millions of TCP connections per second with a static IP address in each Availability Zone
- 3. Insert third-party firewall appliances transparently into the network traffic path
- 4. Send each user to the AWS Region that gives them the lowest network latency, using DNS
Options: Application Load Balancer, Network Load Balancer, Gateway Load Balancer, Amazon Route 53 latency-based routing, Amazon CloudFront.
Show answer and explanation
Correct matches
- Route HTTP requests to different target groups based on the URL path: Application Load Balancer
- Handle millions of TCP connections per second with a static IP address in each Availability Zone: Network Load Balancer
- Insert third-party firewall appliances transparently into the network traffic path: Gateway Load Balancer
- Send each user to the AWS Region that gives them the lowest network latency, using DNS: Amazon Route 53 latency-based routing
An Application Load Balancer operates at layer 7, so it can route on what the request contains — paths, host names, headers — which is exactly what path-based routing needs. A Network Load Balancer works at layer 4 and is built for very high connection rates, with a static IP address in each Availability Zone. A Gateway Load Balancer sits transparently in the traffic path using GENEVE, deploying and scaling third-party virtual appliances such as firewalls. Route 53 latency-based routing answers each DNS query with the Region that has the lowest measured latency from the user's location.
CloudFront also brings users closer to content, but it's a CDN that caches at edge locations — it isn't the tool for any of these four requirements.