Question 590
A quarterly change-audit request asks how many historical blueprint revisions remain available, but the operator assumes unlimited retention and never checks 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. Monitor revision retention and require meaningful descriptions for significant blueprint commits. Auditable recovery depends on the existence and intelligibility of retained committed states.
Incorrect Answers
Apstra configuration views can distinguish generated complete intent, incremental modifications and pristine baseline perspectives with different diagnostic purposes. Here, time Voyager stores retained committed revision checkpoints with descriptions and configurable retention, rather than an unbounded perfect history.
Label staged experiments clearly and use controlled revert procedures before escalating to time-travel recovery. That concerns reverting only uncommitted proposed changes, while the issue here is revision retention and commit descriptions. Confirm the supported revision retention settings and document each meaningful commit so a known-good restore point can be identified.
Committing desired intent initiates validated deployment work whose task outcomes and device states must be checked before declaring network convergence. For this issue, confirm the supported revision retention settings and document each meaningful commit so a known-good restore point can be identified.