Scenario: A Citrix Administrator configured the policies below: POLICY 1: add rewrite action ACT_1 corrupt_http_header Accept-Encoding add rewrite policy POL_1 HTTP.REQ.IS_VALID ACT_1 POLICY 2: add…

Question

Options

• Abind lb vserver lb_vsrv -policyName POL_1 -priority 110 -gotoPriorityExpression NEXT -type
• Bbind lb vserver lb_vsrv -policyName POL_1 -priority 90 -type REQUEST
• Cbind lb vserver lb_vsrv -policyName POL_1 -priority 90 -gotoPriorityExpression END -type
• Dbind lb vserver lb_vsrv -policyName POL_1 -priority 90 -gotoPriorityExpression NEXT -type

• A
  67% (22)
• B
  12% (4)
• C
  18% (6)
• D
  3% (1)

Explanation

Option A is correct because it binds POL_1 with gotoPriorityExpression NEXT, which instructs the NetScaler to continue evaluating the next policy in the chain after POL_1 executes. Combined with a priority of 110 for POL_1 and a higher priority number for POL_2 (e.g., 120), this guarantees POL_1 fires first, then POL_2 is evaluated in sequence.

Option B is wrong because it omits gotoPriorityExpression entirely - without it, the binding defaults to END behavior, so evaluation stops after POL_1 matches and POL_2 is never reached.

Option C is wrong for the same reason: explicitly setting gotoPriorityExpression END terminates the policy chain immediately after POL_1, preventing POL_2 from ever being evaluated.

Option D is wrong because while it correctly uses NEXT, the priority of 90 for POL_1 combined with the POL_2 binding in that option set places POL_2 at a lower priority number (evaluated earlier), meaning POL_2 would actually run before POL_1 - the opposite of what's required.

Memory tip: Think of NEXT as "keep going down the list" and END as "stop here." When you need Policy B to run after Policy A, use NEXT on A and ensure A's priority number is lower (runs first) than B's.

No community discussion yet for this question.