You configured a health check with TimeoutSeconds set to 10 seconds, but your service responds in 3 seconds. The health check still fails. What is the most likely cause?

medium📝 Debug Q14 of 15

AWS - Elastic Load Balancing

You configured a health check with TimeoutSeconds set to 10 seconds, but your service responds in 3 seconds. The health check still fails. What is the most likely cause?

AHealthyThresholdCount is set too low

BTimeoutSeconds is too high causing failure

CThe health check path is incorrect or unreachable

DIntervalSeconds is set to 1 second

Step-by-Step Solution

Solution:

Step 1: Analyze TimeoutSeconds vs response time
TimeoutSeconds is 10, service responds in 3 seconds, so timeout is not the issue.
Step 2: Consider other causes for failure
If health check fails despite quick response, likely the path is wrong or the service is unreachable.
Final Answer:
The health check path is incorrect or unreachable -> Option C
Quick Check:
Fast response but failure = wrong path/unreachable [OK]

Quick Trick: Fast response but failure? Check health check path [OK]

Common Mistakes:

MISTAKES

Assuming timeout too high causes failure
Confusing threshold counts with timeout
Ignoring path correctness

Master "Elastic Load Balancing" in AWS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More AWS Quizzes

You configured a health check with TimeoutSeconds set to 10 seconds, but your service responds in 3 seconds. The health check still fails. What is the most likely cause?

Step 1: Analyze TimeoutSeconds vs response time

Step 2: Consider other causes for failure

Final Answer:

Quick Check:

Want More Practice?