Question 80
At Granitebay Municipal Networks, while preparing a tenant migration, the data center fabric team observes: Fabric operations require per-device CLI edits even for repeated tenant changes. Which review gate should be added to prevent the same error?
Explanation
Correct Answer
At Granitebay Municipal Networks, while preparing a tenant migration, for Granitebay Municipal Networks, include the safeguard: Treat configuration reproducibility as a fabric architecture requirement. It reduces repeat risk from the original mechanism and complements a validation of: A controlled repeated change produces a consistent intended configuration on all selected nodes.
Incorrect Answers
At Granitebay Municipal Networks, while preparing a tenant migration, this option proposes: Maintain a versioned switch-role and hardware support matrix. Although related to Fabric architecture and data center design, the proposed change fits another mechanism: The device-role assignment was made without an approved platform and interface capability matrix. The evidence in the current case requires a different result: A controlled repeated change produces a consistent intended configuration on all selected nodes.
At Granitebay Municipal Networks, while preparing a tenant migration, this option proposes: Review VRF-to-tenant assignments before connecting new workloads. Using that approach would investigate Two tenant environments use identical private IP prefixes and operators assume they must be renumbered instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The design lacks a consistent automation interface and repeatable service intent workflow.
At Granitebay Municipal Networks, while preparing a tenant migration, this option proposes: Test redundant-path policy parity before production handoff. This option assumes the other problem (Two spines have asymmetric network policy and traffic takes a different security path on failover) is present. The case instead describes Fabric operations require per-device CLI edits even for repeated tenant changes, for which the causal issue is The design lacks a consistent automation interface and repeatable service intent workflow.