What is the difference between Ansible, Chef, and Puppet?

Expected Interview Answer

Step-by-Step Explanation

1. Step 1

   Classify the architecture

   Note Ansible is agentless (SSH), while Chef and Puppet require a client agent installed on every managed node.

2. Step 2

   Compare push vs pull

   Ansible pushes changes on demand from a control node; Chef and Puppet nodes pull their desired state from a central server on a schedule.

3. Step 3

   Compare the language

   Ansible uses YAML playbooks, Puppet uses its own declarative DSL, and Chef uses a Ruby-based DSL organized into cookbooks and recipes.

4. Step 4

   Compare declarative vs procedural

   Puppet and Ansible lean declarative (describe the end state); Chef is more procedural (describe the ordered steps).

5. Step 5

   Weigh the trade-offs

   Ansible is fastest to learn and deploy; Puppet and Chef offer richer reporting and continuous drift enforcement for large, long-lived fleets.

Code Example

---
- name: Ensure nginx is installed and running
  hosts: webservers
  become: true
  tasks:
    - name: Install nginx
      ansible.builtin.package:
        name: nginx
        state: present
    - name: Start and enable nginx
      ansible.builtin.service:
        name: nginx
        state: started
        enabled: true

package { 'nginx':
  ensure => installed,
}

service { 'nginx':
  ensure => running,
  enable => true,
  require => Package['nginx'],
}

Follow-up Questions

• When would you choose Ansible over Puppet in production?
• What is configuration drift and how does the pull model handle it?
• How does Ansible achieve idempotency in its modules?
• What is a Chef cookbook and how does it differ from an Ansible role?
• Can Ansible run in a pull mode, and how (ansible-pull)?