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 rewrite action ACT_2 insert_http_header Accept-Encoding “\”identity\”” add rewrite policy POL_2 “HTTP.REQ.IS_VALID” ACT_2
Which set of commands can the administrator use to bind the rewrite policies to the LB vserver lb_vsrv so that POL_2 is evaluated after POL_1 is evaluated successfully?
To ensure that POL_2 is evaluated after POL_1 is successfully evaluated, POL_1 should have a lower priority number (higher priority) and a gotoPriorityExpression of NEXT, allowing the next policy to be evaluated. POL_2 should have a higher priority number (lower priority) with a gotoPriorityExpression of END, indicating no further policies are to be evaluated. Binding POL_1 with priority 90 and POL_2 with priority 100 achieves this configuration, making sure POL_1 is checked first and, if successful, moves to POL_2. This configuration ensures the desired policy evaluation sequence.
Its D for 2 reasons: - pol 1 priority is higher: 90>100 - the gotoPriorityExpression expression
D 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 90 is evaluated first, then it goes to the Next, then 100 is evaluated, with an End on it. Answer A is wrong is POL-2 evalutng first. B is wrong because it does not showing the Next Expression for the other policy. C is wrong because on Priority 1 it says End, So Pol_2 is not looked at. D is right because I follow the POL_1 being lower (90) which applies first, then goes to Next POL_2 which is (100) and then End
Definitely not A and C. In the Citrix ADC operating system, policy priorities work in reverse order—the higher the number, the lower the priority.
Of course D