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.)
A typical Global Server Load Balancing (GSLB) setup has certain limitations. One such limitation is that an administrator cannot define a backup for a backup virtual server in an active standby GSLB setup for a given GSLB domain. Another significant limitation is that any given GSLB virtual server can load-balance only one Fully Qualified Domain Name (FQDN). These constraints affect the flexibility and redundancy configuration options within a GSLB setup.
B,C are correct according to https://docs.citrix.com/en-us/citrix-adc/current-release/global-server-load-balancing/how-to/configure-gslb-content-switch.html
https://docs.netscaler.com/en-us/citrix-adc/current-release/global-server-load-balancing/how-to/configure-gslb-content-switch.html 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.