A company hosts a three-tier ecommerce application in AWS. The website is hosted on Amazon S3 and integrates with an API on three Amazon EC2 instances behind an Application Load Balancer (ALB). The API serves static and dynamic front-end content and backend workers that process sales requests asynchronously. The company expects sudden large spikes in sales requests during product launches. What should a solutions architect recommend to ensure all requests are processed successfully?

The correct solution addresses both content delivery and request processing during spikes. CloudFront for static content improves performance and reduces load on the EC2 instances by caching frequently accessed data closer to users. An SQS queue decouples the request submission from the processing, allowing the application to gracefully handle sudden spikes. Requests are added to the queue and processed by the EC2 instances at their own pace, preventing overload and ensuring no sales requests are lost. Incorrect options: Adding CloudFront for dynamic content is less effective than for static content, as dynamic content changes frequently. Increasing EC2 instances alone might not prevent overload during sudden, extreme spikes if the processing bottleneck is not addressed. Placing EC2 instances in an Auto Scaling group is good for scaling but doesn't fully protect against sudden, massive