Elastic Load Balancer MCQS

Question 1: Which type of Elastic Load Balancer (ELB) operates at the transport layer (Layer 4) of the OSI
model and can handle both TCP and UDP traffic?

A) Application Load Balancer (ALB).

B) Classic Load Balancer (CLB).

C) Network Load Balancer (NLB).

D) Elastic Load Balancer (ELB).

Answer: C) Network Load Balancer (NLB).

Explanation: Network Load Balancer operates at the transport layer (Layer 4) of the OSI model and can
handle both TCP and UDP traffic. It is designed to handle high-throughput, low-latency applications, and
is often used for scenarios such as gaming, real-time media streaming, and IoT applications.

Question 2: Which Elastic Load Balancer (ELB) type allows you to route requests to different target
groups based on the content of the request, such as the URL or HTTP headers?

A) Application Load Balancer (ALB).

B) Classic Load Balancer (CLB).

C) Network Load Balancer (NLB).

D) Elastic Load Balancer (ELB).

Answer: A) Application Load Balancer (ALB).

Explanation: Application Load Balancer (ALB) operates at the application layer (Layer 7) of the OSI model
and allows you to route requests to different target groups based on the content of the request, such as
the URL or HTTP headers. This enables more sophisticated and fine-grained load balancing for modern
web applications.
Question 3: Which Elastic Load Balancer (ELB) type is the oldest and provides basic load balancing across
multiple Amazon EC2 instances?

A) Application Load Balancer (ALB).

B) Classic Load Balancer (CLB).

C) Network Load Balancer (NLB).

D) Elastic Load Balancer (ELB).

Answer: B) Classic Load Balancer (CLB).

Explanation: Classic Load Balancer (CLB) is the oldest ELB type and provides basic load balancing across
multiple Amazon EC2 instances. It operates at both Layer 4 and Layer 7, making it suitable for simple
applications that do not require the advanced features of ALB or NLB.

Question 4: How does Elastic Load Balancing (ELB) help improve the availability and fault tolerance of
applications?

A) ELB automatically increases the CPU capacity of EC2 instances to handle increased traffic.

B) ELB automatically launches new EC2 instances when the existing ones fail health checks.

C) ELB replicates application data across multiple Availability Zones for data redundancy.

D) ELB uses Route 53 to redirect traffic to healthy instances in case of failure.

Answer: B) ELB automatically launches new EC2 instances when the existing ones fail health checks.

Explanation: Elastic Load Balancing (ELB) automatically monitors the health of registered EC2 instances
and performs health checks. If an instance fails a health check or becomes unavailable, ELB automatically
stops sending traffic to that instance and starts routing traffic to healthy instances to maintain the
desired level of availability.

Question 5: Which Elastic Load Balancer (ELB) type supports SSL/TLS termination and allows you to
offload SSL decryption from EC2 instances?
A) Application Load Balancer (ALB).

B) Classic Load Balancer (CLB).

C) Network Load Balancer (NLB).

D) Elastic Load Balancer (ELB).

Answer: A) Application Load Balancer (ALB).

Explanation: Application Load Balancer (ALB) supports SSL/TLS termination, allowing you to offload SSL
decryption from EC2 instances. ALB can handle HTTPS traffic and terminate SSL connections, improving
the performance of EC2 instances by reducing their processing overhead for SSL encryption and
decryption.

Question 6: In which scenario would you use a Network Load Balancer (NLB) over an Application Load
Balancer (ALB)?

A) When you need to distribute traffic across multiple target groups based on URL paths.

B) When you want to load balance TCP and UDP traffic for gaming applications.

C) When you need to offload SSL decryption from EC2 instances for HTTPS traffic.

D) When you want to route traffic based on HTTP request headers.

Answer: B) When you want to load balance TCP and UDP traffic for gaming applications.

Explanation: Network Load Balancer (NLB) is ideal for load balancing TCP and UDP traffic. It is commonly
used for gaming applications, IoT applications, and other use cases that require high-throughput, low-
latency load balancing at the transport layer (Layer 4) of the OSI model.

Question 7: Which Elastic Load Balancer (ELB) type supports content-based routing, path-based routing,
and host-based routing?

A) Application Load Balancer (ALB).

B) Classic Load Balancer (CLB).

C) Network Load Balancer (NLB).

D) Elastic Load Balancer (ELB).

Answer: A) Application Load Balancer (ALB).

Explanation: Application Load Balancer (ALB) supports content-based routing, path-based routing, and
host-based routing. This allows you to route requests to different target groups based on the content of
the request, URL paths, or HTTP host headers.

Question 1: Which type of Elastic Load Balancer (ELB) can route traffic to multiple target groups based on
the content of the request, such as the URL or HTTP headers?

A) Application Load Balancer (ALB).

B) Classic Load Balancer (CLB).

C) Network Load Balancer (NLB).

D) Elastic Load Balancer (ELB).

Answer: A) Application Load Balancer (ALB).

Explanation: The Application Load Balancer (ALB) operates at the application layer (Layer 7) of the OSI
model and can route traffic to multiple target groups based on the content of the request, such as the
URL or HTTP headers. ALB provides more advanced and flexible routing capabilities for modern web
applications.

Question 2: Which Elastic Load Balancer (ELB) type is best suited for distributing TCP and UDP traffic, and
is ideal for high-throughput, low-latency applications like gaming and IoT?

A) Application Load Balancer (ALB).

B) Classic Load Balancer (CLB).

C) Network Load Balancer (NLB).

D) Elastic Load Balancer (ELB).

Answer: C) Network Load Balancer (NLB).

Explanation: The Network Load Balancer (NLB) is designed to handle TCP and UDP traffic and is suitable
for high-throughput, low-latency applications like gaming and IoT. It operates at the transport layer
(Layer 4) of the OSI model, providing ultra-low latencies and high connection scalability.

Question 3: How does Elastic Load Balancing (ELB) contribute to the security of your application and
infrastructure?

A) ELB automatically encrypts all traffic between the load balancer and the EC2 instances.

B) ELB performs regular security audits on the EC2 instances registered with the load balancer.

C) ELB acts as a web application firewall, blocking malicious traffic from reaching the EC2 instances.

D) ELB hides the IP addresses of the EC2 instances, adding an extra layer of protection.

Answer: D) ELB hides the IP addresses of the EC2 instances, adding an extra layer of protection.

Explanation: Elastic Load Balancing (ELB) hides the IP addresses of the EC2 instances behind the load
balancer's own IP address. Clients communicate with the load balancer, which then forwards requests to
the instances. This adds an extra layer of protection, as the IP addresses of the instances are not directly
exposed to the clients.

Question 4: How does Elastic Load Balancing (ELB) handle instances that fail health checks?

A) ELB will immediately terminate instances that fail health checks to prevent further issues.

B) ELB will continue to send traffic to instances that fail health checks to give them a chance to recover.

C) ELB will stop sending traffic to instances that fail health checks and redirect traffic to healthy
instances.

D) ELB will automatically disable health checks for instances that fail to avoid unnecessary scaling
actions.
Answer: C) ELB will stop sending traffic to instances that fail health checks and redirect traffic to healthy
instances.

Explanation: Elastic Load Balancing (ELB) continuously monitors the health of registered instances using
health checks. If an instance fails a health check, ELB will stop sending traffic to that instance and
redirect traffic to healthy instances to ensure high availability.

Question 5: How does Elastic Load Balancing (ELB) help with horizontal scaling of your application?

A) ELB automatically increases the size of EC2 instances to handle increased traffic.

B) ELB automatically replicates your application across multiple AWS regions.

C) ELB distributes incoming traffic across multiple EC2 instances, automatically scaling based on demand.

D) ELB stores your application data in multiple Availability Zones for redundancy.

Answer: C) ELB distributes incoming traffic across multiple EC2 instances, automatically scaling based on
demand.

Explanation: Elastic Load Balancing (ELB) distributes incoming traffic across multiple EC2 instances,
automatically scaling the number of instances based on demand. As the traffic to your application
increases, ELB automatically adds more instances to handle the load and removes instances when the
traffic decreases.

Question 6: Which Elastic Load Balancer (ELB) type can route requests to different target groups based
on the domain name in the host header of the HTTP request?

A) Application Load Balancer (ALB).

B) Classic Load Balancer (CLB).

C) Network Load Balancer (NLB).

D) Elastic Load Balancer (ELB).

Answer: A) Application Load Balancer (ALB).

Explanation: The Application Load Balancer (ALB) can route requests to different target groups based on
the domain name in the host header of the HTTP request. This feature enables you to host multiple
websites or applications on a single ALB and route traffic to the appropriate target group based on the
domain name.

Question 1: Which Elastic Load Balancer (ELB) type provides support for distributing traffic to multiple
ports on the same Amazon EC2 instance?

A) Application Load Balancer (ALB).

B) Classic Load Balancer (CLB).

C) Network Load Balancer (NLB).

D) Elastic Load Balancer (ELB).

Answer: B) Classic Load Balancer (CLB).

Explanation: The Classic Load Balancer (CLB) provides support for distributing traffic to multiple ports on
the same Amazon EC2 instance. It can route traffic to different ports based on the configuration specified
in the load balancer's listener settings.

Question 2: How does Elastic Load Balancing (ELB) help ensure high availability for your application?

A) ELB replicates your application data across multiple Availability Zones for data redundancy.

B) ELB stores snapshots of your EC2 instances in different AWS regions for disaster recovery.

C) ELB automatically provisions additional EC2 instances to handle traffic spikes.

D) ELB continuously monitors the health of registered instances and redirects traffic away from
unhealthy instances.

Answer: D) ELB continuously monitors the health of registered instances and redirects traffic away from
unhealthy instances.

Explanation: Elastic Load Balancing (ELB) continuously monitors the health of registered instances using
health checks. If an instance fails a health check or becomes unavailable, ELB stops sending traffic to that
instance and redirects traffic to healthy instances to ensure high availability of your application.
Question 3: Which Elastic Load Balancer (ELB) type is recommended for applications that require
advanced routing, support for containers, and WebSocket protocols?

A) Application Load Balancer (ALB).

B) Classic Load Balancer (CLB).

C) Network Load Balancer (NLB).

D) Elastic Load Balancer (ELB).

Answer: A) Application Load Balancer (ALB).

Explanation: The Application Load Balancer (ALB) is recommended for applications that require
advanced routing, support for containers (using Amazon ECS), and WebSocket protocols. ALB operates at
the application layer (Layer 7) of the OSI model and provides more advanced load balancing capabilities
for modern web applications.

**Question 4: Which Elastic Load Balancer (ELB) type can route traffic based on IP addresses in the
incoming request?

A) Application Load Balancer (ALB).

B) Classic Load Balancer (CLB).

C) Network Load Balancer (NLB).

D) Elastic Load Balancer (ELB).

Answer: C) Network Load Balancer (NLB).

Explanation: The Network Load Balancer (NLB) can route traffic based on IP addresses in the incoming
request. This feature allows you to implement Network Address Translation (NAT) scenarios or use cases
that require source IP preservation.

Question 5: What happens to connections established with instances that are deregistered from an
Elastic Load Balancer (ELB)?
A) The connections will be closed immediately, and clients will have to reconnect.

B) The connections will be paused and resume once the instances are re-registered.

C) The connections will be terminated gracefully, and clients will receive an error message.

D) The connections will remain active, and ELB will continue routing requests to the deregistered
instances.

Answer: A) The connections will be closed immediately, and clients will have to reconnect.

Explanation: When instances are deregistered from an Elastic Load Balancer (ELB), the connections
established with those instances will be closed immediately. Clients will have to reconnect, and ELB will
stop routing requests to the deregistered instances.

Question 6: Which Elastic Load Balancer (ELB) type is capable of handling millions of requests per second
while maintaining low latencies?

A) Application Load Balancer (ALB).

B) Classic Load Balancer (CLB).

C) Network Load Balancer (NLB).

D) Elastic Load Balancer (ELB).

Answer: C) Network Load Balancer (NLB).

Explanation: The Network Load Balancer (NLB) is capable of handling millions of requests per second
while maintaining low latencies. It is designed for high-throughput, low-latency use cases, making it ideal
for applications with extreme performance requirements.

Question 1: Which Elastic Load Balancer (ELB) type provides support for distributing traffic to targets in
multiple AWS accounts and across different regions?

A) Application Load Balancer (ALB).

B) Classic Load Balancer (CLB).

C) Network Load Balancer (NLB).

D) Gateway Load Balancer (GWLB).

Answer: D) Gateway Load Balancer (GWLB).

Explanation: The Gateway Load Balancer (GWLB) is a new type of Elastic Load Balancer that is designed
to work with AWS Transit Gateway. It provides support for distributing traffic to targets in multiple AWS
accounts and across different regions connected to the Transit Gateway.

Question 2: Which Elastic Load Balancer (ELB) type provides a static IP address that you can associate
with your load balancer and that remains the same even when the load balancer scales up or down?

A) Application Load Balancer (ALB).

B) Classic Load Balancer (CLB).

C) Network Load Balancer (NLB).

D) Elastic Load Balancer (ELB).

Answer: C) Network Load Balancer (NLB).

Explanation: The Network Load Balancer (NLB) provides a static IP address (Elastic IP) that you can
associate with your load balancer. This IP address remains the same even when the load balancer scales
up or down, providing a fixed entry point for your applications.

Question 3: Which Elastic Load Balancer (ELB) type allows you to use AWS WAF (Web Application
Firewall) to protect your applications from common web exploits and attacks?

A) Application Load Balancer (ALB).

B) Classic Load Balancer (CLB).

C) Network Load Balancer (NLB).

D) Elastic Load Balancer (ELB).

Answer: A) Application Load Balancer (ALB).

Explanation: The Application Load Balancer (ALB) allows you to use AWS WAF (Web Application Firewall)
to protect your applications from common web exploits and attacks. You can configure AWS WAF rules to
filter and monitor incoming HTTP/HTTPS requests before they reach your application servers.

Question 4: Which Elastic Load Balancer (ELB) type is best suited for use cases that require static IP
addresses for your load balancer, such as applications with whitelisting requirements?

A) Application Load Balancer (ALB).

B) Classic Load Balancer (CLB).

C) Network Load Balancer (NLB).

D) Elastic Load Balancer (ELB).

Answer: C) Network Load Balancer (NLB).

Explanation: The Network Load Balancer (NLB) is best suited for use cases that require static IP addresses
for your load balancer. If your applications have whitelisting requirements or rely on fixed IP addresses,
NLB is the recommended choice.

Question 5: How does Elastic Load Balancing (ELB) support the encryption of data in transit between
clients and the load balancer?

A) ELB automatically encrypts the data in transit using AES-256 encryption.

B) ELB supports SSL/TLS termination, which enables encryption between clients and the load balancer.

C) ELB supports IPsec VPN tunnels for secure communication between clients and the load balancer.

D) ELB does not provide encryption capabilities; it relies on the clients to encrypt the data.

Answer: B) ELB supports SSL/TLS termination, which enables encryption between clients and the load
balancer.
Explanation: Elastic Load Balancing (ELB) supports SSL/TLS termination, which allows the load balancer
to handle the SSL/TLS handshake with clients and establish secure encrypted connections. The
communication between clients and the load balancer is encrypted using SSL/TLS.

Question 6: What is the purpose of the "stickiness" feature in Elastic Load Balancing (ELB)?

A) To ensure that instances maintain a consistent level of CPU utilization during traffic spikes.

B) To allow clients to establish persistent connections with specific EC2 instances.

C) To enable load balancer components to "stick" together for better performance.

D) To ensure that all requests from the same client are routed to the same target for session persistence.

Answer: D) To ensure that all requests from the same client are routed to the same target for session
persistence.

Explanation: The "stickiness" feature in Elastic Load Balancing (ELB) allows for session persistence. When
enabled, ELB ensures that all requests from the same client are routed to the same target (EC2 instance)
throughout the duration of a user's session. This is useful for maintaining session state and preventing
session-related issues in stateful applications.