Load Balancing for Evenly Distributed Traffic in AWS | Exam Preparation Guide

Load Balancing for Evenly Distributed Traffic

Prev Question Next Question

Question

As an AWS professional you have been told to ensure that traffic to an application is evenly balanced.

The application has multiple web servers that host the application? Choose an answer from the options below which will fulfil the above requirement.

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E.

Answer - C.

Option A is INCORRECT because a NAT instance is ideally used to route traffic from a private subnet to the internet via a public subnet.

Option B is INCORRECT because you don't want to point Cloudfront to private IP Addresses.

Option D is INCORRECT because we use the ALIAS record of the ELB DNS name instead of EIP.

You can use an ELB, assign the web servers and have a Route 53 entry to the ELB.For more information on how to use ELB, please visit the below link:

https://aws.amazon.com/elasticloadbalancing/

The correct answer to ensure traffic to an application is evenly balanced among multiple web servers is option D: Configure a Route53 ALIAS record to point to the ELB DNS name.

Explanation:

Amazon Elastic Load Balancer (ELB) is a load balancer service provided by AWS that automatically distributes incoming traffic to multiple targets, such as EC2 instances or containers, across multiple Availability Zones within a region.

Option A is incorrect because it suggests using a NAT instance, which is not a load balancer and does not distribute traffic evenly across multiple targets. Also, a DNS A record that points to the NAT instance public IP address would not distribute traffic among multiple targets.

Option B is incorrect because CloudFront is a content delivery network (CDN) that caches and delivers content from edge locations closer to the user. It is not a load balancer service and does not distribute traffic evenly across multiple targets.

Option C is incorrect because EL (Elastic Load Balancing) is not a valid AWS service. Perhaps the option was meant to suggest using EC2 Auto Scaling groups, which can automatically adjust the number of EC2 instances in response to changes in demand. However, Auto Scaling groups alone do not distribute traffic evenly across multiple instances.

Option D is the correct answer because it suggests using Route53, AWS's domain name system (DNS) service, to create an ALIAS record that points to the DNS name of an ELB. This record will automatically resolve to the IP addresses of the healthy instances registered with the ELB, thus distributing incoming traffic evenly across them. This option is recommended for applications that require high availability and scalability.

Option E is incorrect because it suggests configuring an Elastic IP (EIP) address for the ELB, which is not recommended as it may lead to a single point of failure. Also, a DNS A record that points to the EIP would not distribute traffic among multiple instances.