What must be configured to establish a spine-leaf architecture using Fabric Composer?

Question

Options

• AQoS policies
• BVLAN tagging
• CUnderlay and overlay networks
• DSingle-hop routing

• A
  4% (1)
• B
  7% (2)
• C
  89% (25)

Explanation

Fabric Composer requires both underlay and overlay networks to be configured because spine-leaf architecture depends on two distinct network layers working together: the underlay provides the physical IP routing fabric (typically using BGP or OSPF between spine and leaf switches), while the overlay carries tenant/application traffic using encapsulation protocols like VXLAN. Without both layers defined, the fabric has no routing foundation and no way to tunnel workload traffic across it.

Why the distractors are wrong:

• A (QoS policies): QoS is a traffic-shaping feature applied after the fabric is built - not a prerequisite for establishing the architecture.
• B (VLAN tagging): VLANs are a Layer 2 construct; spine-leaf fabrics are Layer 3-routed, and VXLAN overlays replace traditional VLAN-based segmentation.
• D (Single-hop routing): Spine-leaf inherently involves multi-hop paths (leaf → spine → leaf); single-hop routing contradicts the architecture's design.

Memory tip: Think "under → over" - you must build the road (underlay) before you can run the traffic (overlay). If you remember that spine-leaf = two layers of the network stack, option C is the only choice that references two distinct network components.

No community discussion yet for this question.