Question 160
At Baystone Municipal Networks, while committing an SR Linux configuration change, the data center fabric team observes: An operator inspects an IPv4 route in a tenant instance but checks the default IPv4 table. Which review gate should be added to prevent the same error?
Explanation
Correct Answer
At Baystone Municipal Networks, while committing an SR Linux configuration change, the preventive control is: Include routing-instance names in troubleshooting artifacts. It catches the same mechanism (The diagnostic omits the selected network instance during route lookup) before the symptom recurs. An appropriate regression observation is: The test prefix and its selected next hops appear only in the expected routing instance.
Incorrect Answers
At Baystone Municipal Networks, while committing an SR Linux configuration change, this option proposes: Update physical-to-logical interface mappings after hardware changes. The option describes a different failure mode: A fabric team applies a new interface description to the wrong port after a chassis replacement. It would address The old physical port mapping was reused without reconciling current interface identifiers, but here the case reports An operator inspects an IPv4 route in a tenant instance but checks the default IPv4 table. The current required evidence is: The test prefix and its selected next hops appear only in the expected routing instance.
At Baystone Municipal Networks, while committing an SR Linux configuration change, this option proposes: Keep an optics and interface compatibility checklist for replacements. That choice would be more relevant when this different symptom occurs: A 100G uplink remains down after an optics swap despite a valid peer port. The present scenario instead points to: The diagnostic omits the selected network instance during route lookup. The correct resolution has its own verification outcome: The test prefix and its selected next hops appear only in the expected routing instance.
At Baystone Municipal Networks, while committing an SR Linux configuration change, this option proposes: Serialize conflicting maintenance or require peer review of candidate differences. This is a valid category of fabric maintenance for another scenario (Two administrators apply incompatible pending edits to the same SR Linux device), not the targeted action for Baystone Municipal Networks. The distinction is the actual cause: The diagnostic omits the selected network instance during route lookup.