Cost-Optimized Static Website Hosting with S3 and CloudFront
Short answer
A Move the website to an Amazon S3 bucket. Configure an Amazon CloudFront distribution for the S3 bucket.
Question
Key Takeaways
This question tests the cost-effective delivery of static assets; the common trap is over-engineering with ElastiCache or Amplify when S3 + CloudFront is the standard low-cost pattern.
Host static website content on Amazon S3 and use Amazon CloudFront to minimize costs while handling increasing traffic, avoiding expensive compute or caching layers.
Common mistake: Many learners choose ElastiCache (B) believing it handles traffic spikes, but ElastiCache is for dynamic application caching, not static file hosting, and adds significant cost and complexity.
Expert Analysis
Why the Answer Is Correct
Moving static content to Amazon S3 provides durable, low-cost storage, while Amazon CloudFront serves as a global Content Delivery Network (CDN). CloudFront caches content at edge locations, reducing latency for users and minimizing data transfer costs compared to serving directly from EC2 or S3 origin without caching. This combination is the industry standard for cost-optimized static website hosting.
Why the Other Options Are Wrong
Option B suggests using ElastiCache, which is an in-memory caching service designed for dynamic databases or applications, not for hosting static files. It incurs hourly instance costs and adds unnecessary complexity. Option C and D involve AWS Amplify, which is a developer platform for full-stack apps, not a simple static host, and adding ALBs or EC2 instances contradicts the goal of minimizing costs.
Community Comment Notes
The community overwhelmingly supports A, noting that "CloudFront helps reduce costs" by leveraging its CDN capabilities. Users correctly point out that ElastiCache is inappropriate for static content, as one commenter noted, "ElastiCache is for DB, not for S3." Another user emphasized that "S3 and CloudFront is straightforward and simple," aligning with the exam's focus on best practices.
Official Reference
This link opens the official vendor documentation in a new tab.
Exam Strategy
Always look for keywords like 'static content' and 'minimize costs.' The default architectural choice for this scenario is S3 for storage and CloudFront for distribution/delivery. Avoid solutions involving compute (EC2) or complex caching layers (ElastiCache) unless explicitly required for dynamic behavior.
Frequently Asked Questions
Why not use ElastiCache for static content?
Does CloudFront reduce S3 costs?
Community Votes
80% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 10 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 10
-
Scheldon 👍 9 Answered AAnswer A Based on https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/getting-started-secure-static-website-cloudformation-template.html Amazon CloudFront: Uses the durable storage of Amazon Simple Storage Service (Amazon S3) – This solution creates an Amazon S3 bucket to host your static website’s content. To update your website, just upload your new files to the S3 bucket.
-
FrozenCarrot 👍 3 Answered BS3 for static contents, and ElastiCache for traffic increasing. No need for cloudfront cuz there is no need for global deliver for the website
-
muhammadahmer36 👍 3 Answered AA. Move the website to an Amazon S3 bucket. Configure an Amazon CloudFront distribution for the S3 bucket.
-
j21kjf0o9ijhj 👍 2 Answered AWhy??? Guys, you'll fail the others. Don't troll or believe everything chatgpt says... 😕 The question indicates "The website serves static content", why would you use elasticache for it? It may work, but it'll take a helluva effort. S3 and CloudFront is straightforward and simple. Not only that, it also works great for static content. It's AWS's cdn. It can also serve dynamic content, but that's out of scope for this question. https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/getting-started-secure-static-website-cloudformation-template.html
-
Dantecito 👍 1 Answered AI don't think anyone has mentioned it, but cloudfront helps reduce costs. If you want to use ElastiCache, it is possible but incredibly difficult, the question asks to reduce costs and cloudfront is cheaper than ElastiCache.
Show 5 more comments
-
Abdullah2004 👍 1 Answered Bwebsite serves static content So we need to ElastiCache when traffic increases , no need for cloudfront
-
mk168898 👍 1 Answered BS3 bucket is correct, so it's between A or B. B because cache to handle when traffic increase.
-
Cpso 👍 1 Answered AA. but questions should specify it is static or dynamic website
-
joanna91 👍 1 Answered AA vs B -> A. Because Elsticache is for DB, not for S3.
-
trinh_le 👍 3 Answered Astatic content -> S3
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All SAA-C03 Questions
Access 120 questions with complete answers and detailed explanations.
View Full SAA-C03 Practice Test →