Question 450
A new leaf is connected to a spare spine port outside its assigned topology and the build dashboard reports cabling anomalies before deployment. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
This control reduces recurrence of the same class of failure: Apstra uses planned physical link relationships and observed neighbor data to validate whether actual cabling matches the staged blueprint. Apply the recurring practice: Reconcile physical patch records and blueprint cable maps after every rack move or spine port change. The previous example was: A new leaf is connected to a spare spine port outside its assigned topology and the build dashboard reports cabling anomalies before deployment.
Incorrect Answers
Successful device deployment depends on the required address and identifier resources being assigned consistently to the modeled fabric. Here, apstra uses planned physical link relationships and observed neighbor data to validate whether actual cabling matches the staged blueprint.
The supported Apstra deployment mode and device state determine how intent configuration is introduced and reconciled with the current platform. For this issue, compare the blueprint cable map with the discovered endpoint interfaces and correct or explicitly revise the intended physical connections.
Distinguish rendered preview, uncommitted intent and active configuration in commissioning records. Here, apstra uses planned physical link relationships and observed neighbor data to validate whether actual cabling matches the staged blueprint. Specifically for the prevention question, the case to validate is: A new leaf is connected to a spare spine port outside its assigned topology and the build dashboard reports cabling anomalies before deployment.