A Citrix Administrator executed the following command in the Global Server Load Balancing (GSLB) environment: set gslb site SiteB triggerMonitor MEPDOWN
What will be the effect of this command to the default service monitoring behavior on the remote site?
The command 'set gslb site SiteB triggerMonitor MEPDOWN' configures the GSLB site to invoke the service monitor only when the Metric Exchange Protocol (MEP) connectivity has been lost between SiteA and SiteB. This means that the monitoring by the service monitor is triggered when the metrics exchange via MEP is not possible, indicating an MEPDOWN state.
D is correct
D. When MEP is down, monitors take over / https://docs.citrix.com/en-us/netscaler/12/global-server-load-balancing/monitoring.html
D is the best answer, but the help page on the ADC tells this: * MEPDOWN - Monitor the GSLB service only when the exchange of metrics through the Metrics Exchange Protocol (MEP) is disabled. So only when disabled, not when down.
MEPDOWN – The health of GSLB Services that refer to services hosted on this site will be controlled by the configured monitors only if the Site Metric MEP Status is DOWN/DISABLED. https://support.citrix.com/article/CTX251348/citrix-adc-gslb-mep-vs-monitors
B- is ok; Exchange metrics with other sites. Metrics are exchanged by using Metric Exchange Protocol (MEP). The appliances in the GSLB setup exchange health information once every second. If you disable metrics exchange, you can use only static load balancing methods (such as round robin, static proximity, or the hash-based methods), and if you disable metrics exchange when a dynamic load balancing method (such as least connection) is in operation, the appliance falls back to round robin. Also, if you disable metrics exchange, you must use a monitor to determine the state of GSLB services. Otherwise, the service is marked as DOWN. Possible values: ENABLED, DISABLED