AWS Certified Solutions Architect – Associate (SAA-C03) — Question 929
A global ecommerce company uses a monolithic architecture. The company needs a solution to manage the increasing volume of product data. The solution must be scalable and have a modular service architecture. The company needs to maintain its structured database schemas. The company also needs a storage solution to store product data and product images.
Which solution will meet these requirements with the LEAST operational overhead?
Answer options
- A. Use an Amazon EC2 instance in an Auto Scaling group to deploy a containerized application. Use an Application Load Balancer to distribute web traffic. Use an Amazon RDS DB instance to store product data and product images.
- B. Use AWS Lambda functions to manage the existing monolithic application. Use Amazon DynamoDB to store product data and product images. Use Amazon Simple Notification Service (Amazon SNS) for event-driven communication between the Lambda functions.
- C. Use Amazon Elastic Kubernetes Service (Amazon EKS) with an Amazon EC2 deployment to deploy a containerized application. Use an Amazon Aurora cluster to store the product data. Use AWS Step Functions to manage workflows. Store the product images in Amazon S3 Glacier Deep Archive.
- D. Use Amazon Elastic Container Service (Amazon ECS) with AWS Fargate to deploy a containerized application. Use Amazon RDS with a Multi-AZ deployment to store the product data. Store the product images in an Amazon S3 bucket.
Correct answer: D
Explanation
Amazon ECS with AWS Fargate provides a serverless container environment that minimizes server management, while Amazon RDS Multi-AZ maintains structured relational schemas with high availability, and Amazon S3 offers highly durable, low-overhead object storage for images. Option A is incorrect because storing images directly inside an RDS database is a poor architectural practice and managing EC2 instances increases operational overhead. Option B uses DynamoDB, which is a NoSQL database that does not fit the structured relational requirement, and Option C introduces unnecessary operational complexity with EKS while incorrectly using Glacier Deep Archive for active, frequently accessed product images.