Exam ANS-C01 All QuestionsBrowse all questions from this exam
Go to Exam
Question 138

A company has 10 web server Amazon EC2 instances that run in an Auto Scaling group in a production VPC. The company has 10 other web servers that run in an on-premises data center. The company has a 10 Gbps AWS Direct Connect connection between the on-premises data center and the production VPC.

The company needs to implement a load balancing solution that receives HTTPS traffic from thousands of external users. The solution must distribute the traffic across the web servers on AWS and the web servers in the on-premises data center. Regardless of the location of the web servers, HTTPS requests must go to the same web server throughout the entire session.

Which solution will meet these requirements?

    Correct Answer: B

    The optimal load balancing solution that meets the mentioned requirements involves using an Application Load Balancer (ALB) in the production VPC. The ALB supports specifying IP addresses as targets, which is necessary for load balancing traffic to both EC2 instances and on-premises servers. Additionally, enabling application-based session affinity (sticky sessions) ensures that HTTPS requests from the same user go to the same web server throughout the entire session. Thus, creating an ALB, with a target group specified as IP type, and enabling sticky sessions fulfills all the criteria presented in the question.

Discussion
Josh1217Option: B

Only 'IP' target type will allow load balancing across On-Prem and Cloud. Plus need Stickiness. So Option B.

[Removed]

B route traffic to both EC2 instances and on-premises servers, use IP as the target type https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-target-groups.html

awskiller007

B https://aws.amazon.com/blogs/aws/new-application-load-balancing-via-ip-address-to-aws-on-premises-resources/

ryluisOption: B

ALB support on prem's ip address as a target group, and you need session affinity for this. https://aws.amazon.com/blogs/aws/new-application-load-balancing-via-ip-address-to-aws-on-premises-resources/

PratapOption: B

Applcation LB and IP address in TG

takecoffeOption: C

you need network load balancer to add ips of the onpremise servers

Pratap

on premise instances can be added as targets to ALB

_mavik_Option: B

NLB doesn't support sticky session

AradOption: B

B is the right answer.

JosMoOption: B

aggred on B

Balasmaniam

B is correct ans

AJ7428Option: C

Answer to the key is thousands of users connecting..

AJ7428

changing to Answer B.

Blitz1Option: B

Something is wrong with question or answers. When you create target groups you can specify the target type either: 1) Instances ( and here you can add also EC2 scaling groups) 2) IP Address ( Supports load balancing to VPC and on-premises resources. ) But when you have both EC2 scaling and on-prem IP what can you do ? Plus it is saying "receives HTTPS traffic from thousands of external users" which implies that autoscale should work to accommodate. A very complex solution will be to have ALB in ALB meaning that in the target groups of first ALB you will have IP of the on-prem server and the IP of a load-balancer which includes the EC2 auto-scalling group but it's kinda a nightmare to proper manage this thing but technically possible. So only because of that i will go for B but i strongly believe something is wrong with the question.

Balasmaniam

doubt on answer: C, because when using an instance ID as a target, an EC2 instance could only receive traffic from the load balancer on its primary IP address and primary network interface. This limits hosting multiple applications on the same instance where each application requires different IP address, network interface, or security group. Using IP addresses as targets removes this limitation as the load balancer can route to multiple IP addresses and network interfaces on the same instance.