If a VSX Gateway is protecting multiple customer networks behind only one shared interface, the VSX Administrator must either configure _____________ for source-based routing or deploy a VLAN…

Question

Options

• AAn Internal Virtual Router
• BVSX Gateway High Availability
• CNon-VLAN Interface Trunking
• DVSX Gateway Load Sharing
• EMultiple External Virtual Routers

• A
  80% (35)
• B
  2% (1)
• C
  5% (2)
• D
  11% (5)
• E
  2% (1)

Explanation

An Internal Virtual Router (IVR) enables source-based routing within the VSX environment, which is essential when multiple customer networks must share a single physical interface - the IVR examines the source IP to determine which virtual system's routing table should handle the traffic, effectively separating customers without needing VLANs.

Why the distractors are wrong:

• B (HA) addresses redundancy and failover, not traffic segregation across a shared interface.
• C (Non-VLAN Interface Trunking) is not a real VSX concept, and trunking is actually VLAN-dependent - the opposite of what the question describes.
• D (Load Sharing) distributes traffic across multiple physical gateways for performance; it doesn't solve the per-customer routing problem.
• E (Multiple External Virtual Routers) - External VRs connect VSX to upstream/outside networks; source-based routing for internal customer segregation is the job of an Internal VR.

Memory tip: Think "Internal = Inside the house." When multiple tenants (customers) share one front door (interface), an Internal Virtual Router acts as the building directory - it reads who sent it (source) to route each tenant's mail to the right apartment (virtual system).

No community discussion yet for this question.