Which solution meets these requirements?
Create a web distribution on Amazon CloudFront to serve the S3 content for the application. Create a CNAME record in a Route 53 hosted zone that points to the CloudFront distribution, resolving to the application’s URL domain name.
Create a web distribution on Amazon CloudFront to serve the S3 content for the application. Create an ALIAS record in the Amazon Route 53 hosted zone that points to the CloudFront distribution, resolving to the application’s URL domain name.
Create an A record in a Route 53 hosted zone for the application. Create a Route 53 traffic policy for the web application, and configure a geolocation rule. Configure health checks to check the health of the endpoint and route DNS queries to other endpoints if an endpoint is unhealthy.
Create an A record in a Route 53 hosted zone for the application. Create a Route 53 traffic policy for the web application, and configure a geoproximity rule. Configure health checks to check the health of the endpoint and route DNS queries to other endpoints if an endpoint is unhealthy.
Explanations:
A CNAME record cannot be used for the root domain, and thus, it is not suitable for resolving the application’s URL domain name. An ALIAS record is preferred for root domains in Route 53, as it allows for the use of CloudFront distributions.
Creating a web distribution on CloudFront to serve the S3 content reduces latency for users globally and consolidates contracts by centralizing the delivery method. An ALIAS record in Route 53 allows for proper resolution of the root domain name to the CloudFront distribution.
While an A record could work, it does not optimize content delivery from S3. Traffic policies based on geolocation may not effectively reduce latency for a global audience as CloudFront would. Additionally, this approach does not leverage the benefits of caching and reduced latency provided by CloudFront.
Similar to option C, while an A record and traffic policy could be implemented, it does not utilize CloudFront for content delivery, which is crucial for reducing latency and costs. The geoproximity rule may improve performance for some users, but it does not optimize the delivery as effectively as CloudFront does.
I map out that the answer is:
Create a web distribution on Amazon CloudFront to serve the S3 content for the application. Create an ALIAS record in the Amazon Route 53 hosted zone that points to the CloudFront distribution, resolving to the application’s URL domain name.