An Application Load Balancer is set with an HTTPS listener on port 443 and a valid SSL certificate, but clients receive SSL handshake failures. What is a probable cause?

medium📝 Debug Q6 of 15

AWS - Elastic Load Balancing

AThe backend instances are running HTTP instead of HTTPS

BThe SSL certificate is expired or not trusted by clients

CThe load balancer listener is configured on port 80 instead of 443

DThe security group allows only HTTP traffic

Step-by-Step Solution

Solution:

Step 1: Check SSL certificate validity
Expired or untrusted certificates cause SSL handshake failures.
Step 2: Confirm listener port and protocol
Listener is correctly set to HTTPS on port 443, so this is not the issue.
Step 3: Backend protocol mismatch
Backend protocol mismatch usually causes application errors, not SSL handshake failures.
Final Answer:
The SSL certificate is expired or not trusted by clients -> Option B
Quick Check:
SSL handshake fails if cert invalid or expired [OK]

Quick Trick: SSL handshake fails if certificate is invalid or expired [OK]

Common Mistakes:

Assuming backend protocol causes SSL handshake failure
Ignoring certificate expiration
Confusing listener port with backend port

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

An Application Load Balancer is set with an HTTPS listener on port 443 and a valid SSL certificate, but clients receive SSL handshake failures. What is a probable cause?

Step 1: Check SSL certificate validity

Step 2: Confirm listener port and protocol

Step 3: Backend protocol mismatch

Final Answer:

Quick Check:

Want More Practice?