In a GSLB vServer configuration with RTT as the configured method and LEASTCONNECTION as backup, which method should the administrator change to for a different load-balancing strategy?

In a GSLB vServer configuration with RTT as the configured method and LEASTCONNECTION as backup, which method should the administrator change to for a different load-balancing strategy?

• A. Least Connection
• B. Round Robin
• C. Static Proximity
• D. Least Bandwidth

Answer: (C)

Switching from RTT to a static approach changes how the global load is distributed. RTT relies on real-time latency measurements to pick the closest site, which can vary with network conditions. Static Proximity, on the other hand, uses pre-configured proximity values for each GSLB site, so routing decisions are based on fixed geography rather than current RTT. This gives a predictable, deterministic distribution pattern and is a different strategy from latency-based routing. The backup method can still be LEAST CONNECTION, kicking in if the primary method can’t determine a best site. To implement, configure the vServer to use Static Proximity and assign proximity values to each site accordingly.

Switching from RTT to a static approach changes how the global load is distributed. RTT relies on real-time latency measurements to pick the closest site, which can vary with network conditions. Static Proximity, on the other hand, uses pre-configured proximity values for each GSLB site, so routing decisions are based on fixed geography rather than current RTT. This gives a predictable, deterministic distribution pattern and is a different strategy from latency-based routing. The backup method can still be LEAST CONNECTION, kicking in if the primary method can’t determine a best site. To implement, configure the vServer to use Static Proximity and assign proximity values to each site accordingly.