Question 210
At fictional Cedarbridge Care Systems, during a campus API automation rollout, the operator observes: A VLAN deployment continues after half the switches fail connectivity tests, creating an incomplete campus rollout. Which explanation best matches the actual broken dependency?
Explanation
Correct Answer
Safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. The corresponding repair is: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. Acceptance should show: A failed device causes a controlled halt and restoration, and successful devices pass their intended config comparisons. Applied here, the relevant facts are: A VLAN deployment continues after half the switches fail connectivity tests, creating an incomplete campus rollout. The question asks which explanation best matches the actual broken dependency.
Incorrect Answers
This alternative is a response to another technical cause: The corresponding repair is: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. The reported case instead depends on: The corresponding repair is: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. The action that directly addresses it is “Safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed”.
The proposed action belongs to the mechanism: The corresponding repair is: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key. Here the stated fault follows a different mechanism: The corresponding repair is: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. The corrective choice is “Safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed”.
The offered action targets: The corresponding repair is: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. The case facts point instead to: The corresponding repair is: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. Implement “Safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed” to address that specific condition.