Question 200
At fictional Thornwick Health Trust, during a remote branch provisioning pilot, the operator observes: A temporary inventory update is built as a large Terraform module even though the required API operation is an ephemeral read-only query. What should the team add to its network automation operating process?
Explanation
Correct Answer
Document selection criteria for persistence, state, API coverage, auditability and team maintenance capacity. This prevents the recurrence because infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs. A matching immediate correction is: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations.
Incorrect Answers
The offered action targets: safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. The case facts point instead to: infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs. Implement “Document selection criteria for persistence, state, API coverage, auditability and team maintenance capacity” to address that specific condition.
This alternative is a response to another technical cause: a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. The reported case instead depends on: infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs. The action that directly addresses it is “Document selection criteria for persistence, state, API coverage, auditability and team maintenance capacity”.
The proposed action belongs to the mechanism: many platform APIs paginate large result sets; the first HTTP success response may contain only a subset. Here the stated fault follows a different mechanism: infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs. The corrective choice is “Document selection criteria for persistence, state, API coverage, auditability and team maintenance capacity”.