A company will run an internet-facing application on multiple Amazon EC2 instances across multiple Availability Zones and multiple AWS Regions. Users are worldwide and should be routed to the EC2 instances closest to their location. Which solution meets these requirements?

A geoproximity routing policy in Amazon Route 53 routes users to the nearest AWS Region based on their geographic location, which aligns with the requirement to route users to the closest EC2 instances. A Network Load Balancer (NLB) is chosen over an Application Load Balancer (ALB) because NLBs are designed for extreme performance and static IP addresses, which are often beneficial for internet-facing applications needing high throughput and low latency. Geolocation routing is less flexible than geoproximity, as it routes based on predefined geographic boundaries rather than the actual proximity of the user to the resource. Multivalue answer routing returns multiple healthy records, requiring the client to choose, which isn't ideal for proximity routing. Weighted routing distributes traffic based on weights, not proximity.