In a GSLB environment, what is the effect of executing set gslb site SiteB triggerMonitor MEPDOWN on the remote site’s default service monitoring?

• A. The state of the GSLB service will always be controlled by MEP.
• B. The service monitor is invoked only when MEP has marked the service as DOWN for any reason.
• C. The service monitor will take precedence over MEP.
• D. The service monitor is invoked only when MEP connectivity has been lost between SiteA and SiteB.

Answer: (D)

In GSLB, health is evaluated at two levels: the MEP (Monitoring End Points) connection between sites and the per-service monitors at each site. The setting triggerMonitor MEPDOWN on the remote site’s default service monitoring makes the per-service monitors run only when the MEP link between SiteA and SiteB has actually failed. When the MEP connection is up, the system relies on MEP status for decision making and does not invoke the service monitors. Only after MEP connectivity is lost are the service monitors activated to verify whether the remote site’s services are really down, which then informs failover decisions. That’s why the correct behavior is that the service monitor is invoked only when MEP connectivity has been lost between SiteA and SiteB.