In Layer 3 mode, what is the behavior of the Citrix ADC regarding non-destined traffic?

In Layer 3 mode, what is the behavior of the Citrix ADC regarding non-destined traffic?

• A. It looks at its routing table and forwards all packets that are not destined for any appliance-owned IP address.
• B. It forwards packets based on routing table lookups.
• C. It forwards all traffic to the default gateway.
• D. It drops all non-destined traffic.

Answer: (A)

In Layer 3 mode the Citrix ADC behaves like a router rather than a switch. It only processes and transfers traffic that is not addressed to its own IPs. For any packet whose destination is not an appliance-owned IP address, the ADC looks up its routing table and forwards the packet toward the next hop. This routing decision is what moves non-destined traffic through the network. If a packet is destined for one of the ADC’s own IP addresses (such as a VIP or SNIP), it’s meant for the appliance itself and isn’t forwarded. The default gateway concept matters when no specific route matches, but the behavior isn’t to forward all traffic to the default gateway unconditionally. Non-destined traffic is forwarded according to the routing table, not dropped.

In Layer 3 mode the Citrix ADC behaves like a router rather than a switch. It only processes and transfers traffic that is not addressed to its own IPs. For any packet whose destination is not an appliance-owned IP address, the ADC looks up its routing table and forwards the packet toward the next hop. This routing decision is what moves non-destined traffic through the network.

If a packet is destined for one of the ADC’s own IP addresses (such as a VIP or SNIP), it’s meant for the appliance itself and isn’t forwarded. The default gateway concept matters when no specific route matches, but the behavior isn’t to forward all traffic to the default gateway unconditionally. Non-destined traffic is forwarded according to the routing table, not dropped.