Question 90
At Baystone Rail Logistics, while validating an automation transaction, the data center fabric team observes: A configuration automation script breaks after parsing human-formatted CLI tables. What observation should be required before this case is closed?
Explanation
Correct Answer
At Baystone Rail Logistics, while validating an automation transaction, this result is the relevant closure evidence: The parser reads the required values after output formatting changes without field misalignment. It checks the effect of: Use the supported model-driven JSON output or management API with named fields. The underlying issue was: The integration assumes display column positions are a stable machine-readable interface.
Incorrect Answers
At Baystone Rail Logistics, while validating an automation transaction, this option proposes: The final committed diff contains both approved intents and no overwritten change. That choice would be more relevant when this different symptom occurs: Two administrators apply incompatible pending edits to the same SR Linux device. The present scenario instead points to: The integration assumes display column positions are a stable machine-readable interface. The correct resolution has its own verification outcome: The parser reads the required values after output formatting changes without field misalignment.
At Baystone Rail Logistics, while validating an automation transaction, this option proposes: The intended port displays the approved description and the neighbor mapping is correct. This is a valid category of fabric maintenance for another scenario (A fabric team applies a new interface description to the wrong port after a chassis replacement), not the targeted action for Baystone Rail Logistics. The distinction is the actual cause: The integration assumes display column positions are a stable machine-readable interface.
At Baystone Rail Logistics, while validating an automation transaction, this option proposes: The test prefix and its selected next hops appear only in the expected routing instance. Although related to SR Linux CLI, model configuration and interfaces, the proposed change fits another mechanism: The diagnostic omits the selected network instance during route lookup. The evidence in the current case requires a different result: The parser reads the required values after output formatting changes without field misalignment.