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

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

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.

Explanation:
There is no such thing as VGW. Hence E is not correct answer.



Leave a Reply 1

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


hippo

hippo

VGW is a VPN Gateway. The explanation is rubbish, but the answers are correct.