Question 240
In the fictional Harbor-1 west pod, a staged top-of-rack rollout with a bounded maintenance window, the team reports that separate customers must not share unintended bridge or routing tables. The planned change is "Associate tenant segments with appropriate MAC-VRFs and IP-VRFs." Which post-change observation best validates the intended technical behavior?
Explanation
Correct Answer
Distinct virtual routing and bridging instances provide explicit tenant forwarding boundaries. The option uses “Verify that tenant routes and MACs occur only in the intended network instances” to address “separate customers must not share unintended bridge or routing tables”. The acceptance test is: tenant routes and MACs occur only in the intended network instances.
Incorrect Answers
“Check only that the device hostname is listed in the inventory, without examining tenant isolation behavior” targets a different operation from the reported requirement: “separate customers must not share unintended bridge or routing tables”. Distinct virtual routing and bridging instances provide explicit tenant forwarding boundaries. The confirming result is: tenant routes and MACs occur only in the intended network instances.
“Use an unrelated tenant dashboard as proof, without verifying the required tenant isolation condition” targets a different operation from the reported requirement: “separate customers must not share unintended bridge or routing tables”. Distinct virtual routing and bridging instances provide explicit tenant forwarding boundaries. The confirming result is: tenant routes and MACs occur only in the intended network instances.
“Confirm that a documentation ticket is marked complete, without checking switch state or forwarding behavior” targets a different operation from the reported requirement: “separate customers must not share unintended bridge or routing tables”. Distinct virtual routing and bridging instances provide explicit tenant forwarding boundaries. The confirming result is: tenant routes and MACs occur only in the intended network instances.