If a policy evaluates as_________________ a Citrix ADC performs the action assigned to the ____________ condition and stops further policy evaluation.

Grace U.Mar 29, 2026

The answer is C, UNDEFINED and FALSE, because when a Citrix ADC policy cannot be evaluated and returns UNDEFINED, the appliance treats that outcome the same way it treats a failed match, so it executes the FALSE branch action and immediately halts the policy chain. Once you picture UNDEFINED as basically a "we could not decide" result that the system routes to the safe default path, that pairing sticks.

Jovan I.Mar 14, 2026

Answer is C, UNDEFINED triggers the FALSE-condition action and halts the chain, which catches a lot of people off guard because they assume UNDEFINED just falls through to the next policy in the bind order rather than terminating evaluation right there. Quick follow-up for anyone studying this: do you know which specific scenarios in a real request flow would actually cause a policy expression to return UNDEFINED rather than a clean TRUE or FALSE, and how does that differ from a policy simply not matching?

Anjali D.Mar 24, 2026

Our group landed on C as well. When a policy hits UNDEFINED it means the expression could not be evaluated cleanly, so the ADC takes the action tied to the FALSE branch and exits the evaluation chain right there, which is a key behavior to know for the responder and rewrite policy flow.

Dervla O.Apr 13, 2026

The stem is telling you exactly what to look for: two blanks, two conditions, one action trigger and one stop trigger, which maps cleanly onto TRUE driving the action and FALSE being the condition that halts further evaluation, so A is the only option where both blanks carry distinct, logical values instead of the same word repeated or a vague UNDEFINED that does not actually describe a policy outcome you can act on.