Question 550
A change request is approved based on a preview of a new rack, yet active blueprint state still reflects the original rack count. 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 a postcommit active-state receipt for changes to rack or tenant services. That is important in this case because staged blueprint intent is the editable candidate model and does not become active device state until validated and committed. The scenario was: A change request is approved based on a preview of a new rack, yet active blueprint state still reflects the original rack count.
Incorrect Answers
The alternative applies to another Juniper security situation: A production template revision accidentally alters several rack uplinks, and engineers need an auditable way to restore a prior validated network state. That situation concerns apstra Time Voyager retains committed blueprint revisions that can be selected for a controlled rollback and subsequent redeployment. Its key condition is staged blueprint intent is the editable candidate model and does not become active device state until validated and committed.
Update generic system inventory and connectivity templates during endpoint onboarding. That concerns adding a generic endpoint after blueprint deployment, while the issue here is staged blueprint versus active network intent. Review the staged change and uncommitted diff, commit after required validation, and confirm the active blueprint and affected devices.
Treat failed blueprint validation as a release blocker rather than a message to ignore. Here, staged blueprint intent is the editable candidate model and does not become active device state until validated and committed.