Question 520
A service owner tests a new VRF assignment while the proposed change appears only in the Staged view. Which shortcut would be most likely to undermine this objective?
Explanation
Correct Answer
This is the unsafe shortcut to avoid: assume that viewing a change under Staged applies it instantly across the entire fabric. It violates the principle that staged blueprint intent can differ from the deployed active revision until approved changes are committed. An appropriate alternative is to complete review and commit of the authorized staged change, then monitor device convergence.
Incorrect Answers
“Commit blindly and assume every outstanding uncommitted change belongs to the current ticket” is relevant to a different condition: Two changes are awaiting commit, and an operator wants to deploy only one without understanding the other outstanding edits. The stated question instead concerns: A service owner tests a new VRF assignment while the proposed change appears only in the Staged view. Staged blueprint intent can differ from the deployed active revision until approved changes are committed. The directly relevant unsafe shortcut is “Assume that viewing a change under Staged applies it instantly across the entire fabric”.
That choice—“Interpret a green dashboard as proof that every staged change has already been committed”—addresses this other problem: A network team needs to distinguish observed operational health from whether the desired blueprint configuration is active. Here the scenario is: A service owner tests a new VRF assignment while the proposed change appears only in the Staged view. Staged blueprint intent can differ from the deployed active revision until approved changes are committed. The directly relevant unsafe shortcut is “Assume that viewing a change under Staged applies it instantly across the entire fabric”.
“Use a historical revision rollback for every minor uncommitted typo without inspecting scope” 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 service owner tests a new VRF assignment while the proposed change appears only in the Staged view. Staged blueprint intent can differ from the deployed active revision until approved changes are committed. The directly relevant unsafe shortcut is “Assume that viewing a change under Staged applies it instantly across the entire fabric”.