Question 630
A blueprint expansion involves another leaf pair, but its rack type and resource demand have not been reconciled with spare spines and address pools. 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: Supported Apstra fabric expansion stages a rack instance using design objects and validates required connectivity and resources before deployment. Apply the recurring practice: Run capacity and link-plan checks before every add-rack operation. The previous example was: A blueprint expansion involves another leaf pair, but its rack type and resource demand have not been reconciled with spare spines and address pools.
Incorrect Answers
The alternative applies to another Juniper security situation: An engineer submits a commit after a large rack addition and assumes device configurations are immediately consistent while some deployment tasks remain in progress. That situation concerns committing desired intent initiates validated deployment work whose task outcomes and device states must be checked before declaring network convergence. Its key condition is supported Apstra fabric expansion stages a rack instance using design objects and validates required connectivity and resources before deployment.
Require a postcommit active-state receipt for changes to rack or tenant services. That concerns staged blueprint versus active network intent, while the issue here is adding a rack to a running fabric. Add the approved rack type, verify fabric port and resource availability, complete build assignments and commit only the validated expansion.
Update generic system inventory and connectivity templates during endpoint onboarding. Here, supported Apstra fabric expansion stages a rack instance using design objects and validates required connectivity and resources before deployment.