Question 170
At Northpoint Energy Services, while reviewing interface counters, the data center fabric team observes: An engineer places an IP interface in a default network instance instead of the assigned tenant VRF. What observation should be required before this case is closed?
Explanation
Correct Answer
At Northpoint Energy Services, while reviewing interface counters, the decisive validation is: Traffic sourced in the tenant VRF follows its own lookup table without appearing in unrelated VRFs. It verifies that the change (Bind the approved interface to the intended IP-VRF and check the resulting routes) resolved the mechanism: The interface-to-network-instance binding does not follow the tenancy design.
Incorrect Answers
At Northpoint Energy Services, while reviewing interface counters, this option proposes: The final committed diff contains both approved intents and no overwritten change. Using that approach would investigate Two administrators apply incompatible pending edits to the same SR Linux device instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The interface-to-network-instance binding does not follow the tenancy design.
At Northpoint Energy Services, while reviewing interface counters, this option proposes: The report includes both the intended setting and relevant dependent operational state. The alternative focuses on A broad CLI match filter excludes dependent configuration or state fields, not on the stated defect. For this scenario the expected acceptance result would be: Traffic sourced in the tenant VRF follows its own lookup table without appearing in unrelated VRFs.
At Northpoint Energy Services, while reviewing interface counters, this option proposes: The intended port displays the approved description and the neighbor mapping is correct. It tests a different symptom: A fabric team applies a new interface description to the wrong port after a chassis replacement. For the observed case, the relevant distinction is The interface-to-network-instance binding does not follow the tenancy design, with verification: Traffic sourced in the tenant VRF follows its own lookup table without appearing in unrelated VRFs.