Examkin

Question

Difficulty: HardHigh-Performing and Scalable Network Architectures

An IoT analytics company collects telemetry data from millions of globally distributed devices. The ingestion endpoints are hosted on Amazon EC2 instances behind Network Load Balancers (NLBs) in the us-east-1 and eu-west-1 Regions. The telemetry client applications transmit packets over UDP and require minimal network latency and high availability. During peak periods, regional public internet congestion causes packet loss and latency spikes. The architecture must dynamically route client traffic to the closest healthy Region and fail over within seconds if a Region becomes unreachable. Which two actions should a solutions architect take to meet these requirements?

  1. Associate the Network Load Balancers in both Regions as endpoints of an AWS Global Accelerator accelerator.Answer
  2. Update the client applications to connect to the Anycast IP addresses provided by the AWS Global Accelerator accelerator.Answer
  3. C
    Configure Amazon Route 53 latency-based routing records pointing to the NLB DNS names, relying on DNS health checks for automatic failover.
  4. D
    Establish AWS Site-to-Site VPN connections between the client networks and each Region to route UDP traffic, utilizing a single VPN tunnel per Region.
  5. E
    Configure Network ACL rules in the public subnets to statefully track the return UDP traffic, while configuring Security Groups as stateless to optimize packet processing.

Answer

Associate the Network Load Balancers in both Regions as endpoints of an AWS Global Accelerator accelerator, and update the client applications to connect to the Anycast IP addresses provided by the AWS Global Accelerator accelerator.
The correct answer combines associating the Network Load Balancers in both Regions as endpoints of an AWS Global Accelerator accelerator with updating the client applications to connect to the Anycast IP addresses provided by the accelerator. AWS Global Accelerator routes client UDP traffic over the AWS global private network instead of the public internet, avoiding regional congestion, and uses static Anycast IP addresses to dynamically route connections to the nearest healthy endpoint. In the event of an outage in one Region, Global Accelerator detects the failure via endpoint health checks and automatically redirects client traffic to the alternate Region within seconds, bypassing DNS caching delays.

Step-by-Step Solution

1
Analyze the performance and latency requirements of the UDP workload.
The telemetry data uses UDP, suffers from public internet congestion, and requires low-latency routing to the closest Region with rapid, sub-minute failover.
This determines that DNS-based routing (Route 53) is inadequate because client-side caching of DNS answers delays failover beyond the 'seconds' requirement.
2
Evaluate AWS Global Accelerator for global UDP routing.
AWS Global Accelerator provides Anycast IP addresses that ingest UDP traffic at the nearest AWS edge location and transport it over the congestion-free AWS global network to the NLB endpoints.
This directly resolves the public internet packet loss and latency spikes while providing health-check-driven failover to the alternative Region within seconds.
3
Select the required architectural steps to implement AWS Global Accelerator.
The NLBs in both Regions are associated as endpoints with the accelerator, and the client applications are configured to direct their traffic to the accelerator's Anycast IP addresses.
These two steps establish the scalable and highly available global routing path.

Key Concept

AWS Global Accelerator uses static Anycast IP addresses and the AWS global network to provide low-latency, high-performance routing and sub-minute automatic failover for TCP and UDP workloads across multiple Regions.
Rate this question

Topics

High-Performing and Scalable Network Architectures

More questions from this topic