Examkin

Soru

Zorluk: OrtaHigh-Performing and Scalable Network Architectures

A company hosts a latency-sensitive web application on Amazon EC2 instances behind Application Load Balancers (ALBs) in both the us-east-1 and eu-west-1 Regions. The company wants to optimize the network performance for its global user base, reduce latency, and ensure automated failover to the healthy Region if an ALB fails. Which TWO options should a solutions architect recommend to achieve this high-performing and resilient network architecture?

  1. Provision an AWS Global Accelerator accelerator and configure the ALBs in both Regions as endpoints under the accelerator.Cevap
  2. Configure Amazon Route 53 using a latency-routing policy to direct users to the closest Region, and configure Route 53 health checks on the ALBs to ensure failover.Cevap
  3. C
    Deploy a AWS Site-to-Site VPN connection from the users' client devices to each Region to tunnel traffic securely with up to 1.25 Gbps1.25\text{ Gbps} throughput.
  4. D
    Configure Amazon Route 53 with latency-based routing without active health checks, relying on client-side browser caching to detect load balancer failures.
  5. E
    Configure stateful Network ACLs at the subnet level in both Regions to dynamically reroute inbound HTTP/HTTPS traffic to the alternate Region's ALB if local instances become unresponsive.

Cevap

The solutions architect should provision an AWS Global Accelerator accelerator to route traffic over the AWS global network to the ALBs, and configure Amazon Route 53 with a latency-routing policy combined with active health checks to ensure traffic is directed to the lowest-latency healthy endpoint.
Provisioning an AWS Global Accelerator accelerator is correct because it uses anycast IP addresses and the AWS global network to route traffic to the nearest healthy ALB endpoint, reducing latency and jitter. Configuring Route 53 with latency-based routing and health checks is correct because it resolves DNS queries to the lower-latency Region while automatically omitting unhealthy endpoints if an ALB fails.

Adım Adım Çözüm

1
Evaluate the need for global traffic routing and latency reduction.
Identify that AWS Global Accelerator uses the AWS private global fiber network to route user requests, providing low-latency, anycast IP-based ingress and rapid regional failover.
Global Accelerator optimizes the network path from the user's nearest edge location to the ALB, bypassing the public internet where possible.
2
Analyze DNS-based routing options for multi-Region high availability.
Select Amazon Route 53 with latency-based routing and health checks enabled.
Adding health checks ensures that Route 53 stops returning the IP address of an ALB that fails, preventing blackholing of user traffic.
3
Identify and eliminate options that violate physical or service constraints.
Exclude VPN-based routing due to the 1.25 Gbps1.25\text{ Gbps} tunnel limit and client scaling issues, exclude health-check-free DNS configuration because it fails to provide automated failover, and discard Network ACLs because they are stateless and incapable of routing traffic between Regions.
Understanding limits like VPN bandwidth and the operational characteristics of Route 53 and Network ACLs helps eliminate suboptimal or incorrect designs.

Anahtar Kavram

High-performing global routing and multi-Region resilience require combining latency-optimized path selection (AWS Global Accelerator or Route 53 latency routing) with active health monitoring to automate failover.
Bu soruyu puanla

Konular

High-Performing and Scalable Network Architectures

Bu konudan daha fazla soru