Compute - Classic Load Balancers Flashcards
1
Q
What protocols are supported by the Classic Load Balancer?
A
- The Classic Load Balancer supports TCP, SSL/TLS, HTTP, and HTTPS protocols.
2
Q
When is it recommended to use the Classic Load Balancer?
A
- It is recommended to use the Classic Load Balancer only if you have an existing application running in the EC2-Classic network.
3
Q
What is the EC2-Classic platform?
A
- The EC2-Classic platform was introduced when the first release of EC2 was made generally available. It allows deploying EC2 instances in a single flat network shared with other customers instead of inside a VPC.
4
Q
What are the features of the Classic Load Balancer that the Application Load Balancer (ALB) does not have?
A
- Supports EC2-Classic platform.
- Supports TCP and SSL listeners.
- Has support for sticky sessions using application-generated cookies.
5
Q
Can cross-zone load balancing be enabled or disabled for the Classic Load Balancer?
A
- Yes, cross-zone load balancing for the Classic Load Balancer can be either enabled or disabled.
6
Q
How can you create a Classic Load Balancer in the AWS Management Console?
A
- Go to the EC2 service under Compute.
- Under Load Balancing, click on Load Balancers.
- Click on Create Load Balancer.
- Select Classic Load Balancer and follow the configuration steps, including naming, selecting the VPC, defining listeners, selecting availability zones, configuring security settings, setting up health checks, adding EC2 instances, adding tags, reviewing the configuration, and creating the load balancer.
7
Q
What are the differences between the Classic Load Balancer, Application Load Balancer (ALB), and Network Load Balancer (NLB)?
A
- The ALB is the most feature-rich load balancer.
- The NLB supports features such as static IPs, Elastic IPs, and preserving source IP addresses.
- The Classic Load Balancer supports the EC2-Classic platform and TCP/SSL listeners but has fewer features compared to ALB and NLB.