Question 210
At Winterfield Rail Logistics, while bringing up a server-facing interface, the data center fabric team observes: An operator deletes an SR Linux subinterface that still carries an active tenant service. What test result proves the affected fabric function now works?
Explanation
Correct Answer
At Winterfield Rail Logistics, while bringing up a server-facing interface, for Winterfield Rail Logistics, accept the repair only after this observation: The tenant service remains active on its intended replacement attachment. The test distinguishes real recovery from a superficial status change.
Incorrect Answers
At Winterfield Rail Logistics, while bringing up a server-facing interface, this option proposes: A corrected link maintains stable operational status with no recurring error growth. This option assumes the other problem (A high-speed interface shows rapidly increasing errors while routing sessions still intermittently recover) is present. The case instead describes An operator deletes an SR Linux subinterface that still carries an active tenant service, for which the causal issue is Dependency checks were skipped before removing a network resource.
At Winterfield Rail Logistics, while bringing up a server-facing interface, this option proposes: A new session retains committed network settings regardless of interactive alias availability. The option describes a different failure mode: An engineer expects a CLI alias to change the persistent device configuration. It would address An interactive command shortcut has been confused with configuration datastore content, but here the case reports An operator deletes an SR Linux subinterface that still carries an active tenant service. The current required evidence is: The tenant service remains active on its intended replacement attachment.
At Winterfield Rail Logistics, while bringing up a server-facing interface, this option proposes: The parser reads the required values after output formatting changes without field misalignment. That choice would be more relevant when this different symptom occurs: A configuration automation script breaks after parsing human-formatted CLI tables. The present scenario instead points to: Dependency checks were skipped before removing a network resource. The correct resolution has its own verification outcome: The tenant service remains active on its intended replacement attachment.