In IIS 7.0, what does SSL certificate binding accomplish?

In IIS 7.0, what does SSL certificate binding accomplish?

• A. It binds IP addresses to domains only.
• B. It binds an SSL certificate to a site/port to enable HTTPS, securing web traffic.
• C. It creates a new certificate signing request.
• D. It enables HTTP only.

Answer: (B)

SSL certificate binding in IIS 7.0 ties a specific certificate to a particular site and port so HTTPS traffic can be encrypted. When a client connects to that site on the designated port (usually 443), IIS uses the bound certificate to perform the TLS handshake, proving the server’s identity and encrypting the data in transit. This binding is what actually enables secure web traffic for that site; without it, HTTPS cannot be established for that site. It doesn’t create a certificate signing request, and it isn’t about binding IPs to domains or enabling HTTP only. Note that in IIS 7.0 you typically bind a certificate to a given IP:port combination, since SNI isn’t available there.

SSL certificate binding in IIS 7.0 ties a specific certificate to a particular site and port so HTTPS traffic can be encrypted. When a client connects to that site on the designated port (usually 443), IIS uses the bound certificate to perform the TLS handshake, proving the server’s identity and encrypting the data in transit. This binding is what actually enables secure web traffic for that site; without it, HTTPS cannot be established for that site. It doesn’t create a certificate signing request, and it isn’t about binding IPs to domains or enabling HTTP only. Note that in IIS 7.0 you typically bind a certificate to a given IP:port combination, since SNI isn’t available there.