Load Balancer

Question 1

An e-commerce website is migrating towards a microservices-based approach for their website and plans to expose their website from the same load balancer, linked to different target groups with different URLs: checkout.mycorp.com, www.mycorp.com, mycorp.com/products, and mycorp.com/orders. The website would like to use ECS on the backend to manage these microservices and possibly host the same container of the application multiple times on the same EC2 instance.

Which load balancer (application, network, or classic) will be the easiest to use?

Answer 1

Application Load Balancer can automatically distribute incoming application traffic across multiple targets, such as Amazon EC2 instances, containers, IP addresses, and Lambda functions. It can handle the varying load of your application traffic in a single Availability Zone or across multiple Availability Zones.

Dynamic port mapping with an Application Load Balancer makes it easier to run multiple tasks on the same Amazon ECS service on an Amazon ECS cluster.

Question 2

True or False

ELB cannot distribute incoming traffic for targets deployed in different regions

Answer 2

True

Question 3

True or False

Can you define a Network ACL (NACL) on your Application Load Balancer?

Answer 3

False

NACLs are defined at the subnet level, not Application Load Balancers.

Question 4

What is the best firewall option for scenario below?

Your application is deployed on EC2 instances fronted by an Application Load Balancer. Recently, your infrastructure has come under attack. Attackers perform over 100 requests per second, while your normal users only make about 5 requests per second.

How can you efficiently prevent attackers from overwhelming your application?

Answer 4

Web Application Firewall