Question 460
An administrator discovers a bad blueprint deployment and needs to restore a prior retained intent state. Which evidence most directly verifies the intended network outcome?
Explanation
Correct Answer
This directly tests the desired result: confirm active blueprint state matches the intended retained revision and critical services recover. The decisive investigation is to inspect available retained revisions, current uncommitted changes and the revision's applicability to present devices. The governing principle is that Apstra Time Voyager supports controlled movement to retained blueprint revisions, subject to compatibility and staged-change constraints.
Incorrect Answers
The option “Prove the revised blueprint builds with valid allocations and switches converge on intended active state” is useful in a different setting: A historical revision would restore a system ID that has been reassigned to another device since it was first recorded. The case being tested is: An administrator discovers a bad blueprint deployment and needs to restore a prior retained intent state. Apstra Time Voyager supports controlled movement to retained blueprint revisions, subject to compatibility and staged-change constraints. The direct acceptance evidence is “Confirm active blueprint state matches the intended retained revision and critical services recover”.
“Confirm no required pending work was silently lost and the correct historical revision became active” is relevant to a different condition: An operator has valuable staged changes when another administrator proposes jumping to an older blueprint revision. The stated question instead concerns: An administrator discovers a bad blueprint deployment and needs to restore a prior retained intent state. Apstra Time Voyager supports controlled movement to retained blueprint revisions, subject to compatibility and staged-change constraints. The direct acceptance evidence is “Confirm active blueprint state matches the intended retained revision and critical services recover”.
That choice—“Confirm the pending diff no longer includes the bad edit and the active blueprint is unchanged”—addresses this other problem: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. Here the scenario is: An administrator discovers a bad blueprint deployment and needs to restore a prior retained intent state. Apstra Time Voyager supports controlled movement to retained blueprint revisions, subject to compatibility and staged-change constraints. The direct acceptance evidence is “Confirm active blueprint state matches the intended retained revision and critical services recover”.