How can a Citrix Administrator successfully bind the rewrite policies to the load-balancing vServer so that POL2 is evaluated after POL1?

• A. bind lb vServer lb_vsrv -policyName POL_1 -priority 110 -gotoPriorityExpression NEXT -type REQUEST bind lb vServer lb_vsrv -policyName POL_2 -priority 100 - gotoPriorityExpression END -type REQUEST
• B. bind lb vServer lb_vsrv -policyName POL_2 -priority 100 -gotoPriorityExpression NEXT -type REQUEST bind lb vServer lb_vsrv -policyName POL_1 -priority 90 -gotoPriorityExpression END -type REQUEST
• C. bind lb vServer lb_vsrv -policyName POL_1 -priority 90 -gotoPriorityExpression NEXT -type REQUEST bind lb vServer lb_vsrv -policyName POL_2 -priority 100 - gotoPriorityExpression END -type REQUEST
• D. bind lb vServer lb_vsrv -policyName POL_1 -priority 90 -gotoPriorityExpression END -type REQUEST bind lb vServer lb_vsrv -policyName POL_2 -priority 100 - gotoPriorityExpression NEXT -type REQUEST

Answer: (C)

The binding order of rewrite policies on a load-balancing vServer is controlled by the policy priorities and the gotoPriorityExpression directives. The system evaluates policies in ascending order of their priority values; after a policy runs, gotoPriorityExpression NEXT continues to the next bound policy, while END stops the evaluation there. To have POL2 evaluated after POL1, POL1 must be bound with a lower priority and use NEXT, and POL2 must be bound with a higher priority and use END. In the given setup, POL_1 is bound with priority 90 and NEXT, and POL_2 with priority 100 and END. Since 90 is less than 100, POL1 runs first, then NEXT moves to POL2, which runs next and ends the evaluation. If POL1 had END or if POL2 had a lower priority, POL2 might not run as intended.