Question 250
A new fabric commit causes service degradation and the team wants to return to a known earlier revision with minimal manual reconstruction. 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
That choice—“Prove the revised blueprint builds with valid allocations and switches converge on intended active state”—addresses this other problem: An engineer wants to return to a blueprint commit created before several resource pool and hardware changes. Here the scenario is: A new fabric commit causes service degradation and the team wants to return to a known earlier revision with minimal manual reconstruction. 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 the pending diff no longer includes the bad edit and the active blueprint is unchanged” is associated with a distinct issue: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. By contrast, the actual problem is: A new fabric commit causes service degradation and the team wants to return to a known earlier revision with minimal manual reconstruction. 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”.
The option “Confirm no required pending work was silently lost and the correct historical revision became active” is useful in a different setting: An operator has valuable staged changes when another administrator proposes jumping to an older blueprint revision. The case being tested is: A new fabric commit causes service degradation and the team wants to return to a known earlier revision with minimal manual reconstruction. 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”.