Scenario: A Citrix Administrator executed the following command in a global server load balancing (GSLB) environment: set gsib site SiteB -triggerMonitor MEPDOWN What will be the effect of this…

Question

Options

• AThe service monitor will take precedence over Metric Exchange Protocol (MEP).
• BThe service monitor is invoked only when Metric Exchange Protocol (MEP) connectivity has been
• CThe service monitor is invoked only when Metric Exchange Protocol (MEP) has marked the service
• DThe state of the GSLB service will always be controlled by Metric Exchange Protocol (MEP).

• A
  12% (6)
• B
  6% (3)
• C
  80% (41)
• D
  2% (1)

Explanation

Setting -triggerMonitor MEPDOWN on a GSLB site means the local service health monitor for a remote site's services is triggered only when MEP has reported that service as DOWN - acting as a secondary confirmation mechanism rather than running probes continuously. This is correct because MEPDOWN specifically ties the local monitor's activation to MEP's service state signal, not to general MEP link loss or unconditional probing.

Why the distractors are wrong:

• A is wrong because MEPDOWN does not give the service monitor precedence over MEP; MEP remains the primary authority, and the monitor only supplements it under a specific condition.
• B is wrong because it describes MEP connectivity (link-level failure between sites), whereas MEPDOWN is triggered by MEP marking the service itself as down - a more granular, service-level distinction.
• D is wrong because that describes the NONE trigger setting, where MEP exclusively controls service state and local monitors are never invoked.

Memory tip: Think of MEPDOWN as "trust but verify" - MEP is in charge, but when MEP says a service is dead, the local monitor gets called in to double-check. If MEP says the service is fine, the monitor stays silent.

No community discussion yet for this question.