A company operates a web portal that delivers global breaking news, local alerts, and weather updates. Each user receives a personalized view composed of static and dynamic content. Content is served over HTTPS through an API server on an Amazon EC2 instance behind an Application Load Balancer (ALB). The company wants to deliver this content to users worldwide with the LEAST latency. How should a solutions architect design the application to minimize latency for all users?

The correct option minimizes latency for global users by leveraging Amazon CloudFront, a content delivery network (CDN). CloudFront caches both static and dynamic content at edge locations worldwide, closer to users, reducing the physical distance data must travel. Specifying the ALB as an origin allows CloudFront to fetch dynamic content from the application server when not cached, still benefiting from CloudFront's optimized network path. Deploying in a single region simplifies management and cost compared to multi-region deployments, while CloudFront handles global distribution. Incorrect options: Deploying in two regions with Route 53 latency routing adds complexity and cost without fully optimizing content delivery at the edge for both static and dynamic content like CloudFront does. Serving static content via CloudFront and dynamic content directly from the ALB means dynamic content misses the latency benefits of CloudFront's edge network. Deploying in two regions with Route 53 geolocation routing also adds complexity and cost, and while it directs users to a closer region, it doesn't provide the same edge caching and network optimization as CloudFront for all content types.