An online magazine is launching its first global edition and expects a large spike in traffic. Current architecture: ALB, EC2 web/app servers, and Amazon Aurora MySQL; much of the site is read-heavy and some static content exists. Performance for a global audience is the top priority for the week after launch. Which combination of actions should a solutions architect take to reduce response times globally? (Choose two.)

The correct options address global performance for a read-heavy site with static content. An Aurora global database provides fast, low-latency global reads by physically replicating data across regions, which is crucial for a global audience. Deploying web and application tiers worldwide, combined with Amazon Route 53's latency-based routing, directs users to the closest healthy endpoint, minimizing network latency. Amazon S3 with cross-Region replication efficiently stores and serves static content globally. Amazon CloudFront distributions cache content at edge locations, further reducing latency for both dynamic and static content. Auto Scaling groups ensure the application can handle traffic spikes. Incorrect options: Logical cross-Region replication for Aurora is slower than a global database. Replacing web servers with S3 is not feasible for a dynamic application. Direct Connect improves connectivity between on-premises and AWS, not global user-to-application latency. Migrating from Aurora to RDS for MySQL is a downgrade in performance and scalability for this use case. Placing all tiers in private subnets is a security measure, not a performance enhancement for global access.