What happens when a responder policy bound to a vServer uses 'gotoPriorityExpression END'?

What happens when a responder policy bound to a vServer uses 'gotoPriorityExpression END'?

• A. The request continues to evaluate the next policy.
• B. The request stops evaluating policies and returns the current result.
• C. The request is redirected to another vServer.
• D. The request is logged and then passed to the backend.

Answer: (B)

gotoPriorityExpression END stops policy evaluation for the vServer and returns the result produced by the policies evaluated so far. In other words, once a policy matches and this END is reached, no further responder policies are checked, and the response (or action) defined up to that point is sent back. It doesn’t by itself redirect to another vServer, nor does it imply logging or sending traffic to the backend unless the policy action already dictated that.

gotoPriorityExpression END stops policy evaluation for the vServer and returns the result produced by the policies evaluated so far. In other words, once a policy matches and this END is reached, no further responder policies are checked, and the response (or action) defined up to that point is sent back. It doesn’t by itself redirect to another vServer, nor does it imply logging or sending traffic to the backend unless the policy action already dictated that.