Question 670
A fabric alarms on a tenant service while recent task errors point to one spine configuration push, but operations investigates only endpoint VLAN tagging. 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. Preserve cross-layer triage steps and recent change context in blueprint incident workflows. That is important in this case because apstra's blueprint model and operational telemetry allow analysts to follow dependencies across service, device, cabling, configuration and analytics evidence. The scenario was: A fabric alarms on a tenant service while recent task errors point to one spine configuration push, but operations investigates only endpoint VLAN tagging.
Incorrect Answers
Committing desired intent initiates validated deployment work whose task outcomes and device states must be checked before declaring network convergence. Here, apstra's blueprint model and operational telemetry allow analysts to follow dependencies across service, device, cabling, configuration and analytics evidence.
Version shared property values and review all consumers before modifying common settings. That concerns property sets used by repeated configuration intent, while the issue here is blueprint root cause investigation across objects. Correlate the affected intent object with recent tasks, physical link status, device state and overlay routes, then fix the evidenced failing dependency.
Staged blueprint intent is the editable candidate model and does not become active device state until validated and committed. For this issue, correlate the affected intent object with recent tasks, physical link status, device state and overlay routes, then fix the evidenced failing dependency.