Question 180
At Clearline Rail Logistics, while bringing up a server-facing interface, the data center fabric team observes: A management query returns incomplete output because an operator filters out relevant configuration branches. What repeatable acceptance check would reduce recurrence?
Explanation
Correct Answer
At Clearline Rail Logistics, while bringing up a server-facing interface, keep source and filter expressions alongside captured troubleshooting output. This ongoing review specifically addresses: A broad CLI match filter excludes dependent configuration or state fields. It should remain part of change acceptance, not only incident closure.
Incorrect Answers
At Clearline Rail Logistics, while bringing up a server-facing interface, this option proposes: Inspect full interface paths when reviewing routed interface changes. The option describes a different failure mode: A routed port is configured with an IP address under an unexpected subinterface context. It would address The IP addressing change was attached to the wrong interface or subinterface scope, but here the case reports A management query returns incomplete output because an operator filters out relevant configuration branches. The current required evidence is: The report includes both the intended setting and relevant dependent operational state.
At Clearline Rail Logistics, while bringing up a server-facing interface, this option proposes: Require tested checkpoints for changes with material reachability risk. This is a valid category of fabric maintenance for another scenario (An engineer makes a risky multi-node edit without saving a known-good baseline), not the targeted action for Clearline Rail Logistics. The distinction is the actual cause: A broad CLI match filter excludes dependent configuration or state fields.
At Clearline Rail Logistics, while bringing up a server-facing interface, this option proposes: Serialize conflicting maintenance or require peer review of candidate differences. Although related to SR Linux CLI, model configuration and interfaces, the proposed change fits another mechanism: The change process lacks candidate-change coordination and effective-diff review. The evidence in the current case requires a different result: The report includes both the intended setting and relevant dependent operational state.