A global logistics company is preparing for a major system integration that will connect a… — AWS Certified Solutions Architect - Professional

A global logistics company is preparing for a major system integration that will connect a new partner's fleet of $100,000$ delivery vehicles. The integration will launch on a specific date and will result in an immediate, one-time $20\times$ increase in telemetry traffic at exactly 09:00 UTC. The existing telemetry processing service runs on Amazon EC2 instances inside an Auto Scaling group (ASG) behind an Application Load Balancer (ALB). The instances reside in private subnets across two Availability Zones (AZ-A and AZ-B) and retrieve reference metadata from external APIs via a single NAT Gateway located in AZ-A. The EC2 instances require a $5$ -minute bootstrapping period to pull configuration files and warm up application caches before they can successfully process requests. Under the current scaling configuration, when CPU utilization spikes, the ASG launches instances but does not wait for the bootstrapping to complete before launching more, resulting in severe over-provisioning. Additionally, the architecture must ensure that a failure of a single Availability Zone or NAT Gateway does not disrupt outbound connectivity for the EC2 instances. Which three actions should the Solutions Architect take to prepare the architecture for the launch and resolve these reliability issues?

Create a NAT Gateway in AZ-B, and configure the route table of the private subnets in AZ-B to route outbound internet traffic through this new gateway.Cevap
Update the Auto Scaling group scaling policy to include a default instance warmup of $300$ seconds.Cevap
Submit a request to AWS Support to pre-warm the Application Load Balancer to the expected request rate and concurrent connection levels prior to the launch time.Cevap
D
Deploy a second NAT Gateway in AZ-A, and configure Route 53 DNS failover to route outbound traffic between the two NAT Gateways.
E
Decrease the Auto Scaling group's cooldown period to $60$ seconds to allow the group to quickly launch additional instances.
F
Configure an Application Load Balancer scaling policy based on target response times to automatically scale the load balancer capacity during the spike.

Cevap

To resolve these issues, the Solutions Architect should create a NAT Gateway in AZ-B and update the route table for AZ-B's private subnets, configure the Auto Scaling group scaling policy to include a default instance warmup of

300

seconds, and submit a request to AWS Support to pre-warm the Application Load Balancer.

The correct options address the three specific requirements: establishing AZ-specific NAT Gateways to avoid a single point of failure for outbound traffic, configuring an instance warmup period of

300

seconds to match the bootstrapping duration and prevent over-provisioning, and requesting ALB pre-warming from AWS Support to handle the sudden, massive traffic spike.

Adım Adım Çözüm

Address the single point of failure for outbound internet traffic by creating a second NAT Gateway in AZ-B and updating the routing of the private subnets in AZ-B to point to this new NAT Gateway, leaving the route tables in AZ-A untouched.

Each Availability Zone has independent outbound internet routing, eliminating cross-AZ dependencies and single points of failure.

Outbound traffic from private subnets needs to be resilient to AZ failures, which requires localized NAT Gateways per AZ.

Resolve the scaling policy over-provisioning by modifying the ASG settings to include a default instance warmup of

300

seconds.

The ASG will pause scaling actions for

300

seconds after launching an instance, allowing it to bootstrap fully before the group evaluates metrics again.

This prevents the scaling metric from continuously triggering scale-out actions while newly launched instances are still bootstrapping.

Ensure the Application Load Balancer can handle the instantaneous

20\times

traffic surge by submitting a pre-warming request ticket to AWS Support.

AWS will pre-allocate sufficient capacity for the ALB in advance of the scheduled launch.

Standard ALB auto-scaling is reactive and cannot keep pace with an instantaneous, massive flash traffic spike.

Anahtar Kavram

To achieve high availability and handle sudden traffic spikes, Solution Architects must design multi-AZ redundant NAT configurations, utilize ELB pre-warming for anticipated massive surges, and tune Auto Scaling group warmup/cooldown intervals to match instance bootstrapping times.

Soru

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Konular