Balancer (ALB) is configured with a single HTTP 80 listener. A SysOps administrator must ensure The SysOps administrator already has requested and validated a public certificate for be required to…

Question

Options

• ACreate an additional ALB listener for HTTPS on port 443. Set the default action to forward all
• BCreate an additional ALB listener for HTTPS on port 443. Set the default action to forward all
• CModify the ALB default rule for the HTTP port 80 listener. Create a rule in the listener to forward
• DModify the ALB default rule for the HTTP port 80 listener to redirect to HTTPS on port 443. Create

• A
  3% (2)
• B
  12% (7)
• C
  8% (5)
• D
  77% (46)

Explanation

Option D is correct because it satisfies both requirements: users continue connecting to the same HTTP port 80 endpoint (no change needed on their end), while the ALB silently redirects that traffic to HTTPS 443 - combined with a new HTTPS 443 listener that forwards to the target group, this enforces encryption end-to-end.

Options A and B are wrong because simply adding an HTTPS 443 listener without modifying the HTTP 80 listener means users would have to manually update their endpoint from http:// to https:// - violating the "no endpoint change" requirement.

Option C is wrong because forwarding on port 80 keeps traffic on plain HTTP; it never enforces HTTPS. A "forward" action sends traffic to a target group as-is, while a "redirect" action changes the protocol/port before passing the request along.

Memory tip: Think "80 redirects, 443 forwards." The HTTP listener's job is to redirect (bounce the user to HTTPS), and the HTTPS listener's job is to forward (deliver traffic to your backend). If you mix those up, you either stay on HTTP or force users to update their bookmarks.

No community discussion yet for this question.