Question 510
A network change report says configuration was activated on every leaf, but the task history identifies a rejected command on one device. 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: A successful request to deploy does not prove completion; Apstra task state and device-level error details determine the actual result. Apply the recurring practice: Monitor and archive deployment task outcomes before closing change tickets. The previous example was: A network change report says configuration was activated on every leaf, but the task history identifies a rejected command on one device.
Incorrect Answers
The alternative applies to another Juniper security situation: A builder expects a leaf to appear active immediately after discovery, although it still has unresolved cabling and interface-map requirements. That situation concerns apstra distinguishes discovered, staged, deployable and active device conditions based on build prerequisites and completed management actions. Its key condition is a successful request to deploy does not prove completion; Apstra task state and device-level error details determine the actual result.
Successful device deployment depends on the required address and identifier resources being assigned consistently to the modeled fabric. For this issue, inspect active task progress and the failed device operation, resolve the supported configuration issue and verify final active state.
Include agent version and management-channel prerequisites in leaf onboarding checklists. Here, a successful request to deploy does not prove completion; Apstra task state and device-level error details determine the actual result.