Question 350
A builder copies a single-leaf rack layout into a dual-leaf production pod but neglects the second leaf and generic-system attachments specified by the intended rack pattern. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
The preventive practice is aligned with the diagnosed mechanism, not an unrelated protection. Standardize reviewed rack-type patterns and check their logical structure before expanding a blueprint. Reusable rack abstractions reduce drift, but only if their declared components match the actual infrastructure.
Incorrect Answers
Version controlled templates and review them before site-scale replication. That concerns template selection and Clos topology policy, while the issue here is rack type composition for reusable racks. Choose or design a rack type whose leaf count, generic-system endpoints and link relationships match the approved physical rack.
An Apstra logical device models port counts, speeds and roles without requiring a specific vendor hardware platform at the initial design stage. For this issue, choose or design a rack type whose leaf count, generic-system endpoints and link relationships match the approved physical rack.
Review endpoint attachment diversity in rack-type design approvals and connectivity tests. Here, an Apstra rack type models repeated rack structure using logical leaf/access/generic devices and their intended links independent of vendor model. Specifically for the prevention question, the case to validate is: A builder copies a single-leaf rack layout into a dual-leaf production pod but neglects the second leaf and generic-system attachments specified by the intended rack pattern.