A logistics company keeps switch configurations as versioned templates and uses automation to apply them, instead of typing each change by hand. Which practice is that?
Select an answer to reveal the explanation.
Short Explanation
You’ve moved from typing each change by hand to keeping the recipe under version control and letting automation apply it consistently. That practice is infrastructure as code. A golden configuration typed into switches, a cable diagram, and a tabletop exercise don’t apply templates through automation.
Full Explanation
Infrastructure as code stores infrastructure definitions in versioned text and applies them through automation, so changes can be reviewed, repeated, and not retyped on each device. The logistics company keeps switch configurations as versioned templates and applies them with automation, which is infrastructure as code. A golden configuration is an approved baseline, but when engineers still type it into each switch, the code-driven apply step is absent. A cable diagram documents physical runs; it does not push configuration templates. A tabletop exercise talks through a disaster scenario; it is not a deployment tool. Exam caveat: infrastructure as code still needs change control and a rollback, because automation can apply a bad template faster than a person can. Practical check: change a template in version control, review the diff, apply it to a lab switch, and confirm the running configuration matches the template. Keep the automation account limited to the switches it is supposed to change.