Question 110
At Windmere Digital Commerce, while reviewing interface counters, the data center fabric team observes: A service has healthy IPv4 reachability but its IPv6 traffic fails due to missing local addressing. Which evidence directly validates the intended repair?
Explanation
Correct Answer
At Windmere Digital Commerce, while reviewing interface counters, for Windmere Digital Commerce, accept the repair only after this observation: A controlled IPv6 path succeeds through the correct network instance. The test distinguishes real recovery from a superficial status change.
Incorrect Answers
At Windmere Digital Commerce, while reviewing interface counters, this option proposes: Link status and physical error counters are healthy on both ends of a supported connection. 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 subinterface or IP-VRF lacks the intended IPv6 address or route information. The correct resolution has its own verification outcome: A controlled IPv6 path succeeds through the correct network instance.
At Windmere Digital Commerce, while reviewing interface counters, this option proposes: A rehearsal restores the known-good state if the change acceptance test fails. Although related to SR Linux CLI, model configuration and interfaces, the proposed change fits another mechanism: The change procedure omitted configuration checkpoints and rollback criteria. The evidence in the current case requires a different result: A controlled IPv6 path succeeds through the correct network instance.
At Windmere Digital Commerce, while reviewing interface counters, this option proposes: The report includes both the intended setting and relevant dependent operational state. Using that approach would investigate A management query returns incomplete output because an operator filters out relevant configuration branches instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The subinterface or IP-VRF lacks the intended IPv6 address or route information.