What could be the cause?
A. The load balancer performed a health check on the application and found that compute instances were not in a healthy state and terminated the instances.
B. The security lists of the subnets on which the two instances are located do not have "allow" rules for port 80 and 443.
C. The client requested https access to the application and the load balancer service does not support end-to-end SSL from the client to the listener to the back-end set.
D. The Dynamic Routing Gateway is preventing the client traffic from your data center network from reaching the public IP of the load balancer.
Answer:B
What could be the cause?
A. The load balancer performed a health check on the application and found that compute instances were not in a healthy state and terminated the instances. B. The security lists of the subnets on which the two instances are located do not have "allow" rules for port 80 and 443. C. The client requested https access to the application and the load balancer service does not support end-to-end SSL from the client to the listener to the back-end set. D. The Dynamic Routing Gateway is preventing the client traffic from your data center network from reaching the public IP of the load balancer.