AWS - Study Group 1 Elastic Load Balancer

Question 1

Which operating systems does the Classic Load Balancer support?

Answer 1

The Classic Load Balancer supports Amazon EC2 instances with any operating system currently supported by the Amazon EC2 service.

Question 2

Which protocols does the Classic Load Balancer support?

Answer 2

The Classic Load Balancer supports load balancing of applications using HTTP, HTTPS (Secure HTTP), SSL (Secure TCP) and TCP protocols.

Question 3

what three types of Load Balancers are there?

Answer 3

Application Load Balancer
Network Load Balancer
Classic Load Balancer

Question 4

You can create, access, and manage your load balancers using any of the following interfaces. T or F

AWS Management Console
AWS Command Line Interface (AWS CLI)
AWS SDKs
Query API

Answer 4

True

You can create, access, and manage your load balancers using any of the following interfaces:

AWS Management Console— Provides a web interface that you can use to access Elastic Load Balancing.
AWS Command Line Interface (AWS CLI) — Provides commands for a broad set of AWS services, including Elastic Load Balancing, and is supported on Windows, Mac, and Linux. For more information, see AWS Command Line Interface.
AWS SDKs — Provides language-specific APIs and takes care of many of the connection details, such as calculating signatures, handling request retries, and error handling. For more information, see AWS SDKs.
Query API— Provides low-level API actions that you call using HTTPS requests. Using the Query API is the most direct way to access Elastic Load Balancing, but it requires that your application handle low-level details such as generating the hash to sign the request, and error handling. For more information, see the following:
Application Load Balancers and Network Load Balancers — API version 2015-12-01
Classic Load Balancers — API version 2012-06-01

Question 5

What TCP ports can I load balance?

Answer 5

You can perform load balancing for the following TCP ports:

[EC2-VPC] 1-65535
[EC2-Classic] 25, 80, 443, 465, 587, 1024-65535

Question 6

Does the Classic Load Balancer support IPv6 traffic?

Answer 6

Yes. Each Classic Load Balancer has an associated IPv4, IPv6, and dualstack (both IPv4 and IPv6) DNS name. IPv6 is not supported in VPC. You can use an Application Load Balancer for native IPv6 support in VPC.

Question 7

This type of ELB routes traffic based on either application or network level information

Answer 7

Classic Load Balancer

Question 8

This type of ELB routes traffic based on advanced application level information that includes the content of the request.

Answer 8

Application Load Balancer

Question 9

this Load Balancer is ideal for applications needing advanced routing capabilities, microservices, and container-based architectures.

Answer 9

Automatic

Question 10

This Load Balancer is ideal for simple load balancing of traffic across multiple EC2 instances

Answer 10

Classic

Question 11

Can I migrate to Network Load Balancer from Classic Load Balancer?

Answer 11

Yes. You can migrate to Network Load Balancer from Classic Load Balancer using one of the options listed in this document.

Question 12

Can I use the existing API for Classic Load Balancers for my Network Load Balancers?

Answer 12

No. To create a Classic Load Balancer, use the 2012-06-01 API. To create a Network Load Balancer or an Application Load Balancer, use the 2015-12-01 API.

Question 13

Can I create my Network Load Balancer in a single Availability Zone?

Answer 13

Yes, you can create your Network Load Balancer in a single availability zone by providing a single subnet when you create the load balancer.

Question 14

Can I have a Network Load Balancer with a mix of ELB-provided IPs and Elastic IPs or assigned private IPs?

Answer 14

No. A Network Load Balancer’s addresses must be completely controlled by you, or completely controlled by ELB. This is to ensure that when using Elastic IPs with a Network Load Balancer, all addresses known to your clients do not change.

Question 15

If I remove/delete a Network Load Balancer what will happen to the Elastic IP addresses that were associated with it?

Answer 15

The Elastic IP Addresses that were associated with your load balancer will be returned to your allocated pool and made available for future use.

Question 16

How does Network Load Balancer pricing work?

Answer 16

You are charged for each hour or partial hour that a Network Load Balancer is running and the number of Load Balancer Capacity Units (LCU) used by Network Load Balancer per hour.

Question 17

What is a Load Balancer Capacity Unit (LCU)?

Answer 17

An LCU is a new metric for determining how you pay for a Network Load Balancer. An LCU defines the maximum resource consumed in any one of the dimensions (new connections/flows, active connections/flows, and bandwidth) the Network Load Balancer processes your traffic.

Question 18

Can I get a history of Classic Load Balancer API calls made on my account for security analysis and operational troubleshooting purposes?

Answer 18

Yes. To receive a history of Classic Load Balancer API calls made on your account, simply turn on CloudTrail in the AWS Management Console.

Question 19

Can I use Classic Load Balancers in Amazon Virtual Private Cloud?

Answer 19

Yes – see the Elastic Load Balancing web page.

Question 20

Can I use a single Classic Load Balancer for handling HTTP and HTTPS requests?

Answer 20

Yes, you can map HTTP port 80 and HTTPS port 443 to a single Classic Load Balancer.

Question 21

Can I configure a security group for the front-end of Classic Load Balancers?

Answer 21

If you are using Amazon Virtual Private Cloud, you can configure security groups for the front-end of your Classic Load Balancers.

Question 22

Which operating systems does an Application Load Balancer support?

Answer 22

An Application Load Balancer supports targets with any operating system currently supported by the Amazon EC2 service.

Question 23

Which protocols does an Application Load Balancer support?

Answer 23

An Application Load Balancer supports load balancing of applications using HTTP and HTTPS (Secure HTTP) protocols.

Question 24

Can I configure my Amazon EC2 instances to accept traffic only from my Application Load Balancers?

Answer 24

Yes

Question 25

Can I configure a security group for the front-end of an Application Load Balancer?

Answer 25

Yes

Question 26

Can I use the existing APIs that I use with my Classic Load Balancer with an Application Load Balancer?

Answer 26

No. Application Load Balancers require a new set of APIs.

Question 27

Can I convert my Classic Load Balancer to an Application Load Balancer (and vice versa)?

Answer 27

No, you cannot convert one load balancer type into another.

Question 28

Can I migrate to Application Load Balancer from Classic Load Balancer?

Answer 28

Yes. You can migrate to Application Load Balancer from Classic Load Balancer using one of the options listed in this document.

Question 29

Can I use a single Application Load Balancer for handling HTTP and HTTPS requests?

Answer 29

Yes, you can add listeners for HTTP port 80 and HTTPS port 443 to a single Application Load Balancer

Question 30

Can I get a history of Application Load Balancing API calls made on my account for security analysis and operational troubleshooting purposes?

Answer 30

Yes. To receive a history of Application Load Balancing API calls made on your account, use AWS CloudTrail.

Question 31

Does an Application Load Balancer support HTTPS termination?

Answer 31

Yes, you can terminate HTTPS connection on the Application Load Balancer. You must install an SSL certificate on your load balancer. The load balancer uses this certificate to terminate the connection and then decrypt requests from clients before sending them to targets.

Question 32

Is IPv6 supported with an Application Load Balancer?

Answer 32

es, IPv6 is supported with an Application Load Balancer.

Question 33

How does Application Load Balancer pricing work? (How are you charged?)

Answer 33

You are charged for each hour or partial hour that an Application Load Balancer is running and the number of Load Balancer Capacity Units (LCU) used per hour.