Which combination of steps should a solutions architect take to reduce system response times for a global audience?
(Choose two.)
Use logical cross-Region replication to replicate the Aurora MySQL database to a secondary Region. Replace the web servers with Amazon S3. Deploy S3 buckets in cross-Region replication mode.
Ensure the web and application tiers are each in Auto Scaling groups. Introduce an AWS Direct Connect connection. Deploy the web and application tiers in Regions across the world.
Migrate the database from Amazon Aurora to Amazon RDS for MySQL. Ensure all three of the application tiers ג€” web, application, and database ג€” are in private subnets.
Use an Aurora global database for physical cross-Region replication. Use Amazon S3 with cross-Region replication for static content and resources. Deploy the web and application tiers in Regions across the world.
Introduce Amazon Route 53 with latency-based routing and Amazon CloudFront distributions. Ensure the web and application tiers are each in Auto Scaling groups.
Explanations:
While using Amazon S3 for static content is beneficial for reducing load on web servers, using logical cross-Region replication for Aurora MySQL is not optimal for performance. S3 buckets cannot replace web servers for dynamic content, and cross-Region replication would introduce latency.
Auto Scaling groups help manage traffic spikes, but introducing AWS Direct Connect is not relevant for reducing response times for global users. Deploying in multiple Regions is beneficial, but the focus on network connectivity is misplaced in this context.
Migrating to Amazon RDS for MySQL does not inherently improve performance compared to Aurora. Placing all tiers in private subnets may restrict accessibility and is not related to reducing response times for a global audience.
Using an Aurora global database allows for low-latency cross-Region replication, enhancing performance for global access. Deploying static content in S3 with cross-Region replication further reduces latency for users accessing these resources.
Amazon Route 53 with latency-based routing directs users to the closest available Region, improving response times. Amazon CloudFront caches static content closer to users, and Auto Scaling groups ensure adequate resources during traffic spikes, contributing to overall performance.