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 cross-Region replication for static content using S3 is beneficial, replacing web servers with S3 is not appropriate as S3 cannot serve dynamic content. Additionally, Aurora MySQL does not support logical replication to a secondary Region effectively for a global audience.
Auto Scaling groups are useful for managing traffic spikes, but introducing AWS Direct Connect is unnecessary for a public-facing application. Deploying across multiple Regions could help, but without proper database replication and content delivery strategies, it won’t optimally reduce response times.
Migrating from Amazon Aurora to RDS for MySQL does not enhance performance or reduce response times. Keeping application tiers in private subnets can also hinder access and performance for a global audience.
Using an Aurora global database provides efficient cross-Region replication for the database, and S3 with cross-Region replication effectively serves static content. This approach, combined with deploying web and application tiers in multiple Regions, optimizes performance for a global audience.
Implementing Amazon Route 53 with latency-based routing ensures users are directed to the nearest resource, reducing latency. Using Amazon CloudFront as a CDN accelerates the delivery of static content. Auto Scaling groups help handle traffic surges effectively, ensuring optimal performance.