A travel agency chain runs an application on two fixed Amazon EC2 instances behind a Route 53 multivalue record that returns the instances' Elastic IPs. The app uses DynamoDB for primary storage and a self-hosted Redis cache. Destination content is updated quarterly; updates spike load and have caused downtime. You must make the app highly available and able to handle the update load. Which solution meets these needs?

The correct solution addresses all requirements. Deploying DAX improves DynamoDB read performance and offloads the database, crucial during content updates. An Auto Scaling group behind an ALB ensures high availability and automatically scales EC2 instances to handle increased load. Scheduled scaling proactively provisions capacity before quarterly content updates, preventing downtime. Updating Route 53 to point to the ALB alias simplifies DNS management and integrates with the scaling solution. The other options are incorrect because: Using CloudFront with the Auto Scaling group as an origin is suitable for static content or caching at the edge, but the application likely serves dynamic content requiring direct access to the ALB. Manual scaling is also insufficient. ElastiCache for Memcached is a valid caching solution, but DAX specifically optimizes DynamoDB reads, which is a primary bottleneck. Combining CloudFront with DAX still suffers from the CloudFront origin issue and manual scaling.