In a rewrite policy binding scenario, what effect does the -gotoPriorityExpression NEXT have when binding POL_1 and POL_2 to a vserver?

In a rewrite policy binding scenario, what effect does the -gotoPriorityExpression NEXT have when binding POL_1 and POL_2 to a vserver?

• A. End evaluation after POL_1
• B. Move to the next policy after POL_1
• C. Immediately apply POL_2
• D. Restart evaluation from POL_1

Answer: (B)

The action -gotoPriorityExpression NEXT controls how policy evaluation flows when multiple rewrite policies are bound to a vserver. When POL_1 matches and this action is in effect, the engine doesn’t stop there; it proceeds to evaluate the next policy in the binding order. So POL_2 is evaluated next, allowing its rewrite actions to apply if it matches as well. If POL_2 doesn’t match, evaluation completes for that binding (and the request continues according to the rest of the policy and binding configuration). In short, NEXT means “continue with the next bound policy after POL_1,” enabling a chained evaluation rather than halting or restarting.

The action -gotoPriorityExpression NEXT controls how policy evaluation flows when multiple rewrite policies are bound to a vserver. When POL_1 matches and this action is in effect, the engine doesn’t stop there; it proceeds to evaluate the next policy in the binding order. So POL_2 is evaluated next, allowing its rewrite actions to apply if it matches as well. If POL_2 doesn’t match, evaluation completes for that binding (and the request continues according to the rest of the policy and binding configuration). In short, NEXT means “continue with the next bound policy after POL_1,” enabling a chained evaluation rather than halting or restarting.