Which Route 53 configuration should a solutions architect use to provide the MOST high-performing experience?
Create an A record with a latency policy.
Create an A record with a geolocation policy.
Create a CNAME record with a failover policy.
Create a CNAME record with a geoproximity policy.
Explanations:
An A record with a latency policy directs traffic to the Region with the lowest latency for the user, providing the most responsive experience by reducing delay. This is optimal for performance as it dynamically adjusts based on real-time latency measurements.
A geolocation policy routes traffic based on the geographic location of the user, which may not necessarily provide the lowest latency. While it can improve performance for users in specific regions, it lacks the adaptability of latency-based routing.
A CNAME record with a failover policy is designed to route traffic to a primary site and automatically switch to a secondary site if the primary fails. This setup is more focused on availability than performance, making it less suitable for optimizing user experience based on latency.
A CNAME record with a geoproximity policy allows routing based on geographic distance, which can improve performance for users closer to a Region. However, it does not take real-time latency into account, making it less effective than a latency-based policy for performance optimization.