Question 620
A data center change must touch only racks with an approved maintenance tag, yet the team manually enumerates racks from a stale spreadsheet. 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 tag definitions and include selection-scope reviews in bulk blueprint updates. Search and metadata improve change targeting, but do not replace verification of the objects returned.
Incorrect Answers
The alternative applies to another Juniper security situation: An administrator stages an incorrect port map but no commit has occurred, and the incident team starts a full historical network rollback unnecessarily. That situation concerns the Apstra Revert action on uncommitted changes can discard staged changes that have not yet become the active blueprint. Its key condition is apstra tags and object search can identify a constrained set of blueprint items for inspection and controlled modification.
Time Voyager stores retained committed revision checkpoints with descriptions and configurable retention, rather than an unbounded perfect history. For this issue, filter the active blueprint by verified attributes and tags, review object identities and stage changes only for approved targets.
Add task-status and targeted service checks after every operational blueprint commit. Here, apstra tags and object search can identify a constrained set of blueprint items for inspection and controlled modification.