A global company hosts a web application on Amazon EC2 instances behind an Application Load Balancer (ALB). Static content is stored in an Amazon S3 bucket and the application serves dynamic content from the ALB. The company wants to reduce latency and improve performance for both static and dynamic content, using its own domain name registered in Amazon Route 53. What should a solutions architect implement?

The correct solution is to create a CloudFront distribution with multiple origins: the S3 bucket for static content and the ALB for dynamic content. CloudFront is a Content Delivery Network (CDN) that caches content at edge locations globally, significantly reducing latency for both static and dynamic content by serving it closer to users. Route 53 can then be configured to point the domain name to the CloudFront distribution, ensuring all traffic benefits from the CDN. Incorrect options: Using Global Accelerator for S3 is unnecessary as CloudFront already provides global caching for S3. Global Accelerator is primarily for improving performance of TCP/UDP applications over the AWS global network, not typically for serving static content directly from S3 or as a primary CDN for HTTP/HTTPS content when CloudFront is a better fit. Splitting static and dynamic content across different top-level endpoints (CloudFront and Global Accelerator) would complicate domain management and potentially negate some of the benefits of a unified CDN.