Question 100
At Clearline Municipal Networks, while checking a network-instance assignment, the data center fabric team observes: An engineer places an IP interface in a default network instance instead of the assigned tenant VRF. What repeatable acceptance check would reduce recurrence?
Explanation
Correct Answer
At Clearline Municipal Networks, while checking a network-instance assignment, use this repeatable control: Include network-instance binding in interface peer reviews. Its scope is the problem (The interface-to-network-instance binding does not follow the tenancy design), not an unrelated network maintenance procedure.
Incorrect Answers
At Clearline Municipal Networks, while checking a network-instance assignment, this option proposes: Keep release-specific command examples and avoid vendor CLI substitution. Using that approach would investigate A junior operator tries to use a command copied from a different network operating system 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 Clearline Municipal Networks, while checking a network-instance assignment, this option proposes: Prefer schema-backed data for automated state collection. The alternative focuses on The integration assumes display column positions are a stable machine-readable interface, 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 Clearline Municipal Networks, while checking a network-instance assignment, this option proposes: Alert on abnormal MAC-move events while reviewing multi-homing designs. This option assumes the other problem (A device reports repeated MAC moves between two attachment points during a suspected Layer 2 loop) is present. The case instead describes An engineer places an IP interface in a default network instance instead of the assigned tenant VRF, for which the causal issue is The interface-to-network-instance binding does not follow the tenancy design.