Examkin

Question

Difficulty: MediumEdge Caching and Content Delivery for Resilient Architectures

A company operates a globally distributed mobile gaming application. The gaming client communicates with a backend matchmaking and state service using a custom TCP-based protocol. The backend is currently hosted on Amazon ECS tasks behind an Application Load Balancer (ALB) in a single AWS Region. Users in distant regions are experiencing high latency and connection timeouts due to public internet routing inefficiencies. Additionally, client devices require a fixed set of IP addresses for security allowlisting in corporate firewalls. Which solution should a solutions architect recommend to resolve the latency issues while meeting the security requirements?

  1. Configure AWS Global Accelerator in front of the ALB. Register the ALB as the endpoint group target. Update the client configuration to connect via the provided Anycast static IP addresses.Answer
  2. B
    Configure an Amazon CloudFront distribution with the ALB as the origin. Route traffic through CloudFront using a custom Domain Name System (DNS) record, and enable Origin Shield.
  3. C
    Configure Amazon Route 53 with latency-based routing to resolve the application's domain name directly to the ALB. Apply AWS WAF to the ALB to accelerate TCP connections.
  4. D
    Deploy AWS WAF and enable AWS Shield Advanced directly on the ALB. Use the AWS Shield Anycast IPs to route global client traffic through the nearest AWS edge location.

Answer

Configure AWS Global Accelerator in front of the ALB. Register the ALB as the endpoint group target. Update the client configuration to connect via the provided Anycast static IP addresses.
AWS Global Accelerator is designed to optimize routing and improve availability for TCP and UDP traffic by onboarding traffic at the nearest AWS Edge Location and routing it over the congestion-free AWS global network. It also provides two static Anycast IP addresses, which satisfies the client firewall allowlisting requirement.

Step-by-Step Solution

1
Analyze the protocol and client requirements.
The application uses a custom TCP-based protocol (non-HTTP/S) and requires static IP addresses on the client-side for firewall allowlisting.
This rules out Amazon CloudFront, which is restricted to HTTP/HTTPS traffic, and requires a service that can provide static Anycast IPs.
2
Evaluate network acceleration services.
AWS Global Accelerator supports non-HTTP TCP/UDP protocols, routes traffic over the AWS global network to reduce latency, and provides two static Anycast IP addresses.
This directly matches all requirements of the scenario, including latency reduction and fixed IP support.
3
Select the optimal architecture configuration.
Provision AWS Global Accelerator with the Application Load Balancer (ALB) as the endpoint target.
This setup allows clients to connect to the static Anycast IPs, routing their TCP packets over the optimized AWS global backbone to the ALB.

Key Concept

AWS Global Accelerator vs. Amazon CloudFront for non-HTTP/S TCP traffic
Estimated Time:1m 30s
Rate this question

Topics

Edge Caching and Content Delivery for Resilient Architectures

More questions from this topic