Question 520
A wiring team changes one redundant uplink plan and updates the patch spreadsheet but not the Apstra physical model before deployment. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
A lasting control should detect the original error before release. Make patch changes and blueprint topology changes part of one reviewed maintenance transaction. That is important in this case because a topology validation alert can mean observed cabling differs from the declared blueprint even when the chosen physical link could otherwise carry traffic. The scenario was: A wiring team changes one redundant uplink plan and updates the patch spreadsheet but not the Apstra physical model before deployment.
Incorrect Answers
Staged modeled changes and rendered previews are not automatically active until the supported deployment or commit workflow completes. Here, a topology validation alert can mean observed cabling differs from the declared blueprint even when the chosen physical link could otherwise carry traffic.
Review endpoint versus fabric-node roles before importing rack inventory. That concerns managed versus generic system classification, while the issue here is initial cable mismatch versus intentional alternate topology. Decide whether the physical patch or approved intent should change, then align the cable map and revalidate the leaf-spine adjacency.
The supported Apstra deployment mode and device state determine how intent configuration is introduced and reconciled with the current platform. For this issue, decide whether the physical patch or approved intent should change, then align the cable map and revalidate the leaf-spine adjacency.