1Y0-231 · Question #84
The StoreFront service is using SSL and is showing as DOWN. What could be causing this issue?
The correct answer is C. A certificate is NOT bound to the monitor. When a Citrix ADC (NetScaler) monitor communicates with a StoreFront service over SSL, it must present a valid certificate to complete the SSL handshake. Without a certificate bound to the monitor, the SSL negotiation fails entirely, and the ADC marks the service as DOWN - even…
Question
The StoreFront service is using SSL and is showing as DOWN. What could be causing this issue?
Options
- AThe reverse option is NOT enabled.
- BA wildcard certificate is in use.
- CA certificate is NOT bound to the monitor.
- DThe secure checkbox is NOT checked in the StoreFront monitor.
How the community answered
(59 responses)- A5% (3)
- B15% (9)
- C71% (42)
- D8% (5)
Explanation
When a Citrix ADC (NetScaler) monitor communicates with a StoreFront service over SSL, it must present a valid certificate to complete the SSL handshake. Without a certificate bound to the monitor, the SSL negotiation fails entirely, and the ADC marks the service as DOWN - even though StoreFront itself may be running perfectly.
Why the distractors are wrong:
- A (Reverse option not enabled): The reverse option inverts monitor logic (UP becomes DOWN and vice versa). It has nothing to do with SSL connectivity failures.
- B (Wildcard certificate in use): Wildcard certificates are fully valid for SSL monitors. The type of certificate is not the issue - the absence of a bound certificate is.
- D (Secure checkbox not checked): If the Secure checkbox were unchecked, the monitor would send plain HTTP to an HTTPS endpoint - a different kind of failure. The scenario states SSL is in use, meaning Secure is checked; the missing piece is the certificate binding.
Memory tip: Think of it this way - SSL is a two-way handshake. The monitor needs its own certificate to participate. No cert bound = no handshake = service DOWN. "SSL needs a cert to shake hands."
Topics
Community Discussion
No community discussion yet for this question.