Ops wants OS packages, services, and config files on city VMs installed identically every time. Which practice fits best?
Select an answer to reveal the explanation.
Short Explanation
Think of a restaurant recipe card for every server—same packages, same services, same config files, every kitchen. That is configuration as code, not hoping last night's SSH session somehow sticks.
Full Explanation
Configuration as code (CaC) encodes system and application configuration—packages, services, and files—so environments can be brought to a known state consistently. It complements IaC by focusing on what runs on the instances rather than only the cloud resources themselves. Console notes and session recordings are not durable configuration sources.