Question 200
At Parkhaven Rail Logistics, while auditing the model-driven CLI hierarchy, the data center fabric team observes: A fabric team applies a new interface description to the wrong port after a chassis replacement. Which recurring validation best prevents this failure mode?
Explanation
Correct Answer
At Parkhaven Rail Logistics, while auditing the model-driven CLI hierarchy, update physical-to-logical interface mappings after hardware changes. This ongoing review specifically addresses: The old physical port mapping was reused without reconciling current interface identifiers. It should remain part of change acceptance, not only incident closure.
Incorrect Answers
At Parkhaven Rail Logistics, while auditing the model-driven CLI hierarchy, this option proposes: Include routing-instance names in troubleshooting artifacts. That choice would be more relevant when this different symptom occurs: An operator inspects an IPv4 route in a tenant instance but checks the default IPv4 table. The present scenario instead points to: The old physical port mapping was reused without reconciling current interface identifiers. The correct resolution has its own verification outcome: The intended port displays the approved description and the neighbor mapping is correct.
At Parkhaven Rail Logistics, while auditing the model-driven CLI hierarchy, this option proposes: Test dual-stack families independently on every service turn-up. Although related to SR Linux CLI, model configuration and interfaces, the proposed change fits another mechanism: The subinterface or IP-VRF lacks the intended IPv6 address or route information. The evidence in the current case requires a different result: The intended port displays the approved description and the neighbor mapping is correct.
At Parkhaven Rail Logistics, while auditing the model-driven CLI hierarchy, this option proposes: Separate operator shell conveniences from device configuration policy. Using that approach would investigate An engineer expects a CLI alias to change the persistent device configuration instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The old physical port mapping was reused without reconciling current interface identifiers.