lb_vsrv so that POL_2 is evaluated after POL_2 is evaluated?

Scenario:

POLICY 1:

add rewrite action ACT_1 corrupt_http_header Accept-Encoding

add rewrite policy POL_1 HTTPS.REQ.IS_VALID ACT_1

POLICY 2:

add rewrite action ACT_2 insert_http_header Accept-Encoding “”identity””

add rewrite policy POL_2 “HTTP.REQ.IS_VALID “ ACT_2

How can a Citrix Administrator successfully bind the above rewrite policies to the load-

balancing vServer

lb_vsrv so that POL_2 is evaluated after POL_2 is evaluated?
A . bind lb vServer lb_vsrv CpolicyName POL_1 Cpriority 110 CgotoPriorityExpression NEXT Ctype REQUEST
bind lb vServer lb_vsrv CpolicyName POL_2 Cpriority 100 CgotoPriorityExpression END Ctype REQUEST
B. bind lb vServer lb_vsrv CpolicyName POL_1 Cpriority 90 CgotoPriorityExpression NEXT Ctype REQUEST
bind lb vServer lb_vsrv CpolicyName POL_2 Cpriority 100 CgotoPriorityExpression END Ctype REQUEST
C. bind lb vServer lb_vsrv CpolicyName POL_1 Cpriority 90 CgotoPriorityExpression END Ctype REQUEST
bind lb vServer lb_vsrv CpolicyName POL_2 Cpriority 80 CgotoPriorityExpression NEXT Ctype REQUEST
D. bind lb vServer lb_vsrv CpolicyName POL_1 Cpriority 90 Ctype REQUEST bind lb vServer lb_vsrv CpolicyName POL_2 Cpriority 100 Ctype REQUEST

View Answer

Answer: B

Explanation:

– Pol1 has a prio of 90 so it’s evaluated first

-gotoPrioExpression NEXT means that it will evaluate next item in the policy list – Pol2 has a prio of 100, so it"s avaluated after Pol1