What should a solutions architect do to meet these requirements?

By:
On:
In: SAA-C03
Tagged:
With: 0 Comments
A gaming company is designing a highly available architecture.The application runs on a modified Linux kernel and supports only UDP-based traffic.The company needs the front-end tier to provide the best possible user experience.That tier must have low latency, route traffic to the nearest edge location, and provide static IP addresses for entry into the application endpoints.

What should a solutions architect do to meet these requirements?

Configure Amazon Route 53 to forward requests to an Application Load Balancer. Use AWS Lambda for the application in AWS Application Auto Scaling.

Configure Amazon CloudFront to forward requests to a Network Load Balancer. Use AWS Lambda for the application in an AWS Application Auto Scaling group.

Configure AWS Global Accelerator to forward requests to a Network Load Balancer. Use Amazon EC2 instances for the application in an EC2 Auto Scaling group.

Configure Amazon API Gateway to forward requests to an Application Load Balancer. Use Amazon EC2 instances for the application in an EC2 Auto Scaling group.

Explanations:

Amazon Route 53 cannot provide low latency with static IPs, and Application Load Balancers are not optimized for UDP traffic.

While CloudFront can help with latency, it does not natively support UDP traffic. Network Load Balancers are suitable, but AWS Lambda is not a good fit for the architecture described.

AWS Global Accelerator provides static IPs, improves latency by routing to the nearest edge, and can forward UDP traffic to a Network Load Balancer with EC2 instances in an Auto Scaling group.

API Gateway is not suitable for UDP traffic, and while it can route to an Application Load Balancer, it does not meet the requirement for low latency and static IPs.

Leave a Reply

Your email address will not be published. Required fields are marked *

four × one =