You created a Route 53 health check for an HTTPS endpoint on port 443, but Route 53 always marks it unhealthy even though the site is up. What is the most likely cause?

medium📝 Debug Q14 of 15

AWS - Route 53

AThe health check is set to HTTP instead of HTTPS

BThe failure threshold is set too high

CThe endpoint is using port 80 instead of 443

DThe health check is configured with TCP protocol

Step-by-Step Solution

Solution:

Step 1: Check protocol mismatch
If the health check is set to HTTP but the endpoint requires HTTPS, the check will fail.
Step 2: Confirm correct protocol and port
HTTPS requires protocol HTTPS and port 443; using HTTP protocol causes failure.
Final Answer:
The health check is set to HTTP instead of HTTPS -> Option A
Quick Check:
Protocol mismatch causes failure [OK]

Quick Trick: Match protocol exactly with endpoint [OK]

Common Mistakes:

Ignoring protocol and port mismatch
Assuming failure threshold causes failure
Confusing TCP with HTTPS protocol

Master "Route 53" 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 created a Route 53 health check for an HTTPS endpoint on port 443, but Route 53 always marks it unhealthy even though the site is up. What is the most likely cause?

Step 1: Check protocol mismatch

Step 2: Confirm correct protocol and port

Final Answer:

Quick Check:

Want More Practice?