An ecommerce company will deploy a web application on AWS: EC2 for the web app, Amazon RDS for the relational database, and Amazon S3 for static assets. The company wants a robust, resilient architecture. Which solution meets these requirements?

The correct solution ensures high availability and resilience. Deploying EC2 instances across multiple Availability Zones with an Auto Scaling group protects against single AZ failures and scales capacity automatically. A Multi-AZ RDS DB instance provides automatic failover to a standby replica in another AZ, ensuring database availability. Using Amazon CloudFront to distribute static assets from S3 improves performance by caching content closer to users and enhances resilience by leveraging CloudFront's global network. The other options are less robust: Deploying EC2 and RDS in a single AZ creates a single point of failure. Deploying EC2 in a single AZ with cross-AZ RDS is better for the database but leaves the application vulnerable. Serving static assets directly from EC2 instances is inefficient and lacks resilience. While Lambda and Aurora Serverless are scalable, storing static assets in EFS One Zone-IA is not ideal for web serving due to potential latency and lack of global distribution compared to S3/CloudFront.