A metro pod wants separate IP fabrics for storage versus general compute. What architecture choice does that request illustrate at concept level?
Select an answer to reveal the explanation.
Short Explanation
Sometimes the city builds two neighborhoods instead of one noisy block—storage fabric here, compute fabric there. That is pod or fabric segmentation for isolation. It is not a call to mush everything back into one STP lake.
Full Explanation
Separate IP fabrics for storage versus general compute illustrate pod or fabric segmentation isolating workload classes at the Layer 3 fabric level. It is not a mandate that storage and compute share one VTEP and one underlay ASN only. It is not a call to collapse into one STP domain. It is not moving all storage NICs to spines so compute leaves never see storage. Exam caveat: Segmentation controls blast radius and performance profiles; plan routing/overlay boundaries per fabric. Operational check: Document distinct underlay ASN/VNI/policy domains for storage vs compute pods. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure.