Elastic Load Balancing (ELB) test - AWS Certified Solutions Architect - Associate questions

Question 1

What is the maximum number of listeners that can be configured on a load balancer?

One listener only None - there is no specified limit Five listeners Ten listeners

Correct Answer: None - there is no specified limit

AWS does not impose any limit on the number of listeners that can be configured on an Elastic Load Balancer. However, it is a good practice to only configure the listeners that are necessary for the application to function properly, as each listener adds some overhead to the load balancer's processing.

Question 2

What is the difference between Auto Scaling and Elastic Load Balancing (ELB)?

Auto Scaling is a service that automatically encrypts incoming and outgoing traffic between instances, while ELB distributes traffic evenly across instances to avoid overloading any single instance. Auto Scaling and Elastic Load Balancing (ELB) are two different but complementary services that work together to ensure that an application provides a consistent user experience. Auto Scaling is a service that automatically adjusts the number of instances running in response to changes in traffic patterns, while ELB distributes traffic evenly across instances to avoid overloading any single instance. Auto Scaling is a service that automatically distributes traffic evenly across instances to avoid overloading any single instance, while ELB adjusts the number of instances running in response to changes in traffic patterns. Auto Scaling is a service that automatically balances the distribution of resources across instances to ensure the best possible performance, while ELB adjusts the number of instances running in response to changes in traffic patterns.

Correct Answer: Auto Scaling and Elastic Load Balancing (ELB) are two different but complementary services that work together to ensure that an application provides a consistent user experience. Auto Scaling is a service that automatically adjusts the number of instances running in response to changes in traffic patterns, while ELB distributes traffic evenly across instances to avoid overloading any single instance.

Auto Scaling and Elastic Load Balancing are two complementary services that work together to scale applications and ensure a consistent user experience. Auto Scaling automatically adjusts the number of instances running based on changes in traffic patterns, while Elastic Load Balancing evenly distributes traffic across instances to avoid overloading any single instance. When used together, these services provide the best possible user experience by ensuring that an application is always running on the right number of instances and that traffic is distributed evenly across those instances.

Question 3

What is the purpose of a health check in Elastic Load Balancing (ELB)?

A health check is a way to limit the number of sessions an Elastic Load Balancer can handle. By setting a session limit, you can prevent server overload and improve application performance. A health check is a periodic test that determines whether an instance is available to receive traffic from the Elastic Load Balancer. A failing health check can trigger ELB to stop sending traffic to an unhealthy target instance. A health check is a way to provide application-level encryption using the Elastic Load Balancer. This protects user data by encrypting traffic between the load balancer and users. A health check is a way to enable sticky sessions in Elastic Load Balancer. This ensures that traffic is sent to the same instance during a single user's session, improving application performance.

Correct Answer: A health check is a periodic test that determines whether an instance is available to receive traffic from the Elastic Load Balancer. A failing health check can trigger ELB to stop sending traffic to an unhealthy target instance.

In Elastic Load Balancing, a health check is used to determine whether an instance is healthy and available to receive incoming traffic. The health check monitors the status of the instance by sending a request to the instance and checking the response. If the response is successful, the instance is marked as healthy, and traffic is sent to it. If the response is unsuccessful, the instance is marked as unhealthy, and traffic is not sent to it. The health check is a critical component of Elastic Load Balancing as it ensures that traffic is routed only to healthy instances, thereby reducing the risk of application downtime and improving user experience.

Elastic Load Balancing (ELB)

AWS Certified Solutions Architect - Elastic Load Balancing (ELB) Example Questions

Question 1

Question 2

Question 3

Unlock Premium Access