What should a SysOps administrator do to meet these requirements?
In each new Region, create a new Elastic Load Balancer and a new set of EC2 instances to run a copy of the application. Transition to a geolocation routing policy.
In each new Region, create a copy of the application on new EC2 instances. Add these new EC2 instances to the Elastic Load Balancer in eu-west-2. Transition to a latency routing policy.
In each new Region, create a copy of the application on new EC2 instances. Add these new EC2 instances to the Elastic Load Balancer in eu-west-2. Transition to a multivalue routing policy.
In each new Region, create a new Elastic Load Balancer and a new set of EC2 instances to run a copy of the application. Transition to a latency routing policy.
Explanations:
While creating a new Elastic Load Balancer and EC2 instances in each new region is necessary, transitioning to a geolocation routing policy does not ensure that users are directed to the region with the fastest response time. Geolocation routing directs users based on their geographic location rather than latency.
Adding new EC2 instances in different regions to the existing Elastic Load Balancer in eu-west-2 does not utilize the benefits of having regional ELBs. Furthermore, a latency routing policy is required to direct users to the region with the fastest response time, which is not achievable with instances centralized in one region.
Similar to option B, adding instances to the existing ELB in eu-west-2 does not optimize performance based on latency across regions. Moreover, a multivalue routing policy is typically used for failover rather than directing users based on the fastest response time.
This option correctly involves creating new Elastic Load Balancers and EC2 instances in each region. Transitioning to a latency routing policy allows Route 53 to direct users to the region with the lowest latency, ensuring optimal response times for the web application.