Configuration Management: CMDB vs. Ansible vs. Version Control
NewThe same phrase means three jobs. In IT service management, configuration management means keeping the CMDB, the record of which IT assets exist and how they depend on each other. In DevOps, it means tools such as Ansible, Puppet and Chef that set up servers automatically. In older software teams, software configuration management (SCM) means version control, builds and releases. A search for 'configuration management' brings back all three.
How to tell them apart on a resume
CMDB / ITSM
ServiceNow CMDB, configuration items (CIs), Discovery, Service Mapping, asset management, ITIL.
Infrastructure automation
Ansible playbooks, Puppet, Chef, SaltStack, automated server builds, often alongside Terraform.
Software configuration management
Git, SVN, ClearCase, branching, build and release management, SCM engineer or build engineer titles.
The question that settles it
“When you say configuration management, do you mean keeping a CMDB, automating server setup with tools like Ansible, or version control and releases?”
Each term in plain English
- CMDB
The database that lists a company's IT assets (servers, applications, network devices, cloud resources) and how they depend on each other.
Ask “How did your team keep the CMDB accurate, and how did you know how accurate it was?”
- Chef / Puppet
Configuration-management tools that keep large fleets of servers set up identically — the same software, settings and users on every machine — by describing the desired state in code.
Ask “Is that environment still running Chef or Puppet today? If you moved off it, what did you move to and why?”
- Ansible
A configuration-management tool that automates setting up and maintaining servers by describing their desired state in code (playbooks) — an agentless alternative/complement to tools like Terraform, more focused on configuring existing machines than provisioning new infrastructure.
Ask “How did your team split responsibilities between Terraform (or similar) and Ansible — what did each one actually own?”
- Git
The standard tool for tracking changes to code over time and enabling multiple people to collaborate on the same codebase without overwriting each other's work.
Ask “Tell me about a time you had to untangle a messy merge conflict or recover lost work with Git.”
Open the full tool for the other look-alike pairs, role profiles, and the JD decoder.