nerdexam
Citrix

1Y0-231 · Question #153

Scenario: A Citrix Administrator needs to configure a Responder policy, so that the string "/mytraining" is added to every URL path received. The administrator should use these commands to…

The correct answer is B. "!(HTTP.REQ.URL.STARTSWITH(\"mytraining\"))". Option B is correct because the responder action prepends "mytraining" to the incoming URL path, meaning after a redirect the resulting URL will start with "mytraining." The negation operator (!) ensures the policy only fires when the URL does not already start with…

Load Balancing

Question

Scenario: A Citrix Administrator needs to configure a Responder policy, so that the string “/mytraining” is added to every URL path received. The administrator should use these commands to accomplish this:

add responder action Redirect_Act redirect “HTTP.REQ.URL.PATH_AND_QUERY+\”mytraining\”” –responseStatusCode 302 > add responder policy Redirect_Pol ___________ Redirect_Act > bind lb vServer lb_vsrv_www –policyName Redirect_Pol –priority 100 –gotoPriorityExpression END –type _______ (Choose the correct option to complete the set of commands.)

Options

  • A"!(HTTP.REQ.URL.ENDSWITH("mytraining"))"
  • B"!(HTTP.REQ.URL.STARTSWITH("mytraining"))"
  • C"!(HTTP.REQ.URL.ENDSWITH("mytraining"))"
  • D"!(HTTP.REQ.URL.STARTSWITH("mytraining"))"

How the community answered

(44 responses)
  • A
    14% (6)
  • B
    80% (35)
  • C
    2% (1)
  • D
    5% (2)

Explanation

Option B is correct because the responder action prepends "mytraining" to the incoming URL path, meaning after a redirect the resulting URL will start with "mytraining." The negation operator (!) ensures the policy only fires when the URL does not already start with "mytraining," preventing an infinite redirect loop where each redirected request would trigger another redirect.

Options A and C use ENDSWITH, which would be appropriate if the action were appending "mytraining" to the end of the URL - but since the redirect constructs a URL beginning with "mytraining," checking the end of the URL wouldn't catch already-redirected requests, causing an infinite loop. Option D uses the correct STARTSWITH expression but pairs it with the wrong -type binding parameter (e.g., RESPONSE instead of REQUEST); since Responder policies act on incoming client requests, the binding type must be REQUEST.

Memory tip: Think STARTSWITH = Start of path = the redirect Sends you to a URL that Starts with the new string. The ! is your loop-breaker - "don't redirect if I've already done my job."

Topics

#Responder Policy#URL Redirection#Policy Binding#HTTP Request Conditions

Community Discussion

No community discussion yet for this question.

Full 1Y0-231 Practice