SAA-C03 · Question #360
A company hosts a website on Amazon EC2 instances behind an Application Load Balancer (ALB). The website serves static content. Website traffic is increasing. The company wants to minimize the…
The correct answer is A. Move the website to an Amazon S3 bucket. Configure an Amazon CloudFront distribution for the. Serving static content from Amazon S3 is highly cost-effective and scalable. By fronting the S3 bucket with Amazon CloudFront, you also enable global caching, reduced latency, and even lower costs by reducing direct S3 access. There is no need for EC2 or ALB, and no need to…
Question
A company hosts a website on Amazon EC2 instances behind an Application Load Balancer (ALB). The website serves static content. Website traffic is increasing. The company wants to minimize the website hosting costs. Which solution will meet these requirements?
Options
- AMove the website to an Amazon S3 bucket. Configure an Amazon CloudFront distribution for the
- BMove the website to an Amazon S3 bucket. Configure an Amazon ElastiCache cluster for the S3
- CMove the website to AWS Amplify. Configure an ALB to resolve to the Amplify website.
- DMove the website to AWS Amplify. Configure EC2 instances to cache the website.
How the community answered
(23 responses)- A91% (21)
- B4% (1)
- D4% (1)
Explanation
Serving static content from Amazon S3 is highly cost-effective and scalable. By fronting the S3 bucket with Amazon CloudFront, you also enable global caching, reduced latency, and even lower costs by reducing direct S3 access. There is no need for EC2 or ALB, and no need to manage servers, further lowering operational burden and expenses. This pattern is the recommended AWS architecture for serving static web content.
Community Discussion
No community discussion yet for this question.