Elastic Load Balancing (ELB)

Question 1

For web apps, microservices & containers

Primarily used for load balancing HTTP and HTTPS traffic

Answer 1

Application Load Balancer (ALB)

Question 2

Handling millions of requests per second while maintaining ultra-low latencies

For load balancing TCP. UDP, and TLS traffic

Answer 2

Network Load Balancer (NLB)

Question 3

Running third party virtual appliances in AWS

Suitable for custom firewalls, deep packet inspection systems, intrusion detection & prevention systems and many other virtual appliances

Answer 3

Gateway Load Balancer (GWLB)

Question 4

For legacy applications in AWS

For implementing Custom Security Policies and TCP passthrough configuration

No recommended for modern applications

Answer 4

Classic Load Balancer (CLB)

Question 5

Can only route traffic in a single AWS Region

Answer 5

ELB

Question 6

Can route traffic to multiple AWS Regions

Answer 6

Route 53

Question 7

Can you directly install cloudwatch log agent to an application load balancer?

Answer 7

No, this is commonly installed on an Amazon EC2 Instance.

Question 8

Does CloudWatch metrics track actual traffic to your ALB?

Answer 8

No, it only monitors the changes to your ALB itself and the actual IP traffic that it distributes to the target groups

Question 9

Can you use AWS CloudTrail to get detailed information of all HTTP requests of a ALB?

Answer 9

No, CloudTrail can only track the resource changes made to your ALB, but not the actual IP traffic that goes through it.

Question 10

Capture detailed information about the requests made to your load Balancer and store them as log files in S3.

Answer 10

Access logs