Explanation:
The security group of the EC2 instance does not allow for traffic from the security group of the Application Load Balancer
The route for the health check is misconfigured
You must ensure that your load balancer can communicate with registered targets on both the listener port and the health check port. Whenever you add a listener to your load balancer or update the health check port for a target group used by the load balancer to route requests, you must verify that the security groups associated with the load balancer allow traffic on the new port in both directions.
Ultimate access to all questions.
No comments yet.
You have set up an Elastic Load Balancer (ELB) to distribute traffic among several EC2 instances. However, the ELB has flagged all of your EC2 instances in the target group as unhealthy. Despite this, you are still able to access the website directly by entering the IP addresses of the EC2 instances into your web browser.
What might be the causes for the ELB marking your instances as unhealthy? (Select two)
A
Your web-app has a runtime that is not supported by the Application Load Balancer
B
The route for the health check is misconfigured
C
The EBS volumes have been improperly mounted
D
ou need to attach Elastic IP to the EC2 instances
E
The security group of the EC2 instance does not allow for traffic from the security group of the Application Load Balancer