Question 60
At Midvale Health Systems, while checking rack-to-rack resilience, the data center fabric team observes: A hardware inventory assigns 7220 IXR leaf roles to every spine without validating model capabilities. What ongoing operational safeguard directly addresses this root issue?
Explanation
Correct Answer
At Midvale Health Systems, while checking rack-to-rack resilience, the preventive control is: Maintain a versioned switch-role and hardware support matrix. It catches the same mechanism (The device-role assignment was made without an approved platform and interface capability matrix) before the symptom recurs. An appropriate regression observation is: Each proposed device meets its required fabric port and routing capabilities in the design inventory.
Incorrect Answers
At Midvale Health Systems, while checking rack-to-rack resilience, this option proposes: Require underlay transport tests as a prerequisite for overlay service acceptance. Although related to Fabric architecture and data center design, the proposed change fits another mechanism: The overlay was designed without a working routed underlay between tunnel endpoints. The evidence in the current case requires a different result: Each proposed device meets its required fabric port and routing capabilities in the design inventory.
At Midvale Health Systems, while checking rack-to-rack resilience, this option proposes: Validate east-west path requirements when selecting data center topology. Using that approach would investigate A proposed three-tier design forces east-west traffic through an unnecessary aggregation hop instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The device-role assignment was made without an approved platform and interface capability matrix.
At Midvale Health Systems, while checking rack-to-rack resilience, this option proposes: Treat configuration reproducibility as a fabric architecture requirement. The alternative focuses on The design lacks a consistent automation interface and repeatable service intent workflow, not on the stated defect. For this scenario the expected acceptance result would be: Each proposed device meets its required fabric port and routing capabilities in the design inventory.