Question 410
A shared Apstra design catalog contains production and laboratory logical devices, yet nobody applies consistent metadata for filtering or lifecycle ownership. 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. Audit catalog tags and ownership during design-object revision or deprecation. Metadata improves design selection and traceability but cannot repair an incorrect logical topology or interface map.
Incorrect Answers
Underlay interface and loopback addressing requires available appropriately scoped address resources independent of tenant overlay identifiers. Here, design tags provide organizational metadata for discovering and grouping catalog objects; tags do not themselves define forwarding or fabric port behavior.
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 design tags for logical organization. Apply an approved tagging convention and use tagged catalog searches to select the intended logical device, rack type or template.
Requalify interface maps on hardware model changes, not only the template name. Here, design tags provide organizational metadata for discovering and grouping catalog objects; tags do not themselves define forwarding or fabric port behavior.