Question 730
A rack contains correctly discovered storage links and an approved tenant VLAN, yet its attachment template was created but never applied to the intended links. 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. Include connectivity-template assignment checks in endpoint onboarding and movement workflows. That is important in this case because creating a tenant network and creating a connectivity template are separate from assigning the template to the intended connected interfaces. The scenario was: A rack contains correctly discovered storage links and an approved tenant VLAN, yet its attachment template was created but never applied to the intended links.
Incorrect Answers
Review route changes and policy enforcement coverage in one tenant change-control workflow. That concerns tenant security policy enforcement alongside routing, while the issue here is connectivity template assignment to generic-system links. Apply the reviewed connectivity template to the correct generic-system attachment, validate staging and commit its network changes.
An Apstra routing zone represents Layer 3 tenancy and maps associated networks into a distinct VRF routing domain for isolation. However, the present prevention decision is grounded in: A rack contains correctly discovered storage links and an approved tenant VLAN, yet its attachment template was created but never applied to the intended links. For this issue, apply the reviewed connectivity template to the correct generic-system attachment, validate staging and commit its network changes.
Track border interface, routing-zone and peer parameters together for tenant interconnect changes. Here, creating a tenant network and creating a connectivity template are separate from assigning the template to the intended connected interfaces.