A company plans to run a public web application on Amazon EC2 instances behind an Elastic Load Balancer (ELB). The company's security team wants to protect the website by using AWS Certificate…

Question

Options

• ACreate an Application Load Balancer that has one HTTPS listener on port 80.
• BCreate an Application Load Balancer that has one HTTP listener on port 80 and one HTTPS
• CCreate an Application Load Balancer that has two TCP listeners on port 80 and port 443.
• DCreate a Network Load Balancer that has two TCP listeners on port 80 and port 443.

• A
  8% (5)
• B
  82% (51)
• C
  3% (2)
• D
  6% (4)

Explanation

Option B is correct because an Application Load Balancer (ALB) supports ACM certificate integration on HTTPS listeners and allows you to configure an HTTP listener on port 80 with a redirect rule to HTTPS on port 443 - this is the standard AWS pattern for enforcing encrypted traffic.

Why the others are wrong:

• A is wrong because port 80 is the HTTP port; you cannot attach an ACM certificate to a plain HTTP listener, and a single listener cannot redirect to itself.
• C is wrong because TCP listeners (used for pass-through traffic) do not support ACM certificates or HTTP-to-HTTPS redirect rules - that requires HTTP/HTTPS listener types.
• D is wrong for the same reason as C: Network Load Balancers use TCP/TLS listeners and do not natively support HTTP-level redirect logic or ACM-managed certificate termination in the same way ALBs do.

Memory tip: Think "ALB = Application layer = HTTP/HTTPS awareness." Only an ALB understands HTTP semantics well enough to inspect a request and redirect it - an NLB operates at Layer 4 (TCP) and has no concept of "redirect this HTTP request to HTTPS."

No community discussion yet for this question.