What two options are limitations of a typical Global Server Load Balancing (GSLB) setup? (Choose two.)
What two options are limitations of a typical Global Server Load Balancing (GSLB) setup? (Choose two.)
One limitation of a typical Global Server Load Balancing (GSLB) setup is that you cannot apply spillover policies on a subset of GSLB services and have a backup for that subset, which is described in option A. Another limitation is that any given GSLB Vserver can load-balance only one Fully Qualified Domain Name (FQDN), as stated in option D. These two points reflect common restrictions in GSLB configurations, where flexibility in policy application and domain handling are often constrained.
A & C are correct. In a typical GSLB deployment, you can prioritize the selection of a set of GSLB services bound to a GSLB virtual server, but you cannot do the following: Restrict the selection of a GSLB service from a subset of GSLB services bound to a GSLB virtual server for the given domain. Apply different load balancing methods on the different subsets of GSLB services in the deployment. Apply spillover policies on a subset of GSLB services, and you cannot have a backup for a subset of GSLB services. Configure a subset of GSLB services to serve different content. That is, you cannot content switch between servers in different GSLB sites. The GSLB configuration assumes that the servers contain the same content. Define a subset GSLB service with different priorities and specify an order in which the services in the subset are applied to a request.
AC are correct. " Configure GSLB service selection using content switching Restrict the selection of a GSLB service from a subset of GSLB services bound to a GSLB virtual server for the given domain. Apply spillover policies on a subset of GSLB services, and you cannot have a backup for a subset of GSLB services." Reference: https://docs.citrix.com/en-us/netscaler/12/global-server-load-balancing/how-to/configure-gslb-contentswitch.html