Which two steps are necessary to configure global server load balancing (GSLB) service selection using content switching (CS)? (Choose two.)

Question

Options

• AConfigure CS policies that designate a load-balancing vServer as the target vServer.
• BBind the GSLB domain to the GSLB vServer.
• CConfigure a CS vServer of target type GSLB.
• DBind the domain to the CS vServer instead of the GSLB vServer.

• A
  74% (17)
• C
  9% (2)
• D
  17% (4)

Explanation

Configuring GSLB with content switching requires two distinct but complementary actions: CS policies (A) must designate load-balancing vServers as their targets, which is how the content-switching layer knows where to forward requests based on URL/header rules; and the GSLB domain (B) must be bound to the GSLB vServer so that DNS-based global load balancing can resolve client requests to the correct data center.

Option C is a distractor because CS vServers do not have a "GSLB target type" - CS vServers route to LB vServers, not directly to GSLB entities. GSLB operates at the DNS layer, not as a direct CS target.

Option D inverts the correct architecture: the GSLB domain must be bound to the GSLB vServer (as stated in B), not the CS vServer - doing so would bypass GSLB's DNS-based site selection entirely.

Memory tip: Think of it as two separate layers that each need one configuration step - the content layer (CS policies → LB vServer targets) and the global DNS layer (GSLB domain → GSLB vServer). One step per layer = two steps total.

No community discussion yet for this question.