Examkin

Soru

Zorluk: OrtaEdge Caching and Content Delivery for Resilient Architectures

An architecture team is designing a global IoT telemetry solution. The system collects continuous status reports from millions of devices using a custom TCP-based protocol. The backend ingestion servers run on Amazon EC2 instances behind Application Load Balancers (ALBs) deployed in the us-east-1 and eu-west-1 regions. The solution must minimize packet latency, route device traffic to the nearest healthy region, and automatically failover within seconds during a regional outage. Which AWS service configuration meets these resilience and performance requirements?

  1. Provision AWS Global Accelerator and associate the Application Load Balancers (ALBs) in both regions as endpoints. Configure the accelerator to route custom TCP traffic over the AWS global network to the nearest healthy ALB, providing automatic failover.Cevap
  2. B
    Create an Amazon CloudFront distribution with the Application Load Balancers (ALBs) configured in an origin group. Set the default Cache-Control headers and Time-To-Live (TTL) to zero to route the custom TCP telemetry traffic without caching.
  3. C
    Use Amazon Route 53 with a latency-based routing policy to route client traffic directly to the Application Load Balancers (ALBs). Rely on the client’s DNS cache expiration to handle regional failover when an ALB becomes unhealthy.
  4. D
    Deploy AWS WAF at the edge to inspect incoming custom TCP traffic and configure AWS Shield Standard on the Application Load Balancers (ALBs) to manage cross-region failover and traffic redirection.

Cevap

Provision AWS Global Accelerator and associate the Application Load Balancers (ALBs) in both regions as endpoints. Configure the accelerator to route custom TCP traffic over the AWS global network to the nearest healthy ALB, providing automatic failover.
AWS Global Accelerator is designed to optimize performance and availability for TCP and UDP traffic. It uses Anycast IP addresses to ingest traffic at the edge location closest to the user and routes it over the AWS global network to the nearest healthy regional endpoint. It performs continuous health checks and automatically redirects traffic to healthy endpoints in other regions within seconds if a regional failure occurs.

Adım Adım Çözüm

1
Analyze the protocol requirement.
The application uses a custom TCP-based protocol rather than standard HTTP/HTTPS.
This determines which edge services are compatible, as some services are limited to specific application layer protocols.
2
Evaluate Amazon CloudFront's protocol compatibility.
CloudFront is disqualified because it only supports HTTP, HTTPS, and WebSockets.
CloudFront cannot ingest or route raw custom TCP traffic.
3
Evaluate Route 53 latency routing for the failover time constraint.
Route 53 latency routing is disqualified because it cannot guarantee failover within seconds due to client DNS caching.
DNS-based failover is dependent on TTL expiration and client compliance, which often exceeds the desired outage recovery window.
4
Select AWS Global Accelerator as the optimal solution.
AWS Global Accelerator meets the requirements by supporting custom TCP traffic, using Anycast IP routing over the AWS global backbone, and automatically failing over to healthy endpoints in seconds.
This provides both the lowest latency routing and the resilient sub-minute failover required by the scenario.

Anahtar Kavram

AWS Global Accelerator vs. Amazon CloudFront for non-HTTP TCP traffic failover and optimization
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Edge Caching and Content Delivery for Resilient Architectures

Bu konudan daha fazla soru