A company is launching a global online ticket booking platform. The architecture consists of an Application Load Balancer (ALB) routing requests to an Amazon Elastic Container Service (Amazon ECS) cluster running on AWS Fargate. The application stores ticket availability and booking details in an Amazon Aurora PostgreSQL database. During major ticket release events, traffic is expected to scale instantly from a baseline of requests per second to a peak of requests per second. During testing, the rapid surge in traffic caused the ALB to return HTTP 503 Service Unavailable errors. Additionally, the primary database instance suffered from high CPU utilization due to a massive volume of read-only queries from users searching for available seats. The solutions architect must optimize the platform's performance and scalability to handle the flash traffic without dropping requests or degrading the user experience. Which two recommendations should the Solutions Architect make to scale the platform and prevent performance degradation?
- Request AWS Support to pre-warm the Application Load Balancer to the expected capacity prior to the ticket release events, to prevent dropped connections from the instantaneous traffic burst.Cevap
- Deploy Amazon Aurora Replicas in multiple Availability Zones and configure Aurora Auto Scaling to dynamically scale the read capacity based on reader CPU utilization.Cevap
- CRely on the Application Load Balancer's automatic scaling policies to scale out in response to the traffic surge, as pre-warming is handled natively without prior request.
- DConfigure the application to route search queries to the Amazon RDS Multi-AZ standby instance to offload the primary database instance and scale query capacity.
- EDeploy an Amazon ElastiCache for Memcached cluster to cache search results and replicate session state with multi-AZ persistence.