AWS Certified Solutions Architect - Associate
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
An ecommerce company wants to launch a one-deal-a-day website on AWS. Each day will feature exactly one product on sale for a period of 24 hours. The company wants to be able to handle millions of requests each hour with millisecond latency during peak hours.
Which solution will meet these requirements with the LEAST operational overhead?
Other
Community
UAnonymous
A
Use Amazon S3 to host the full website in different S3 buckets. Add Amazon CloudFront distributions. Set the S3 buckets as origins for the distributions. Store the order data in Amazon S3.
B
Deploy the full website on Amazon EC2 instances that run in Auto Scaling groups across multiple Availability Zones. Add an Application Load Balancer (ALB) to distribute the website traffic. Add another ALB for the backend APIs. Store the data in Amazon RDS for MySQL.
C
Migrate the full application to run in containers. Host the containers on Amazon Elastic Kubernetes Service (Amazon EKS). Use the Kubernetes Cluster Autoscaler to increase and decrease the number of pods to process bursts in traffic. Store the data in Amazon RDS for MySQL.
D
Use an Amazon S3 bucket to host the website's static content. Deploy an Amazon CloudFront distribution. Set the S3 bucket as the origin. Use Amazon API Gateway and AWS Lambda functions for the backend APIs. Store the data in Amazon DynamoDB.
Explanation:
Explanation
Option D is the correct answer because it provides the LEAST operational overhead while meeting all requirements:
Why Option D is best:
- Serverless architecture - Uses S3, CloudFront, API Gateway, Lambda, and DynamoDB which are all fully managed services with minimal operational overhead.
- High scalability - Can handle millions of requests per hour with millisecond latency:
- CloudFront provides global edge caching
- Lambda automatically scales to handle traffic spikes
- DynamoDB provides single-digit millisecond latency at any scale
- Cost-effective - Pay only for what you use with serverless services
- Low maintenance - No servers to manage, patch, or scale
Why other options are not optimal:
Option A: Storing order data in S3 is inappropriate for transactional data. S3 is for object storage, not for database operations with ACID properties.
Option B: EC2-based solution requires significant operational overhead - managing Auto Scaling groups, patching OS, monitoring instances, managing RDS databases.
Option C: EKS/Kubernetes requires even more operational overhead than EC2 - managing container orchestration, cluster scaling, pod management, etc.
Key architectural benefits of Option D:
- Static content served from S3 + CloudFront for maximum performance
- Dynamic backend via API Gateway + Lambda for serverless compute
- Database using DynamoDB for millisecond latency at scale
- Automatic scaling with no operational intervention needed
- Global distribution via CloudFront edge locations
This architecture perfectly matches the "one-deal-a-day" use case where traffic can spike dramatically during peak hours, requiring automatic scaling with minimal operational effort.
Comments
Loading comments...