Question 10
At Pinebrook Municipal Networks, while expanding a dual-spine Clos topology, the data center fabric team observes: Two tenant environments use identical private IP prefixes and operators assume they must be renumbered. What observation should be required before this case is closed?
Explanation
Correct Answer
At Pinebrook Municipal Networks, while expanding a dual-spine Clos topology, both tenants reach their own gateways without inter-tenant route leakage. This is linked directly to the observed symptom (Two tenant environments use identical private IP prefixes and operators assume they must be renumbered) and cannot be replaced by an unrelated healthy dashboard.
Incorrect Answers
At Pinebrook Municipal Networks, while expanding a dual-spine Clos topology, this option proposes: A path review confirms expected hop count and multipath reachability between tested leaf pairs. 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: Tenant addressing was not separated with routing instances and overlay service boundaries.
At Pinebrook Municipal Networks, while expanding a dual-spine Clos topology, this option proposes: Each proposed device meets its required fabric port and routing capabilities in the design inventory. The alternative focuses on The device-role assignment was made without an approved platform and interface capability matrix, not on the stated defect. For this scenario the expected acceptance result would be: Both tenants reach their own gateways without inter-tenant route leakage.
At Pinebrook Municipal Networks, while expanding a dual-spine Clos topology, this option proposes: The routing table exposes multiple equal-cost next hops and a controlled link failure preserves reachability. This option assumes the other problem (An engineer proposes spanning-tree-blocked links as the principal load-balancing method for a new routed fabric) is present. The case instead describes Two tenant environments use identical private IP prefixes and operators assume they must be renumbered, for which the causal issue is Tenant addressing was not separated with routing instances and overlay service boundaries.