Examkin

Soru

Zorluk: OrtaOptimizing Compute and Storage Performance

A company hosts a read-heavy web application on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB). The application layer is backed by an Amazon RDS for MySQL Multi-AZ DB instance, and the EC2 instances use attached Amazon EBS gp3 volumes to cache static assets. The company expects traffic to spike tenfold in less than 5 minutes due to a promotional event. Which two actions should a solutions architect recommend to optimize compute and storage performance, and ensure the system can handle the sudden surge?

  1. Deploy Amazon RDS Read Replicas and modify the application to route read-heavy database queries to the read replica endpoints.Cevap
  2. Increase the provisioned IOPS and throughput on the existing EBS gp3 volumes to accommodate the higher read-intensive local storage demands.Cevap
  3. C
    Configure the application to route read-heavy database queries to the standby DB instance of the RDS Multi-AZ deployment to balance the query load.
  4. D
    Rely on the Application Load Balancer's default auto-scaling behavior to dynamically allocate compute capacity during the sudden traffic spike.
  5. E
    Purchase EC2 Instance Savings Plans to optimize compute costs for both the scaling EC2 instances and the application's auxiliary AWS Fargate tasks.

Cevap

Deploy Amazon RDS Read Replicas and route read traffic to them, and increase the provisioned IOPS and throughput on the existing EBS gp3 volumes.
Deploying Amazon RDS Read Replicas allows horizontal scaling of the read-heavy database workload, while increasing the provisioned IOPS and throughput on the existing EBS gp3 volumes directly optimizes storage performance without requiring volume resizing or system downtime.

Adım Adım Çözüm

1
Analyze the database workload bottlenecks under a tenfold traffic increase.
Identify that the primary database is a read-heavy RDS MySQL Multi-AZ deployment. Since the standby replica in RDS Multi-AZ cannot serve read traffic, horizontal scaling must be achieved by deploying RDS Read Replicas.
This offloads read operations from the primary DB instance, preventing CPU and memory exhaustion.
2
Evaluate the local storage performance characteristics of the EC2 instances.
Identify that EBS gp3 volumes are used for read-intensive static session assets. These volumes support independent configuration of IOPS and throughput.
Provisioning higher IOPS and throughput directly on gp3 volumes prevents storage I/O bottlenecks during the flash sale without the need to increase volume capacity or cause downtime.
3
Address the rapid network/compute traffic scaling requirements at the load balancing tier.
Recognize that a tenfold spike within 5 minutes is too rapid for default ALB auto-scaling, requiring pre-warming or scheduled scaling.
This ensures the ALB has the capacity provisioned beforehand, preventing HTTP 503 errors and dropped connections.

Anahtar Kavram

Scaling read-heavy database workloads with RDS Read Replicas, optimizing EBS gp3 performance independently of volume size, and understanding ALB scaling limitations under sudden spikes.
Bu soruyu puanla

Konular

Optimizing Compute and Storage Performance