A fire district’s Ansible playbook must be safe to re-run after a partial failure without creating duplicate VRFs on the same routers. Which automation design best provides that safety?
Select an answer to reveal the explanation.
Short Explanation
Idempotent automation is like setting the station thermostat to 72—pressing the button twice does not invent a second furnace. Check or declare the VRF you want, then converge. Wiping everything or inventing new names just makes the next outage harder.
Full Explanation
Idempotent network automation converges devices to a declared desired state so re-running a playbook after a partial failure does not duplicate VRFs or other objects. Declarative controller/API patterns and explicit existence checks before create support that behavior. Destructive wipe-and-recreate or randomized naming destroy predictability. Suppressing errors hides failed creates and increases drift risk.