HPE6-A87 · Question #3
What type of network architecture does Fabric Composer primarily manage?
The correct answer is B. Leaf-Spine. Fabric Composer is designed to manage Leaf-Spine architectures, the dominant topology in modern data center fabrics. This two-tier design uses leaf switches (connecting servers) and spine switches (interconnecting all leaves), providing predictable low-latency, high-bandwidth…
Question
What type of network architecture does Fabric Composer primarily manage?
Options
- AFull Mesh
- BLeaf-Spine
- CRing
- DStar
How the community answered
(58 responses)- A7% (4)
- B88% (51)
- C3% (2)
- D2% (1)
Explanation
Fabric Composer is designed to manage Leaf-Spine architectures, the dominant topology in modern data center fabrics. This two-tier design uses leaf switches (connecting servers) and spine switches (interconnecting all leaves), providing predictable low-latency, high-bandwidth east-west traffic - exactly what fabric management tools are built to orchestrate.
- A (Full Mesh) is incorrect because while every node connects to every other in a full mesh, this topology doesn't scale well in data centers and isn't what "fabric" solutions are architected around.
- C (Ring) is incorrect; ring topologies are associated with older WAN/MAN technologies (like SONET/SDH), not modern data center fabrics.
- D (Star) is incorrect; star topology describes a single central hub/switch connecting endpoints - too simple and single-point-of-failure-prone for what Fabric Composer manages.
Memory tip: Think of "fabric" as a woven cloth - threads running horizontally (spine) cross threads running vertically (leaf), forming an interconnected mesh pattern. That visual maps directly to Leaf-Spine, making "Fabric Composer = Leaf-Spine" easy to recall on exam day.
Topics
Community Discussion
No community discussion yet for this question.