Bird
0
0

An Application Load Balancer is set with HTTPS listener on port 443 and forwards traffic to backend instances on HTTPS port 8443. Clients report SSL errors. What is the likely cause?

medium📝 Debug Q7 of 15
AWS - Elastic Load Balancing
An Application Load Balancer is set with HTTPS listener on port 443 and forwards traffic to backend instances on HTTPS port 8443. Clients report SSL errors. What is the likely cause?
ALoad balancer listener missing SSL certificate
BBackend instances listening on HTTP port 80
CBackend instances use self-signed certificates not trusted by the load balancer
DSecurity group blocking inbound port 443
Step-by-Step Solution
Solution:
  1. Step 1: Check listener SSL certificate requirement

    HTTPS listener requires a valid SSL certificate attached to terminate SSL from clients.
  2. Step 2: Identify impact of backend certificate trust

    Load balancer must trust backend certificates; self-signed certs cause SSL errors.
  3. Final Answer:

    Backend instances use self-signed certificates not trusted by the load balancer -> Option C
  4. Quick Check:

    Backend cert trust required for HTTPS target group [OK]
Quick Trick: Backend certs must be trusted by load balancer [OK]
Common Mistakes:
MISTAKES
  • Ignoring SSL certificate attachment on listener
  • Assuming backend protocol causes client SSL errors
  • Confusing listener port with certificate issues

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes