Question 230
In the fictional Summit-4 west pod, a change-freeze exception for a narrow operational fault, the team reports that a two-tier Clos fabric needs resilient leaf-to-spine paths. The planned change is "Connect every leaf to each spine in the same fabric." Which post-change observation best validates the intended technical behavior?
Explanation
Correct Answer
Multiple spine paths avoid a single aggregation dependency and permit ECMP. The option uses “Verify that each leaf has live routed adjacencies to the intended spines” to address “a two-tier Clos fabric needs resilient leaf-to-spine paths”. The acceptance test is: each leaf has live routed adjacencies to the intended spines.
Incorrect Answers
“Confirm that a documentation ticket is marked complete, without checking switch state or forwarding behavior” targets a different operation from the reported requirement: “a two-tier Clos fabric needs resilient leaf-to-spine paths”. Multiple spine paths avoid a single aggregation dependency and permit ECMP. The confirming result is: each leaf has live routed adjacencies to the intended spines.
“Check only that the device hostname is listed in the inventory, without examining leaf-spine adjacency behavior” targets a different operation from the reported requirement: “a two-tier Clos fabric needs resilient leaf-to-spine paths”. Multiple spine paths avoid a single aggregation dependency and permit ECMP. The confirming result is: each leaf has live routed adjacencies to the intended spines.
“Use an unrelated tenant dashboard as proof, without verifying the required leaf-spine adjacency condition” targets a different operation from the reported requirement: “a two-tier Clos fabric needs resilient leaf-to-spine paths”. Multiple spine paths avoid a single aggregation dependency and permit ECMP. The confirming result is: each leaf has live routed adjacencies to the intended spines.