Which option would you select to reduce the number of health checks sent by NetScaler to backend resources?

• A. Use the No-Monitor option.
• B. Use Service Groups to minimize health checks.
• C. Unbind the current monitor.
• D. Use reverse condition monitoring.

Answer: (A)

When Citrix ADC checks backend resources, it uses monitors to determine if a service is healthy. To truly cut down on the probe traffic, the straightforward approach is to disable health checks for that service by choosing No Monitor. This stops all health probes for that resource, reducing the load from monitoring on both the appliance and the backend.

Keep in mind that turning off monitoring means the appliance has no automatic visibility into the backend’s health, so automatic failover or rebalancing won’t happen for that service until monitoring is re-enabled.

Using a service group isn’t guaranteed to reduce checks, since monitors associated with the group—or the individual members—can still trigger health probes. Unbinding the current monitor could also reduce checks, but it’s less explicit and could lead to ambiguity about what health check behavior remains. Reverse condition monitoring changes interpretation, not the frequency of checks.