A company hosts a high-frequency flash sale application on a fleet of Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB). The application data is stored in an Amazon RDS for MySQL Multi-AZ DB instance. During scheduled weekly flash sales, traffic surges instantly by within two minutes. During these peaks, users experience HTTP 503 Service Unavailable errors, and database read response times increase significantly. A Solutions Architect needs to optimize both compute and storage performance to handle the next flash sale without service degradation.
Which combination of actions should the Solutions Architect take to address these performance issues? (Select TWO.)
- Migrate the database to Amazon Aurora MySQL, deploy Aurora Replicas, and configure Aurora Auto Scaling to dynamically adjust the number of replicas.Cevap
- Request AWS Support to pre-warm the Application Load Balancer to the expected capacity prior to the scheduled flash sales.Cevap
- CConfigure the application to route read queries to the standby replica instance of the Amazon RDS MySQL Multi-AZ deployment during peak traffic.
- DRely on the Application Load Balancer's automatic scaling metrics to dynamically provision capacity during the flash sale traffic spike.
- EDeploy an Amazon ElastiCache for Memcached cluster to act as a persistent database replication target and cache transactional data.
Cevap
Migrate the database to Amazon Aurora MySQL with Aurora Auto Scaling and request AWS Support to pre-warm the Application Load Balancer before the sale.
Pre-warming the Application Load Balancer handles sudden, massive traffic spikes that exceed standard automatic scaling rates. Migrating to Amazon Aurora MySQL allows read workloads to be distributed across multiple Aurora Replicas that scale dynamically with Auto Scaling, resolving the storage bottleneck.
Adım Adım Çözüm
Anahtar Kavram
Optimizing compute scaling limits using ALB pre-warming and database read capacity scaling using Amazon Aurora Replicas.