Scenario: A Citrix Administrator executes 'set gslb site SiteB -triggerMonitor MEPDOWN'. What is the effect on the default service monitoring at the remote site?

Scenario: A Citrix Administrator executes 'set gslb site SiteB -triggerMonitor MEPDOWN'. What is the effect on the default service monitoring at the remote site?

• A. The state of the GSLB service will always be controlled by Metric Exchange Protocol (MEP).
• B. The service monitor will take precedence over MEP.
• C. The service monitor is invoked only when MEP connectivity has been lost between Site A and Site B.
• D. The service monitor is invoked only when Metric Exchange Protocol (MEP) has marked the service as DOWN.

Answer: (D)

The key idea is how GSLB uses MEP to coordinate health between sites. Metric Exchange Protocol (MEP) shares health status, and the triggerMonitor setting controls when the remote site’s default service monitor runs. By setting the trigger to MEPDOWN, the local GSLB will only invoke the remote site's service monitor after MEP has marked the service as DOWN. If MEP still shows UP, the monitor isn’t triggered. This gates extra monitoring behind an MEP-down event, preventing unnecessary checks and letting the system verify the real state only when MEP detects a problem.

The key idea is how GSLB uses MEP to coordinate health between sites. Metric Exchange Protocol (MEP) shares health status, and the triggerMonitor setting controls when the remote site’s default service monitor runs. By setting the trigger to MEPDOWN, the local GSLB will only invoke the remote site's service monitor after MEP has marked the service as DOWN. If MEP still shows UP, the monitor isn’t triggered. This gates extra monitoring behind an MEP-down event, preventing unnecessary checks and letting the system verify the real state only when MEP detects a problem.