PrepAway - Latest Free Exam Questions & Answers

Which options are probable causes of this behavior?

You have a load balancer configured for VPC, and all back-end Amazon EC2 instances are in service. However,
your web browser times out when connecting to the load balancer’s DNS name. Which options are probable
causes of this behavior? Choose 2 answers

PrepAway - Latest Free Exam Questions & Answers

A.
The load balancer was not configured to use a public subnet with an Internet gateway configured

B.
The Amazon EC2 instances do not have a dynamically allocated private IP address

C.
The security groups or network ACLs are not property configured for web traffic.

D.
The load balancer is not configured in a private subnet with a NAT instance.

E.
The VPC does not have a VGW configured.

20 Comments on “Which options are probable causes of this behavior?

  1. samiran mondal says:

    I am confused.Somewhere else I have got answer as A and C. Please let me know which one is correct with proper document link




    0



    0
  2. T says:

    I was wrong,
    B is wrong (ELB don`t need EC2 to have public IP to send traffic to it),
    A and C should be right answers




    0



    0
  3. Arun says:

    A & E are pretty much means the same thing. Not sure why picked A and not E.
    Both will result in ELB not reachable as the VPC used is not connected to internet (Not public).

    Any reasoning that help me understand the difference?




    0



    0
  4. JERRY says:

    For A, I don’t recall in any of the LAB for Load Balancer, we need to attach a Internet GW to a public subnet in order for it to work. We just need to apply the LB in the VPC and it will be assigned a DNS link automatically.




    0



    0

Leave a Reply

Your email address will not be published. Required fields are marked *