Question 50
At Bluehaven Health Systems, while auditing design assumptions, the data center fabric team observes: Two tenant environments use identical private IP prefixes and operators assume they must be renumbered. What test result proves the affected fabric function now works?
Explanation
Correct Answer
At Bluehaven Health Systems, while auditing design assumptions, for Bluehaven Health Systems, accept the repair only after this observation: Both tenants reach their own gateways without inter-tenant route leakage. The test distinguishes real recovery from a superficial status change.
Incorrect Answers
At Bluehaven Health Systems, while auditing design assumptions, this option proposes: The tested broadcast domain is isolated by tenant while routed underlay links remain independently reachable. This option assumes the other problem (A team extends a single large Layer 2 broadcast domain across every rack to simplify mobility) 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.
At Bluehaven Health Systems, while auditing design assumptions, this option proposes: The routing table exposes multiple equal-cost next hops and a controlled link failure preserves reachability. The option describes a different failure mode: An engineer proposes spanning-tree-blocked links as the principal load-balancing method for a new routed fabric. It would address The design confuses legacy Layer 2 loop prevention with Layer 3 equal-cost forwarding, but here the case reports Two tenant environments use identical private IP prefixes and operators assume they must be renumbered. The current required evidence is: Both tenants reach their own gateways without inter-tenant route leakage.
At Bluehaven Health Systems, while auditing design assumptions, this option proposes: A path review confirms expected hop count and multipath reachability between tested leaf pairs. That choice would be more relevant when this different symptom occurs: A proposed three-tier design forces east-west traffic through an unnecessary aggregation hop. The present scenario instead points to: Tenant addressing was not separated with routing instances and overlay service boundaries. The correct resolution has its own verification outcome: Both tenants reach their own gateways without inter-tenant route leakage.