Question 680
A staged multitenancy change passes initial validation but one leaf reports an execution error during the active task, and the service owner announces completion prematurely. 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. Add task-status and targeted service checks after every operational blueprint commit. Successful submission of an automation change is not evidence that its entire distributed deployment has finished successfully.
Incorrect Answers
Record descriptive commit summaries and preserve sufficient revision retention for operational rollback objectives. That concerns time Voyager returning to earlier revision, while the issue here is active task completion versus successful commit intention. Check task status and per-device results, resolve any failed operations and confirm active model and observed device configuration match.
Time Voyager stores retained committed revision checkpoints with descriptions and configurable retention, rather than an unbounded perfect history. However, the present prevention decision is grounded in: A staged multitenancy change passes initial validation but one leaf reports an execution error during the active task, and the service owner announces completion prematurely. For this issue, check task status and per-device results, resolve any failed operations and confirm active model and observed device configuration match.
Run capacity and link-plan checks before every add-rack operation. Here, committing desired intent initiates validated deployment work whose task outcomes and device states must be checked before declaring network convergence.