What should a solutions architect do to meet these requirements?
Create an Amazon CloudFront distribution that has the S3 bucket and the ALB as origins. Configure Route 53 to route traffic to the CloudFront distribution.
Create an Amazon CloudFront distribution that has the ALB as an origin. Create an AWS Global Accelerator standard accelerator that has the S3 bucket as an endpoint Configure Route 53 to route traffic to the CloudFront distribution.
Create an Amazon CloudFront distribution that has the S3 bucket as an origin. Create an AWS Global Accelerator standard accelerator that has the ALB and the CloudFront distribution as endpoints. Create a custom domain name that points to the accelerator DNS name. Use the custom domain name as an endpoint for the web application.
Create an Amazon CloudFront distribution that has the ALB as an origin. Create an AWS Global Accelerator standard accelerator that has the S3 bucket as an endpoint. Create two domain names. Point one domain name to the CloudFront DNS name for dynamic content. Point the other domain name to the accelerator DNS name for static content. Use the domain names as endpoints for the web application.
Explanations:
Using CloudFront to cache both static data from the S3 bucket and dynamic data from the ALB reduces latency and improves performance. Route 53 can route traffic to the CloudFront distribution, ensuring efficient content delivery.
This option incorrectly suggests using Global Accelerator for the S3 bucket. Global Accelerator is more suited for improving latency for TCP/UDP traffic, but CloudFront alone can handle both static and dynamic content effectively.
While it correctly uses CloudFront for the S3 bucket, adding Global Accelerator with both ALB and CloudFront as endpoints complicates the architecture unnecessarily. CloudFront alone suffices for performance improvement.
This option overcomplicates the solution by using two domain names and Global Accelerator. It fails to leverage CloudFront effectively, which can handle both static and dynamic content in a single distribution.
Based on what I know, the answer is:
Create an Amazon CloudFront distribution that has the S3 bucket and the ALB as origins. Configure Route 53 to route traffic to the CloudFront distribution.
I organize that the answer is:
Create an Amazon CloudFront distribution that has the S3 bucket and the ALB as origins. Configure Route 53 to route traffic to the CloudFront distribution.