Scenario: Users are trying to access https://cs.mycompany.com, but are receiving the error below: HTTP 503 Service Unavailable What can a Citrix Administrator change in the Citrix ADC configuration…

Question

Options

• ABind the default load-balancing vServer.
• BEnable the content switching feature.
• CDisable the spillover redirect URL.
• DBind a certificate.

• A
  4% (1)
• B
  78% (18)
• C
  4% (1)
• D
  13% (3)

Explanation

Enabling the content switching feature is correct because Citrix ADC requires features to be explicitly enabled before they function - if content switching is disabled at the system level, any content switching vServer will return HTTP 503 Service Unavailable, regardless of how it's configured. The hostname cs.mycompany.com is a strong hint that a content switching vServer is involved, and the fix is simply running enable ns feature CS (or enabling it via the GUI).

Why the distractors are wrong:

• A (Bind default LB vServer): A missing default load-balancing vServer causes unmatched traffic to be dropped or misdirected - not a blanket 503 on the vServer itself.
• C (Disable spillover redirect URL): Spillover redirect only applies when a vServer hits a capacity threshold; it has no bearing on a vServer failing to respond due to a disabled feature.
• D (Bind a certificate): A missing SSL certificate on an HTTPS vServer causes an SSL/TLS handshake failure, not a 503 - and the vServer must be operational for SSL errors to even occur.

Memory tip: Anytime you see a 503 on a vServer that "should work" with all policies and services configured, think "feature not enabled." In Citrix ADC, features (CS, LB, Rewrite, Responder, etc.) are off by default - 503 is the ADC's way of saying "I don't know what to do with this traffic."

No community discussion yet for this question.