Which solution will meet these requirements?
Add a new value to the existing alias record for app.anycompany.com with the DNS name of the new ALB in ap-southeast-2.
Change the existing alias record to use a geolocation routing policy. Create two geolocation records, one record that references each ALSelect the location that is closest to each Region.
Change the existing alias record to use a latency routing policy. Create two latency records, one record that references each ALB.
Change the existing alias record to use a multivalue routing policy Add the DNS name of each ALB to the record.
Explanations:
Adding a new value to the alias record will not automatically route users to the lowest latency endpoint. Route 53 does not support automatic latency-based routing with multiple ALBs in different regions using a simple routing policy.
A geolocation routing policy is not suitable for automatically routing users to the lowest latency endpoint. It routes users based on their geographical location, not based on latency performance.
A latency routing policy automatically directs users to the endpoint with the lowest latency, which is the desired solution in this scenario. Route 53 will route traffic to the ALB with the lowest latency for the user, either in us-west-2 or ap-southeast-2.
A multivalue routing policy does not route based on latency. It simply returns multiple records for DNS queries, and while it can distribute traffic across multiple endpoints, it does not ensure routing to the lowest latency endpoint.
In my experience, the answer is:
Change the existing alias record to use a latency routing policy. Create two latency records, one record that references each ALB.