Which binding enables using a wildcard certificate with a content-switching virtual server?

• A. Bind wildcard certificate to a single SSL virtual server
• B. Bind wildcard certificate to a content-switching virtual server
• C. Bind SAN certificate to a content-switching virtual server
• D. Bind per-website certificates to a single virtual server

Answer: (B)

Binding a wildcard certificate to a content-switching virtual server is the setup that makes host-based routing work cleanly at the entry point. The content-switching vserver terminates SSL, then uses policies based on the HTTP host to route requests to the correct backend vservers. A wildcard certificate covers all subdomains (for example, *.example.com), so the same certificate can be presented for any incoming domain under that umbrella, enabling seamless SSL termination and accurate content-based switching for multiple sites behind the same CS vserver.

If you bind the wildcard certificate to a regular SSL vserver, you’re not centralizing SSL termination at the entry point that performs the content switching, which complicates or limits how you route requests based on domain. A SAN certificate could cover multiple names, but the scenario specifically focuses on using a wildcard certificate, so binding it to the content-switching vserver is the most appropriate approach. Binding per-website certificates to a single vserver isn’t scalable for broad host-based switching.