Configuration Management Basics

What is configuration management? Why is it important and what tools are commonly used?

Infrastructurebeginner

// interview question

What is configuration management? Why is it important and what tools are commonly used?

Sample answer

Configuration management is the practice of automating and standardizing system configurations across environments. It ensures consistency (all servers configured the same), enables version control of configs, provides audit trails, and reduces manual errors. Common tools: Ansible (agentless, YAML), Puppet (agent-based, DSL), Chef (agent-based, Ruby), and SaltStack. CM enables infrastructure as code and is essential for managing servers at scale.

Why this matters

Without configuration management, maintaining consistency across dozens or hundreds of servers becomes impossible. CM tools enforce desired state - if someone manually changes a config, the CM tool reverts it. This is crucial for security compliance and reproducible deployments. Ansible has become dominant due to its simplicity and agentless architecture.

Code examples

Simple Ansible playbook

yaml

---
- name: Configure web servers
  hosts: webservers
  become: yes
  tasks:
    - name: Install nginx
      apt:
        name: nginx
        state: present
        update_cache: yes

    - name: Start nginx service
      service:
        name: nginx
        state: started
        enabled: yes

    - name: Copy config file
      copy:
        src: nginx.conf
        dest: /etc/nginx/nginx.conf
      notify: Restart nginx

  handlers:
    - name: Restart nginx
      service:
        name: nginx
        state: restarted

Running Ansible

bash

# Check connectivity to hosts
ansible all -m ping

# Run playbook
ansible-playbook site.yml

# Run with specific inventory
ansible-playbook -i production site.yml

# Dry run (check mode)
ansible-playbook site.yml --check

# Limit to specific hosts
ansible-playbook site.yml --limit webserver1

Common mistakes to avoid

Not testing playbooks in staging before production
Hardcoding environment-specific values instead of using variables
Running as root when privilege escalation should be explicit

Likely follow-ups

What is idempotency and why is it important in configuration management?
What is the difference between push and pull-based configuration management?
When would you use configuration management vs. containers?

Answer out loud first, then check yourself against the model answer.

Practice all Junior questions More Infrastructure questions

#ansible#configuration-management#iac#automation#fundamentals

Also worth your time on this topic

Article

Your Automation Platform Is a Credential Honeypot: Ansible CVE-2026-11807

A missing authorization check in Event-Driven Ansible lets any logged-in user pull plaintext vault passwords, SSH keys, and OAuth tokens out of Ansible Automation Platform. It is a CVSS 9.6, it is patched, and it is a reminder of what your automation control plane really holds.

Exercise

Complete Web Server Automation with Ansible

Build a comprehensive Ansible playbook to automate web server deployment, configuration, and security hardening across multiple environments.

75 minutes

Interview

CI/CD Pipeline Stages

What are the typical stages of a CI/CD pipeline and why is each stage important?

junior

Configuration Management Basics

More Infrastructure interview questions

Also worth your time on this topic

Your Automation Platform Is a Credential Honeypot: Ansible CVE-2026-11807

Complete Web Server Automation with Ansible

CI/CD Pipeline Stages