Scenario: A Citrix Administrator is concerned about the number of health checks the Citrix ADC is sending to backend resources. The administrator wants to find a way to remove health checks from…

Question

Options

• AUse reverse-condition monitoring.
• BUnbind the current monitor.
• CUse service groups to minimize health checks.
• DUse the no-monitor option.

• A
  7% (4)
• B
  11% (6)
• C
  4% (2)
• D
  78% (43)

Explanation

Using the no-monitor option when binding a service to a virtual server instructs the Citrix ADC to skip health checks for that specific service, giving administrators granular control without altering the monitor itself. Option A (reverse-condition monitoring) inverts a monitor's success/failure logic - it doesn't remove health checks, it just flips what counts as "up." Option B (unbinding the monitor) would leave the service with no monitor at all, which typically causes ADC to fall back to a default monitor rather than suppressing checks entirely, and it's a blunt action affecting all bindings. Option C (service groups) consolidates monitoring across grouped services but doesn't eliminate checks - it actually applies one monitor to many members efficiently. A helpful memory tip: think of no-monitor = "don't check this one" - it's a targeted suppress flag at bind time, not a change to the monitor object itself, so it leaves everything else untouched.

No community discussion yet for this question.