Examkin

Question

Difficulty: HardEdge Caching and Content Delivery for Resilient Architectures

A global logistics company has deployed a fleet-tracking application that ingests real-time telemetry data from vehicle sensors using a proprietary TCP-based protocol. The backend application is hosted on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB) in a primary AWS Region. The company requires a highly resilient architecture that minimizes latency for global clients, prevents packet loss over the public internet, and automatically fails over to a secondary Region in the event of an outage. Which architecture should a solutions architect recommend to meet these requirements?

  1. A
    Create an Amazon CloudFront distribution with the ALBs configured in an origin group for failover. Set the caching behavior to forward all headers and query parameters, and set the default Time to Live (TTL) to zero.
  2. Create an AWS Global Accelerator accelerator, and associate the ALBs in both the primary and secondary Regions as endpoints. Configure the vehicle sensors to send telemetry data to the static IP addresses provided by the accelerator.Answer
  3. C
    Configure Amazon Route 53 with latency-based routing and health checks pointing to the ALBs in both Regions, allowing client sensors to establish direct TCP connections over the public internet to the closest regional endpoint.
  4. D
    Deploy an AWS WAF Web ACL associated with AWS Shield Advanced at the edge, and configure it to route incoming TCP traffic from the sensors directly to the ALBs in both Regions using IP-based rules.

Answer

Create an AWS Global Accelerator accelerator, associate the Application Load Balancers in both Regions as endpoints, and configure the vehicle sensors to send telemetry data to the accelerator's static IP addresses.
AWS Global Accelerator is the correct solution because it supports TCP and UDP protocols, routes traffic over the congestion-free AWS global network to minimize latency and packet loss, and provides automatic regional failover via health checks. Additionally, it offers static Anycast IP addresses, eliminating issues associated with DNS caching.

Step-by-Step Solution

1
Analyze the application protocol and requirements.
Identify that the application uses a proprietary TCP-based protocol (non-HTTP/HTTPS) and requires low latency, prevention of packet loss, and multi-region failover.
This determines which edge service is capable of routing the traffic, as Amazon CloudFront and AWS WAF only support HTTP/HTTPS, whereas AWS Global Accelerator supports TCP/UDP.
2
Evaluate AWS Global Accelerator as a routing solution.
AWS Global Accelerator provides two static Anycast IP addresses that route traffic over the AWS global private network to the nearest regional endpoint.
Routing traffic over the AWS global backbone reduces network hops, minimizes latency, prevents packet loss over the public internet, and avoids DNS caching issues during failover.
3
Configure endpoint groups and health checks.
Associate the Application Load Balancers (ALBs) from both the primary and secondary Regions as endpoints within the accelerator.
Global Accelerator monitors endpoint health and automatically routes client traffic to the secondary Region in the event of an outage in the primary Region.

Key Concept

AWS Global Accelerator vs. Amazon CloudFront for non-HTTP protocols and multi-region resiliency.
Estimated Time:2m 30s
Rate this question

Topics

Edge Caching and Content Delivery for Resilient Architectures

More questions from this topic