Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 116 discussion

A -> We can configure CloudFront to require HTTPS from clients (enhanced security) https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/using-https-viewers-to-cloudfront.html D -> storing static website on S3 provides scalability and less operational overhead, then configuration of Application LB and EC2 instances (hence E is out) B is out since AWS WAF Web ACL does not to provide HTTPS functionality, but to protect HTTPS only.

agree with A and D static website -> obviously S3, and S3 is super scalable CDN -> CloudFront obviously as well, and with HTTPS security is enhanced. B does not make sense because you are not replacing the CDN with anything, E works too but takes too much effort and compared to S3, S3 still wins in term of scalability. plus why use EC2 when you are only hosting static website

A and D is the safest combination.

these answers are the most common use case for real companies, is like the answers that have more sense

Web Application Firewall creates rules to block attacks, but it does not create HTTPS. It can only allow HTTPS inbound traffic.

Scalability, enhanced security and less operational overhead = CloudFront with HTTPS Scalability and less operational overhead = S3 bucket with static website hosting

A. Amazon CloudFront provides scalable content delivery with HTTPS functionality, meeting security and scalability requirements. D. Deploying the website on an Amazon S3 bucket with static website hosting reduces operational overhead by eliminating server maintenance and patching. Why other options are incorrect: B. AWS WAF does not provide HTTPS functionality or address patching and maintenance. C. Using AWS Lambda introduces complexity and does not directly address patching and maintenance. E. Managing EC2 instances and an Application Load Balancer increases operational overhead and does not minimize patching and maintenance tasks. In summary, configuring Amazon CloudFront for HTTPS and deploying on Amazon S3 with static website hosting provide security, scalability, and reduced operational overhead.

AD A for enhanced security D for static content

LEAST operational overhead = Serverless https://aws.amazon.com/serverless/

AD misses the operational part, how can the app work without a lambda function, an EC2 instance or something?

people do not seem to get the LEAST OPERATIONAL OVERHEAD statement, many people keep voting for options that bring far too Op work

A for enhanced security D for static content

Since Amazon S3 is unlimited and you pay as you go so it means there will be no limit to scale as long as your data is going to grow, so D is one of the correct answers and another correct answer is A, because of this: https://docs.aws.amazon.com/AmazonS3/latest/userguide/WebsiteHosting.html so my answer is AD.

I vote A & C for the reason being least operational overhead.

Here a perfect explanation: https://aws.amazon.com/premiumsupport/knowledge-center/cloudfront-serve-static-website/

Simple and secure

D. Create the new website and an Amazon S3 bucket. Deploy the website on the S3 bucket with static website hosting enabled. A. Configure Amazon CloudFront in front of the website to use HTTPS functionality. By deploying the website on an S3 bucket with static website hosting enabled, the company can take advantage of the high scalability and cost-efficiency of S3 while also reducing the operational overhead of managing and patching a CMS. By configuring Amazon CloudFront in front of the website, it will automatically handle the HTTPS functionality, this way the company can have a secure website with very low operational overhead.