In the virtualized campus network design, which one of the following descriptions about Fabri c networking design is wrong?

Question

Options

• AIf you want to reuse the original access switch (which does not support VXLAN), you can deploy
• BWhen the terminal scale is small, you can choose a centralized gateway network, in which Border
• CSingle/Border networking can be selected according to different scenarios. The VXLAN centralized
• DIf users in multiple VNs want to access the external network, and each VN has different security

• A
  3% (2)
• B
  18% (12)
• C
  72% (49)
• D
  7% (5)

Explanation

Option C contains an incorrect statement about VXLAN centralized gateway deployment in a Fabric network. In campus Fabric design, the centralized gateway model is not restricted to only Border-node scenarios - it can also be used in Single-node deployments. C incorrectly conflates or mischaracterizes when VXLAN centralized gateways can be applied across these topology choices.

Why the distractors are correct (and thus not the answer):

• Option A is accurate: when legacy access switches lack VXLAN support, a VXLAN gateway can be pushed up to the aggregation or core layer, allowing gradual migration without replacing all access hardware.
• Option B is accurate: for smaller terminal scales, a centralized gateway on the Border node is a valid and common design choice, simplifying policy management.
• Option D is accurate: when multiple VNs (Virtual Networks) with differing security policies need external access, deploying per-VN security zones or separate routing instances on the Border is the correct approach.

Memory tip: Think of "C = Confused about centralized." The trap in C is that it implies a restriction on where centralized VXLAN gateways can live - remember that both Single and Border topologies support centralized gateways; the choice depends on scale and redundancy needs, not a hard rule.

No community discussion yet for this question.