Question 370
A live rack cable is connected to the wrong spine port compared with the blueprint's intended cable map. Which evidence most directly verifies the intended network outcome?
Explanation
Correct Answer
This directly tests the desired result: confirm discovered links match the staged cable map and link-state anomalies clear. The decisive investigation is to compare LLDP-discovered endpoints and physical interface identifiers against the generated cable map. The governing principle is that cabling validation compares observed neighbor links against intended device/interface relationships.
Incorrect Answers
“Confirm all affected devices converge on the active blueprint revision without config drift” is associated with a distinct issue: A new switch reports Ready while its peers remain in a deployment-failed state after committing fabric intent. By contrast, the actual problem is: A live rack cable is connected to the wrong spine port compared with the blueprint's intended cable map. Cabling validation compares observed neighbor links against intended device/interface relationships. The direct acceptance evidence is “Confirm discovered links match the staged cable map and link-state anomalies clear”.
The option “Observe matching physical and logical connectivity and no unresolved cabling anomalies” is useful in a different setting: A staging team has different cable-map snapshots from design and observed discovery data. The case being tested is: A live rack cable is connected to the wrong spine port compared with the blueprint's intended cable map. Cabling validation compares observed neighbor links against intended device/interface relationships. The direct acceptance evidence is “Confirm discovered links match the staged cable map and link-state anomalies clear”.
“Confirm active intent, device configuration and required network tests agree on the intended result” is relevant to a different condition: A team needs to roll out a fabric change safely but its change record mixes staging a modification with committing the active state. The stated question instead concerns: A live rack cable is connected to the wrong spine port compared with the blueprint's intended cable map. Cabling validation compares observed neighbor links against intended device/interface relationships. The direct acceptance evidence is “Confirm discovered links match the staged cable map and link-state anomalies clear”.