What is the cause?

You have enabled Elastic Load Balancing HTTP health checking. After looking at the AWS Management Console, you
see that all instances are passing health checks, but your customers are reporting that your site is not responding. What
is the cause?

You have enabled Elastic Load Balancing HTTP health checking. After looking at the AWS Management Console, you
see that all instances are passing health checks, but your customers are reporting that your site is not responding. What
is the cause?

A.
The HTTP health checking system is misreporting due to latency in inter-instance metadata synchronization.

B.
The health check in place is not sufficiently evaluating the application function.

C.
The application is returning a positive health check too quickly for the AWS Management Console to respond.

D.
Latency in DNS resolution is interfering with Amazon EC2 metadata retrieval.



Leave a Reply 4

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


BTuan

BTuan

It seems B is the best
B. because ELB healthcheck just check 1 page that user pre-config, other pages may be still error occured.

Sadeel Anjum

Sadeel Anjum

B.
We need custom health to monitor the application function so in default state B is the best answer.