An ecommerce company is preparing to deploy a web application on AWS to ensure continuous service for customers. The architecture includes a web application that the company hosts on Amazon EC2…

Question

Options

• ADeploy Amazon EC2 instances in a single Availability Zone. Deploy an RDS DB instance in the
• BDeploy Amazon EC2 instances in an Auto Scaling group across multiple Availability Zones.
• CDeploy Amazon EC2 instances in a single Availability Zone. Deploy an RDS DB instance in a
• DUse AWS Lambda functions to serve the web application. Use Amazon Aurora Serverless v2 for

• A
  4% (2)
• B
  87% (48)
• C
  7% (4)
• D
  2% (1)

Explanation

AWS Well-Architected recommends multi-AZ, elastic architectures: use Auto Scaling groups across multiple Availability Zones for EC2 to eliminate single-AZ failure and automatically replace capacity. For relational databases, Amazon RDS Multi-AZ provides synchronous replication and automatic failover for high availability. Serving static content via Amazon CloudFront (with S3 origin) improves resiliency and performance by caching at edge locations and reducing origin load/latency. Options A and C concentrate compute in one AZ and lack resilient static delivery. Option D changes the stack unnecessarily and proposes EFS One Zone-IA for static assets, which is not multi-AZ and is intended for infrequently accessed, single-AZ workloads, reducing resilience. Therefore, B aligns with best practices for high availability, fault tolerance, and global

No community discussion yet for this question.