Question 390
A fabric designer relies on manually entered BGP numbers for each new rack even though the standard build requires controlled assignment from the intended resource ranges. 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 resource pools provide managed allocation of identifiers such as ASNs for the chosen fabric policy and must avoid unintended exhaustion or overlap. Apply the recurring practice: Maintain site ASN allocation records and resource-pool headroom in fabric growth reviews. The previous example was: A fabric designer relies on manually entered BGP numbers for each new rack even though the standard build requires controlled assignment from the intended resource ranges.
Incorrect Answers
The alternative applies to another Juniper security situation: A new blueprint must use an approved three-stage leaf–spine fabric, but the team chooses a template with an unrelated structure and expects switch placement to correct it later. That situation concerns apstra templates compose reusable design elements and networking policies into a blueprint starting structure, including its supported fabric topology. Its key condition is apstra resource pools provide managed allocation of identifiers such as ASNs for the chosen fabric policy and must avoid unintended exhaustion or overlap.
Requalify interface maps on hardware model changes, not only the template name. That concerns interface map matching logical roles to hardware, while the issue here is ASN resource pool allocation in design. Review the expected number and role of ASNs, expand or choose a nonconflicting resource pool and verify blueprint allocation.
Validate logical port capacity and role allocation before approving physical device models for a template. Here, apstra resource pools provide managed allocation of identifiers such as ASNs for the chosen fabric policy and must avoid unintended exhaustion or overlap.