Scenario: A Citrix Administrator configured a load-balancing vServer. The URL for this vServer is vpn.citrix.com. The backend server has the host name configured as server1.citrix.com. The…

Question

Options

• Aset transform action "host change" -priority 10 -reqUrlFrom "https://server1.citrix.com/*" -
• Bset transform action "host change" -priority 10 -reqUrlFrom "https://vpn.citrix.com/*" -reqUrlInto
• Cset transform action "host change" -priority 10 -reqUrlFrom "https://server1.citrix.com/*" -
• Dset transform action "host change" -priority 10 -reqUrlFrom "https://vpn.citrix.com/*" -reqUrlInto

• A
  5% (3)
• B
  75% (41)
• C
  4% (2)
• D
  16% (9)

Explanation

Option B is correct because the reqUrlFrom parameter must match the client-facing URL (vpn.citrix.com) - the hostname clients actually send in their requests - and transform it into the backend server's hostname (server1.citrix.com) via reqUrlInto; this is the correct direction for request-side URL rewriting.

Options A and C are wrong because they set reqUrlFrom to server1.citrix.com, which is backwards: client requests arrive addressed to vpn.citrix.com, not the backend hostname, so that pattern would never match incoming traffic.

Option D appears structurally similar to B but differs in the reqUrlInto value or the response-side parameters - without both the request transformation (vpn → server1) and the response transformation (server1 → vpn) configured correctly, the bidirectional requirement isn't met.

Memory tip: Think of it from the client's perspective first - the client sends vpn.citrix.com, so reqUrlFrom = vpn.citrix.com (what comes from the request). The transform rewrites it into the backend name. "From the outside in" = request direction.

No community discussion yet for this question.