Question 230
A new data center team believes every switch is the authoritative fabric design repository, so it bypasses the Apstra server when modifying common VXLAN policy. 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. Treat the blueprint as the approved change source for managed fabric features and audit out-of-band edits. Intent-based network operations coordinate configuration from a shared model rather than accepting independent device edits as authoritative.
Incorrect Answers
Previously collected telemetry may remain displayed after management collection stops and must not be mistaken for a live measurement. Here, the Apstra server maintains the managed blueprint intent and derives coordinated device configurations from that centralized model.
Preserve time synchronization and documented event-source mappings for blueprint and network incident response. That concerns apstra event log and syslog evidence distinction, while the issue here is apstra server as intent and blueprint coordinator. Stage the intended change in the managed blueprint, validate the generated diffs and deploy through the supported Apstra commit workflow.
Require an active-state verification step for every GUI-driven network change. Here, the Apstra server maintains the managed blueprint intent and derives coordinated device configurations from that centralized model. Specifically for the prevention question, the case to validate is: A new data center team believes every switch is the authoritative fabric design repository, so it bypasses the Apstra server when modifying common VXLAN policy.