Question 370
A design authority wants consistent fabric overlay and underlay behavior across locations but starts separate blueprints without reusing the standard template policies. 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. Version controlled templates and review them before site-scale replication. That is important in this case because apstra templates compose reusable design elements and networking policies into a blueprint starting structure, including its supported fabric topology. The scenario was: A design authority wants consistent fabric overlay and underlay behavior across locations but starts separate blueprints without reusing the standard template policies.
Incorrect Answers
Recompute spine port and bandwidth demand before modifying the number of racks or uplinks per leaf. That concerns spine-capacity planning from oversubscription, while the issue here is template selection and Clos topology policy. Select or revise the approved template and verify its rack types, spine layout and protocol policy before creating the site blueprint.
Physical port breakout and available speed modes constrain which logical port groups can be mapped to actual switch interfaces. However, the present prevention decision is grounded in: A design authority wants consistent fabric overlay and underlay behavior across locations but starts separate blueprints without reusing the standard template policies. For this issue, select or revise the approved template and verify its rack types, spine layout and protocol policy before creating the site blueprint.
Review endpoint attachment diversity in rack-type design approvals and connectivity tests. Here, apstra templates compose reusable design elements and networking policies into a blueprint starting structure, including its supported fabric topology.