Question 530
During a production change postcheck at fictional Marble Bay Software, the change record states: An engineer approves an OSPF automation change after configuration diff alone even though neighbor states have changed unexpectedly. Which control best prevents this particular failure from recurring?
Explanation
Correct Answer
Version baseline snapshots and specify per-feature allowed changes rather than requiring exact equality for volatile counters. This prevents the recurrence because pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs. A matching immediate correction is: Capture structured prechange operational state with pyATS, apply the change, then compare relevant postchange state and assert expected invariants.
Incorrect Answers
The alternative verifies a different condition: latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient. The current case instead depends on: pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs. Confirm that “Version baseline snapshots and specify per-feature allowed changes rather than requiring exact equality for volatile counters”.
That test belongs to another control with this basis: hTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. In the current case, the governing reason is: pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs. The direct verification is “Version baseline snapshots and specify per-feature allowed changes rather than requiring exact equality for volatile counters”.
The alternative verifies a different condition: hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope. The current case instead depends on: pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs. Confirm that “Version baseline snapshots and specify per-feature allowed changes rather than requiring exact equality for volatile counters”.