Question 660
A switch shows configuration not managed by the blueprint, and an engineer assumes a pristine representation and an incremental diff carry identical information. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
This control reduces recurrence of the same class of failure: Apstra configuration views can distinguish generated complete intent, incremental modifications and pristine baseline perspectives with different diagnostic purposes. Apply the recurring practice: Record the configuration-view type and platform state in deployment approvals. The previous example was: A switch shows configuration not managed by the blueprint, and an engineer assumes a pristine representation and an incremental diff carry identical information.
Incorrect Answers
Preserve cross-layer triage steps and recent change context in blueprint incident workflows. That concerns blueprint root cause investigation across objects, while the issue here is rendered versus incremental versus pristine configuration. Select the appropriate supported rendered, incremental or pristine comparison and inspect the actual intended differences before committing changes.
Supported Apstra fabric expansion stages a rack instance using design objects and validates required connectivity and resources before deployment. However, the present prevention decision is grounded in: A switch shows configuration not managed by the blueprint, and an engineer assumes a pristine representation and an incremental diff carry identical information. For this issue, select the appropriate supported rendered, incremental or pristine comparison and inspect the actual intended differences before committing changes.
Standardize tag definitions and include selection-scope reviews in bulk blueprint updates. Here, apstra configuration views can distinguish generated complete intent, incremental modifications and pristine baseline perspectives with different diagnostic purposes.