Question 890
A spine upgrade may affect multiple leaf racks and VRFs, yet a team cannot explain the intended blast radius without traversing the Apstra topology model. 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. Run dependency queries before fabric maintenance and record their scope in the change ticket. Risk assessment improves when physical fault domains are traced to logical services rather than inferred from naming conventions.
Incorrect Answers
Maintain a reviewed inventory of probe scopes, required telemetry sources and intended thresholds. That concerns intent-Based Analytics probe definition, while the issue here is graph query for physical-to-virtual impact. Query the affected device's adjacent links and downstream virtual-network relationships, then verify the returned dependencies against current blueprint state.
Interface error and discard telemetry can reveal degraded forwarding even while physical link state remains up. However, the present prevention decision is grounded in: A spine upgrade may affect multiple leaf racks and VRFs, yet a team cannot explain the intended blast radius without traversing the Apstra topology model. For this issue, query the affected device's adjacent links and downstream virtual-network relationships, then verify the returned dependencies against current blueprint state.
Include intent-graph dependency checks in service-impact assessments for rack changes. Here, a relationship query can connect physical devices and links to dependent logical systems and services in the Apstra intent graph.