Examkin

Soru

Zorluk: OrtaPerformance and Scalability Optimization

A company is preparing to launch a new limited-time promotional campaign that is expected to generate an immediate surge of traffic, going from 500500 requests per second to over 250,000250,000 requests per second within less than a minute. The application is deployed on Amazon ECS Fargate behind an Application Load Balancer (ALB) and uses an Amazon Aurora PostgreSQL database. The application performs read-heavy catalog lookups and write-heavy transaction processing. Which two actions should the Solutions Architect recommend to optimize the performance and scalability of the architecture to handle the peak load?

  1. Submit a support case to AWS to pre-warm the Application Load Balancer (ALB) based on the expected traffic spike of 250,000250,000 requests per second.Cevap
  2. Deploy Aurora Replicas in the DB cluster and configure the application to route read-heavy catalog lookups to the Aurora reader endpoint.Cevap
  3. C
    Rely on the Application Load Balancer's automatic scaling capability, which handles instant traffic surges of any volume dynamically.
  4. D
    Direct the read-heavy catalog lookup queries to the Amazon Aurora Multi-AZ standby instance to offload the primary database instance.
  5. E
    Deploy an Amazon ElastiCache for Memcached cluster with multi-AZ replication to cache catalog data and provide replication failover.

Cevap

Pre-warm the Application Load Balancer (ALB) via AWS Support and deploy Aurora Replicas while directing read queries to the reader endpoint.
Pre-warming the ALB ensures that AWS pre-allocates the necessary network and compute resources to handle the rapid traffic increase, preventing dropped connections. Using Aurora Replicas and directing queries to the reader endpoint scales read operations horizontally and prevents database resource exhaustion during peak volumes.

Adım Adım Çözüm

1
Analyze the scaling characteristics of the Application Load Balancer under sudden flash traffic.
Identify that a sudden jump from 500500 to 250,000250,000 requests per second requires pre-warming to avoid initial HTTP 503 errors and dropped connections.
The ALB autoscaler takes time to detect and scale out in response to traffic growth, making pre-warming essential for instantaneous spikes.
2
Evaluate the database read scaling requirements.
Determine that deploying Aurora Replicas and routing read-heavy queries to the reader endpoint offloads the primary database instance.
This allows the primary instance to handle write-heavy transaction processing without performance degradation.
3
Evaluate and eliminate incorrect database scaling and caching strategies.
Discard RDS Multi-AZ standby routing and Memcached replication architectures.
RDS standby instances do not serve read traffic, and ElastiCache for Memcached lacks built-in multi-AZ replication.

Anahtar Kavram

Handling sudden high-scale traffic spikes on AWS requires pre-provisioning capacity (pre-warming) at the load balancing tier and horizontally scaling the database tier using read replicas rather than relying on standby instances.
Bu soruyu puanla

Konular

Performance and Scalability Optimization

Bu konudan daha fazla soru