What is the effect of a GotoExpression value END on policy evaluation order?

What is the effect of a GotoExpression value END on policy evaluation order?

• A. It means only the first applicable policy at the given priority will execute.
• B. It causes the second policy to execute as well.
• C. It disables the policy entirely.
• D. It restarts evaluation from the beginning.

Answer: (A)

Flow control in policy evaluation is driven by where you are in the priority order and what the goto expression asks the engine to do after a match. When a policy’s condition matches, the engine looks at its goto expression to decide what happens next. If the goto expression is END, evaluation stops right after that policy executes. This means only the first policy that is applicable at that priority level runs, and no further policies are evaluated, either at the same priority or lower priorities. If no policy matches at that priority, evaluation proceeds to the next priority level and repeats. So END makes the system stop after the first applicable policy, preventing any additional policies from running.

Flow control in policy evaluation is driven by where you are in the priority order and what the goto expression asks the engine to do after a match. When a policy’s condition matches, the engine looks at its goto expression to decide what happens next. If the goto expression is END, evaluation stops right after that policy executes. This means only the first policy that is applicable at that priority level runs, and no further policies are evaluated, either at the same priority or lower priorities. If no policy matches at that priority, evaluation proceeds to the next priority level and repeats. So END makes the system stop after the first applicable policy, preventing any additional policies from running.