Scenario: A Citrix ADC receives packets destined for a MAC address owned by the Citrix ADC. The destination IP address of the packets does NOT belong to the Citrix ADC. Layer 3 mode is enabled by…

Question

Options

• Adrop
• Brewrite
• Croute
• Dbridge

• A
  5% (2)
• B
  15% (6)
• C
  74% (29)
• D
  5% (2)

Explanation

When Layer 3 mode is enabled, the Citrix ADC behaves like a router - it accepts the packet because it owns the destination MAC (Layer 2 match), but since the destination IP is not its own, it consults its routing table and forwards the packet toward the correct next hop. This is the defining behavior of L3 mode: forward traffic based on IP, not just MAC ownership.

Why the distractors are wrong:

• A (drop): The ADC only drops packets when there is no route, an explicit policy enforces it, or the feature set requires it - not by default in this scenario.
• B (rewrite): Rewriting refers to modifying headers (e.g., NAT, URL rewriting) - a load-balancing function, not the default packet-forwarding behavior.
• D (bridge): Bridging is the behavior in Layer 2 mode, where the ADC forwards traffic based on MAC addresses without IP-level routing logic; since Layer 3 mode is active here, bridging is not in play.

Memory tip: Think "L3 = IP Routing, L2 = MAC Bridging." If the ADC owns the MAC but not the IP and L3 is on, it routes - just like a standard IP router would.

No community discussion yet for this question.