Question 670
A team needs to group rack devices for maintenance based on operational ownership without renaming every node. Which shortcut would be most likely to undermine this objective?
Explanation
Correct Answer
This is the unsafe shortcut to avoid: run changes against every switch because tags are only informational. It violates the principle that Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity. An appropriate alternative is to apply consistent approved tags and verify the automation selector matches only the intended objects.
Incorrect Answers
That choice—“Manually reuse an existing VTEP address to bypass resource exhaustion”—addresses this other problem: A new blueprint assigns every VTEP from a resource pool that is too small for the proposed rack count. Here the scenario is: A team needs to group rack devices for maintenance based on operational ownership without renaming every node. Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity. The directly relevant unsafe shortcut is “Run changes against every switch because tags are only informational”.
“Assume the logical device automatically creates additional physical interfaces on undersized hardware” is associated with a distinct issue: A site models 48 server attachments using a logical device profile that exposes only 32 suitable host interfaces. By contrast, the actual problem is: A team needs to group rack devices for maintenance based on operational ownership without renaming every node. Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity. The directly relevant unsafe shortcut is “Run changes against every switch because tags are only informational”.
The option “Assign VNIs by copying a number from an unrelated tenant's design sheet” is useful in a different setting: A data center creates two tenants with conflicting VNI allocations despite using a shared Apstra resource service. The case being tested is: A team needs to group rack devices for maintenance based on operational ownership without renaming every node. Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity. The directly relevant unsafe shortcut is “Run changes against every switch because tags are only informational”.