Question 390
At fictional Cobalt Ridge Bank, an acceptance review of a campus API automation rollout finds: A one-time diagnostic query is forced through the same slow infrastructure apply workflow used for persistent configuration changes. What should the team add to its network automation operating process?
Explanation
Correct Answer
Make architecture reviews explicitly compare blast radius, recovery, security and long-term ownership. This prevents the recurrence because automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool. A matching immediate correction is: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. Applied here, the relevant facts are: A one-time diagnostic query is forced through the same slow infrastructure apply workflow used for persistent configuration changes. The question asks what should the team add to its network automation operating process.
Incorrect Answers
The offered statement is true for this other mechanism: model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone. It does not explain the facts described here, which follow from: automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool.
This principle describes a separate cause: safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. The reported condition is governed by: automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool. The two mechanisms should not be conflated.
The offered statement is true for this other mechanism: hTTP PUT represents replacement semantics for a targeted RESTCONF resource, whereas PATCH supports partial edits under the applicable media type. It does not explain the facts described here, which follow from: automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool.