Which operation enables HTTPS on a Citrix ADC site by associating identity with the vServer?

Which operation enables HTTPS on a Citrix ADC site by associating identity with the vServer?

• A. Bind a certificate.
• B. Bind the default load-balancing vServer.
• C. Enable content switching.
• D. Bind a policy to the vServer.

Answer: (A)

Binding an SSL certificate to the vServer is what enables HTTPS by associating the site’s identity with that virtual server. In Citrix ADC, serving HTTPS requires TLS termination at the ADC, which means the ADC must present a valid certificate during the TLS handshake. Binding the certificate (and its private key) to the vServer provides that identity, allowing clients to establish a secure TLS connection with the ADC and access the site securely. The other options don’t enable HTTPS identity: enabling content switching is about routing decisions, binding a policy to the vServer applies traffic rules, and binding the default load-balancing vServer doesn’t configure TLS for the actual site.

Binding an SSL certificate to the vServer is what enables HTTPS by associating the site’s identity with that virtual server. In Citrix ADC, serving HTTPS requires TLS termination at the ADC, which means the ADC must present a valid certificate during the TLS handshake. Binding the certificate (and its private key) to the vServer provides that identity, allowing clients to establish a secure TLS connection with the ADC and access the site securely.

The other options don’t enable HTTPS identity: enabling content switching is about routing decisions, binding a policy to the vServer applies traffic rules, and binding the default load-balancing vServer doesn’t configure TLS for the actual site.