What should a solutions architect do to meet these requirements?
Redesign the application to use Amazon CloudFront.
Redesign the application to use AWS Elastic Beanstalk.
Redesign the application to use a Network Load Balancer.
Redesign the application to use Amazon S3 static website hosting.
Explanations:
Amazon CloudFront is a Content Delivery Network (CDN) that caches static and dynamic content at edge locations around the world, ensuring low latency and high availability for global users. It integrates well with AWS resources like ALB and EC2 instances, improving the user experience for a global audience.
AWS Elastic Beanstalk is a platform-as-a-service (PaaS) solution that automates application deployment. While it simplifies management, it does not directly address the global distribution and performance optimization needs of users, unlike CloudFront.
A Network Load Balancer (NLB) is designed for handling high-throughput and low-latency traffic at the network layer (Layer 4). While it can improve performance for specific use cases, it does not provide the global caching and distribution benefits that CloudFront offers.
Amazon S3 static website hosting is suitable for static content, but it doesn’t work well with dynamic content or custom SSL certificates, which the application likely needs for its product information pages. Also, it doesn’t offer the global caching and low-latency benefits provided by CloudFront.
From what I’ve heard, the answer is:
Redesign the application to use Amazon CloudFront.