Question 610
An operations team must compare pristine, incremental and rendered configuration views before a planned device update. Which shortcut would be most likely to undermine this objective?
Explanation
Correct Answer
This is the unsafe shortcut to avoid: assume every configuration view is identical and blindly paste one into the device CLI. It violates the principle that configuration views represent different aspects of the managed device configuration and should be interpreted in their proper context. An appropriate alternative is to select the approved deployment or diagnostic view before reviewing and applying configuration diffs.
Incorrect Answers
That choice—“Treat the existence of a rendered config file as proof of deployment to every switch”—addresses this other problem: A design is staged and rendered correctly, but a production switch still uses the previous running configuration. Here the scenario is: An operations team must compare pristine, incremental and rendered configuration views before a planned device update. Configuration views represent different aspects of the managed device configuration and should be interpreted in their proper context. The directly relevant unsafe shortcut is “Assume every configuration view is identical and blindly paste one into the device CLI”.
The option “Skip diff review and declare the change complete as soon as the design editor saves it” is useful in a different setting: A team needs to roll out a fabric change safely but its change record mixes staging a modification with committing the active state. The case being tested is: An operations team must compare pristine, incremental and rendered configuration views before a planned device update. Configuration views represent different aspects of the managed device configuration and should be interpreted in their proper context. The directly relevant unsafe shortcut is “Assume every configuration view is identical and blindly paste one into the device CLI”.
“Assume an SSH prompt proves the device is fully under Apstra management” is relevant to a different condition: A new QFX leaf responds to management pings while the Apstra device manager reports no valid agent identity. The stated question instead concerns: An operations team must compare pristine, incremental and rendered configuration views before a planned device update. Configuration views represent different aspects of the managed device configuration and should be interpreted in their proper context. The directly relevant unsafe shortcut is “Assume every configuration view is identical and blindly paste one into the device CLI”.