A company currently hosts a simple web app on EC2 instances behind a load balancer in eu-west-2 and uses a Route 53 simple routing record. They plan to create additional, identical deployments in us-east-1 and ap-south-1 and want users routed to the region that yields the fastest response time. What should the SysOps administrator do?

The correct approach is to deploy a load balancer and EC2 instances in each new region and change the Route 53 record to use latency routing. Latency-based routing directs users to the AWS region that provides the lowest latency, ensuring the fastest response time, which directly addresses the requirement. Each region needs its own load balancer to distribute traffic efficiently to its local EC2 instances. Incorrect options: Geolocation routing directs users based on their geographic location, not necessarily the fastest response time. While it can be useful, it doesn't guarantee the lowest latency. Adding EC2 instances from other regions to a single load balancer in eu-west-2 is not feasible or efficient. Load balancers are typically regional and designed to distribute traffic within their own region. This would also introduce significant cross-region latency. Multivalue routing returns multiple healthy records to the user, allowing the client to choose. This doesn't guarantee the lowest latency and still requires separate regional deployments and load balancers for optimal performance.