Examkin

Soru

Zorluk: OrtaPerformance and Scalability Optimization

A telemetry company is designing a new vehicle tracking system. The system receives data from 200,000200,000 active devices. Due to a daily batch update from a partner API, the system experiences a sudden, instant spike in read queries on the product database, rising from 500500 queries per second to 30,00030,000 queries per second within 3030 seconds. The application runs on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB) and uses an Amazon RDS for PostgreSQL Multi-AZ DB instance. Which configuration should the solutions architect implement to scale the system for these sudden traffic spikes while minimizing query latency?

  1. A
    Rely on the Application Load Balancer's default auto-scaling to absorb the connection spike, deploy Amazon RDS PostgreSQL Read Replicas, and configure the application to route read queries to the Read Replica endpoints.
  2. Submit a support case to AWS to pre-warm the Application Load Balancer prior to the daily update window, deploy Amazon RDS PostgreSQL Read Replicas, and configure the application to route read queries to the Read Replica endpoints.Cevap
  3. C
    Submit a support case to AWS to pre-warm the Application Load Balancer prior to the daily update window, and configure the application to route read queries to the standby DB instance of the RDS Multi-AZ deployment to utilize the idle standby database capacity.
  4. D
    Rely on the Application Load Balancer's default auto-scaling to absorb the connection spike, and configure the application to route read queries to the standby DB instance of the RDS Multi-AZ deployment to optimize resource utilization.

Cevap

Submit a support case to AWS to pre-warm the Application Load Balancer prior to the daily update window, deploy Amazon RDS PostgreSQL Read Replicas, and configure the application to route read queries to the Read Replica endpoints.
The correct solution addresses the limitations of both the load balancer and the database during sudden, extreme spikes. First, because the load balancer cannot scale instantly to handle a 6060-fold spike within 3030 seconds, pre-warming by AWS Support is required. Second, standard RDS Multi-AZ deployments use a passive standby database that cannot accept connections; therefore, to scale reads, the solutions architect must deploy RDS Read Replicas and point the application's read queries to the replica endpoints.

Adım Adım Çözüm

1
Analyze the load balancer scaling characteristics for the rapid traffic spike.
Identify that the traffic increases from 500500 to 30,00030,000 requests per second within 3030 seconds, which exceeds the normal scaling rate of the Application Load Balancer. This requires pre-warming by AWS Support.
Default scaling of the load balancer is gradual. A sudden surge can cause latency and dropped connections if the load balancer has not pre-scaled.
2
Analyze the database scaling capability for high-volume read traffic.
Determine that the Amazon RDS Multi-AZ standby instance cannot serve read queries, necessitating the creation of dedicated RDS Read Replicas to offload the read traffic from the primary writer instance.
Amazon RDS Multi-AZ standby instances are passive and do not accept incoming connections. Horizontal read scaling must be handled by Read Replicas.
3
Combine the load balancer and database tier solutions.
Formulate a configuration consisting of requesting ALB pre-warming and routing queries to the newly deployed Read Replica endpoints.
This dual-tier optimization ensures that both the ingestion/entry point (ALB) and the data storage layer (RDS) scale seamlessly under flash traffic conditions.

Anahtar Kavram

Handling sudden flash traffic spikes requires pre-warming the load balancer and offloading read queries to Read Replicas, since standard RDS Multi-AZ standby instances cannot serve read traffic.
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Performance and Scalability Optimization

Bu konudan daha fazla soru