To consolidate multiple domain names behind a single SSL virtual server, which certificate type should be bound?

To consolidate multiple domain names behind a single SSL virtual server, which certificate type should be bound?

• A. Bind a certificate for each website to the SSL virtual server.
• B. Bind a SAN certificate to a single SSL virtual server.
• C. Bind a Wildcard certificate to a single SSL virtual server.
• D. Bind a Wildcard certificate to a Content Switching virtual server.

Answer: (B)

Consolidating multiple domain names behind one SSL vserver relies on using a certificate that lists all the names it should cover. A SAN (Subject Alternative Name) certificate includes several DNSNames in the certificate itself, so binding that single certificate to one SSL virtual server lets that vserver terminate TLS for any of the included domains without needing separate certificates or vservers for each domain. Wildcard certificates can cover subdomains of one base domain, but they don’t cover multiple, different base domains. Binding a wildcard to a Content Switching vserver isn’t addressing the TLS termination for all those domains on one SSL vserver. So a SAN certificate bound to a single SSL vserver is the right choice.

Consolidating multiple domain names behind one SSL vserver relies on using a certificate that lists all the names it should cover. A SAN (Subject Alternative Name) certificate includes several DNSNames in the certificate itself, so binding that single certificate to one SSL virtual server lets that vserver terminate TLS for any of the included domains without needing separate certificates or vservers for each domain. Wildcard certificates can cover subdomains of one base domain, but they don’t cover multiple, different base domains. Binding a wildcard to a Content Switching vserver isn’t addressing the TLS termination for all those domains on one SSL vserver. So a SAN certificate bound to a single SSL vserver is the right choice.