What binding is required for an SSL vServer to perform TLS handshakes with clients?

• A. Bind a non-SSL service
• B. Bind the SSL certificate to the vServer
• C. Bind the SSL services to an external gateway
• D. Bind DNS to the vServer

Answer: (B)

TLS handshakes require the server to present a valid certificate. On an SSL vServer, you must bind an SSL certificate (and its private key) to the vServer so the TLS stack can present that identity to clients during the handshake. Without a bound certificate, the vServer cannot complete the TLS negotiation, and clients will fail to establish a secure connection. The other options don’t enable TLS handshakes: binding a non-SSL service won’t provide TLS; binding SSL services to an external gateway isn’t how the vServer exposes its certificate; and binding DNS has no effect on the TLS process.