Question 130
At Wildflower Municipal Networks, while committing an SR Linux configuration change, the data center fabric team observes: A new network interface is administratively disabled although optics and cabling are healthy. What test result proves the affected fabric function now works?
Explanation
Correct Answer
At Wildflower Municipal Networks, while committing an SR Linux configuration change, the decisive validation is: The port reports administratively and operationally up with expected link negotiation. It verifies that the change (Apply the intended administrative enable state after validating the physical port assignment) resolved the mechanism: The interface is not enabled in the applicable SR Linux configuration.
Incorrect Answers
At Wildflower Municipal Networks, while committing an SR Linux configuration change, this option proposes: A rehearsal restores the known-good state if the change acceptance test fails. 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 Wildflower Municipal Networks. The distinction is the actual cause: The interface is not enabled in the applicable SR Linux configuration.
At Wildflower Municipal Networks, while committing an SR Linux configuration change, this option proposes: A corrected link maintains stable operational status with no recurring error growth. Although related to SR Linux CLI, model configuration and interfaces, the proposed change fits another mechanism: The fault is in the physical link or transceiver rather than solely in routing policy. The evidence in the current case requires a different result: The port reports administratively and operationally up with expected link negotiation.
At Wildflower Municipal Networks, while committing an SR Linux configuration change, this option proposes: The intended leaf setting appears under the correct model and passes a controlled commit. The alternative focuses on The intended SR Linux CLI is YANG model-driven and has a different configuration hierarchy, not on the stated defect. For this scenario the expected acceptance result would be: The port reports administratively and operationally up with expected link negotiation.