Question 250
A change ticket is closed when a virtual network object appears in a dashboard, even though its blueprint commit remains pending validation. 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. Require an active-state verification step for every GUI-driven network change. That is important in this case because apstra presents modeled and staged intent separately from what has been committed and deployed on managed devices. The scenario was: A change ticket is closed when a virtual network object appears in a dashboard, even though its blueprint commit remains pending validation.
Incorrect Answers
Apstra device management and telemetry depend on working agent and control connectivity in addition to ordinary data-plane reachability. Here, apstra presents modeled and staged intent separately from what has been committed and deployed on managed devices.
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 UI versus active configuration state. Compare staged, uncommitted and active blueprint state, then commit the validated change before claiming production activation.
This choice would be assessed for a different data-center fabric or Apstra operational situation: A helpdesk analyst needs to inspect alarms but receives broad permissions to alter templates and commit production fabric changes. The present incident instead has this observed symptom: A change ticket is closed when a virtual network object appears in a dashboard, even though its blueprint commit remains pending validation. Its decisive constraint is apstra presents modeled and staged intent separately from what has been committed and deployed on managed devices.