Question 450
A dashboard reports that all switches are reachable while a recent staged policy change has not been deployed. Which initial check would most directly distinguish the likely cause?
Explanation
Correct Answer
This checks the relevant evidence first: compare dashboard health with active revision and pending staged configuration diffs. The underlying concept is that device health, intended active blueprint state and pending staged edits describe different dimensions of operations. After confirming the finding, a controlled remediation is to use each blueprint tab for its intended lifecycle step and deploy changes only after authorized review.
Incorrect Answers
“Compare staged differences with active configuration and deployment status before testing production traffic” is associated with a distinct issue: A service owner tests a new VRF assignment while the proposed change appears only in the Staged view. By contrast, the actual problem is: A dashboard reports that all switches are reachable while a recent staged policy change has not been deployed. The relevant inspection is: Compare dashboard health with active revision and pending staged configuration diffs. The most discriminating first check is “Compare dashboard health with active revision and pending staged configuration diffs”.
The option “Inspect the Uncommitted diff and attribution for every pending blueprint change” is useful in a different setting: A blueprint has accumulated unrelated uncommitted routing and rack modifications from different change windows. The case being tested is: A dashboard reports that all switches are reachable while a recent staged policy change has not been deployed. The relevant inspection is: Compare dashboard health with active revision and pending staged configuration diffs. The most discriminating first check is “Compare dashboard health with active revision and pending staged configuration diffs”.
“Determine whether the unwanted modification exists only in Staged or in the Active revision” is relevant to a different condition: A designer notices an accidental rack parameter change before any blueprint commit has occurred. The stated question instead concerns: A dashboard reports that all switches are reachable while a recent staged policy change has not been deployed. The relevant inspection is: Compare dashboard health with active revision and pending staged configuration diffs. The most discriminating first check is “Compare dashboard health with active revision and pending staged configuration diffs”.