AWS Certified Solutions Architect - Associate
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A company wants to run a gaming application on Amazon EC2 instances that are part of an Auto Scaling group in the AWS Cloud. The application will transmit data by using UDP packets. The company wants to ensure that the application can scale out and in as traffic increases and decreases.
What should a solutions architect do to meet these requirements?
Other
Community
UAnonymous
A
Attach a Network Load Balancer to the Auto Scaling group.
B
Attach an Application Load Balancer to the Auto Scaling group.
C
Deploy an Amazon Route 53 record set with a weighted policy to route traffic appropriately.
D
Deploy a NAT instance that is configured with port forwarding to the EC2 instances in the Auto Scaling group.
Explanation:
Explanation
Correct Answer: A - Attach a Network Load Balancer to the Auto Scaling group.
Why this is correct:
- UDP Protocol Support: Network Load Balancers (NLB) support both TCP and UDP protocols at Layer 4 (transport layer), making them suitable for gaming applications that use UDP packets for real-time communication.
- Auto Scaling Integration: NLBs can be directly attached to Auto Scaling groups, allowing them to automatically register new instances as they scale out and deregister instances as they scale in.
- Low Latency: NLBs provide ultra-low latency and high throughput, which is critical for gaming applications.
- Connection Persistence: NLBs can preserve the source IP address and support connection persistence, which is important for UDP-based applications.
Why other options are incorrect:
B. Attach an Application Load Balancer to the Auto Scaling group.
- ALBs operate at Layer 7 (application layer) and only support HTTP/HTTPS protocols, not UDP.
- ALBs are designed for web applications, not real-time gaming applications using UDP.
C. Deploy an Amazon Route 53 record set with a weighted policy to route traffic appropriately.
- Route 53 is a DNS service that operates at the DNS level, not suitable for real-time load balancing of UDP traffic.
- DNS-based routing has limitations: DNS caching can delay failover, and it doesn't provide the same level of health checking and automatic instance registration as a load balancer.
- This approach would require manual updates to DNS records when instances scale in/out.
D. Deploy a NAT instance that is configured with port forwarding to the EC2 instances in the Auto Scaling group.
- NAT instances are primarily for outbound internet connectivity, not for load balancing incoming traffic.
- This would create a single point of failure and wouldn't automatically handle instance registration/deregistration from Auto Scaling.
- Port forwarding on a NAT instance would require manual configuration updates when instances scale in/out.
Key AWS Service Features:
- Network Load Balancer (NLB): Layer 4 load balancer, supports TCP/UDP protocols, preserves source IP, handles millions of requests per second, integrates with Auto Scaling.
- Application Load Balancer (ALB): Layer 7 load balancer, supports HTTP/HTTPS only, provides advanced routing features.
- Route 53: DNS service with routing policies, but not suitable for real-time load balancing of UDP traffic.
- NAT Instance/Gateway: Provides outbound internet access for private instances, not designed for incoming traffic load balancing.
For gaming applications using UDP with Auto Scaling, a Network Load Balancer is the appropriate solution to ensure scalability, low latency, and automatic instance management.
Comments
Loading comments...