A company is creating a new recipe blog sharing application in AWS. The static content has been put into an S3 bucket. In the meantime, a database is needed to store the data for various blog posts. The application retrieves data from the database and dynamically renders a recipe blog page.

Answer options:

A.Configure an elastic load balancer and Auto Scaling group to balance the traffic dynamically.
B.Configure an AWS CloudFront to serve end users from various Edge Locations.
C.Create an Auto Scaling configuration for EC2 instances to automatically scale up and down according to the load.
D.Run the application code in Lambda@Edge to retrieve data from the database, and the response is also cached and served by CloudFront.
E.Use DynamoDB to store data for blog posts that the application is using.
F.For the dynamic data including blog posts for customers, configure an RDS instance as the database.

Correct Answer – B, D, E
The main requirement for this question is that no extra efforts are needed for origin infrastructure, automatic scaling, backups, and database redundancy. Proper AWS services should be chosen to align with this rule. Hence, options having EC2 with ELB and Auto Scaling can be safely eliminated.
Option A is incorrect: Because ELB and Auto Scaling do not help to route traffic to users globally.
Option B is CORRECT: Because CloudFront has over 100 Edge Locations and is a proper CDN to deliver content to end-users with lower latency globally.
Option C is incorrect: Same reason as
Option A as EC2 is eliminated.
Option D is CORRECT: Because Lambda@Edge can work together with CloudFront to build dynamic web applications that automatically scale up and down. There is also no need to build up servers to hold the application code.
Option E is CORRECT: Because DynamoDB database is a fully managed and high-performance database. DynamoDB automatically scales tables to adjust for capacity and maintain performance.
Option F is incorrect: RDS needs Read Replica and Multi-AZ to be scalable, which brings extra efforts. There is also no need to use a relational database for this case. Option E (DynamoDB) is better and is a pure serverless solution together with other valid options.