Which solution will meet these requirements?
Create an Application Load Balancer that has one HTTPS listener on port 80. Attach an SSL/TLS certificate to listener port 80. Create a rule to redirect requests from HTTP to HTTPS.
Create an Application Load Balancer that has one HTTP listener on port 80 and one HTTPS protocol listener on port 443. Attach an SSL/TLS certificate to listener port 443. Create a rule to redirect requests from port 80 to port 443.
Create an Application Load Balancer that has two TCP listeners on port 80 and port 443. Attach an SSL/TLS certificate to listener port 443. Create a rule to redirect requests from port 80 to port 443.
Create a Network Load Balancer that has two TCP listeners on port 80 and port 443. Attach an SSL/TLS certificate to listener port 443. Create a rule to redirect requests from port 80 to port 443.
Explanations:
An Application Load Balancer should not use HTTPS on port 80. HTTPS is typically configured on port 443. Listener port 80 should be HTTP, and HTTP-to-HTTPS redirection is done from port 80 to port 443.
This option correctly configures an Application Load Balancer with HTTP on port 80 and HTTPS on port 443. It also attaches the SSL/TLS certificate to the HTTPS listener and includes a redirection rule from HTTP to HTTPS.
An Application Load Balancer uses HTTP/HTTPS protocols, not TCP. The use of TCP listeners on port 80 and port 443 does not allow for automatic HTTP-to-HTTPS redirection.
A Network Load Balancer works at the TCP layer and cannot perform HTTP-to-HTTPS redirection. Additionally, it does not support HTTP/HTTPS listener rules like an Application Load Balancer.