Question 660
While investigating a network policy migration for fictional Cedarbridge Care Systems, the team reports: A playbook restarts network services after every configuration check even when the device configuration is unchanged. Which targeted correction best addresses the network automation failure?
Explanation
Correct Answer
Notify a handler only when the associated configuration task reports a real change, and apply the restart once if necessary. This addresses the problem because ansible handlers are triggered by changed tasks and coalesce notifications, separating configuration checks from disruptive service actions. Confirm success using: Unchanged reruns cause no service restart, while an approved changed configuration invokes its handler exactly once. Applied here, the relevant facts are: A playbook restarts network services after every configuration check even when the device configuration is unchanged. The question asks which targeted correction best addresses the network automation failure.
Incorrect Answers
This alternative is a response to another technical cause: hTTP PUT represents replacement semantics for a targeted RESTCONF resource, whereas PATCH supports partial edits under the applicable media type. The reported case instead depends on: ansible handlers are triggered by changed tasks and coalesce notifications, separating configuration checks from disruptive service actions. The action that directly addresses it is “Notify a handler only when the associated configuration task reports a real change, and apply the restart once if necessary”.
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: ansible handlers are triggered by changed tasks and coalesce notifications, separating configuration checks from disruptive service actions. The corrective choice is “Notify a handler only when the associated configuration task reports a real change, and apply the restart once if necessary”.
The offered action targets: hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. The case facts point instead to: ansible handlers are triggered by changed tasks and coalesce notifications, separating configuration checks from disruptive service actions. Implement “Notify a handler only when the associated configuration task reports a real change, and apply the restart once if necessary” to address that specific condition.