Scenario: A Citrix Administrator created an SSL virtual server using only the commands below: The SSL virtual server is currently in a DOWN state. What could be the reason the SSL virtual server is…

Question

Exhibit

Options

• ASSLv3 is disabled.
• BThe SSL certificate is NOT bound to the virtual server.
• CThe virtual server SSL port is NOT set to port 443.
• DThe SSL services are NOT on the 10.102.29.X network.

• A
  4% (2)
• B
  71% (37)
• C
  17% (9)
• D
  8% (4)

Explanation

An SSL virtual server on Citrix NetScaler/ADC requires a certificate-key pair to be bound before it can transition to an UP state - without it, the virtual server cannot perform SSL handshakes, so it stays DOWN regardless of other configuration. Option A is wrong because disabling SSLv3 doesn't cause a DOWN state; the virtual server will still negotiate using TLS protocols. Option C is wrong because port 443 is conventional but not mandatory - you can configure SSL on any port, and the port choice doesn't affect UP/DOWN state. Option D is wrong because network placement of backend services may affect service availability, but the virtual server itself goes DOWN due to missing certificate binding, not network topology.

Memory tip: Think "no cert = no service." An SSL virtual server is like a HTTPS doorman who refuses to work without ID (the certificate) - until you bind a valid certificate-key pair with bind ssl vserver, the doorman stays off duty (DOWN).

No community discussion yet for this question.