Week 12 · Lesson 7

Configuration Management Tools

Puppet, Chef and Ansible are the three configuration-management tools the CCNA names. They all enforce a desired state across many devices, but they differ in one crucial respect: whether software has to be installed on the managed device (agent-based) or not (agentless).

CCNA 200-301 Domain 6.0 Automation and Programmability Verified 2026-10-11
Part 1

Infrastructure as code

Infrastructure as code (IaC) means defining your infrastructure — servers, switches, firewall rules, VLANs — in text files that live in version control, rather than in the heads of engineers or the running configurations of individual devices. The device configuration becomes an output, generated from source files.

Definition — infrastructure as code. Managing and provisioning infrastructure through machine-readable definition files held in version control, so deployments are repeatable, reviewable and reproducible.

Configuration-management tools are the engines that apply IaC. They all work in the declarative style from Lesson 1: you write the desired state, the tool checks the current state, and it makes the changes needed to converge — safely, repeatedly and idempotently. Where they differ is how they reach the managed device.

ModelHow it worksExamples
Agent-based (pull)Software is installed on each managed device; it periodically pulls policy from a central server.Puppet, Chef
Agentless (push)No software on the device; the tool connects in over a standard protocol such as SSH and pushes changes.Ansible
The IaC pipeline · step through it
Stage 1 of 4
1 Writesource files 2 Reviewversion control 3 Applythe tool converges 4 Verifyno drift left Git repository (source of truth) Puppet · Chef · Ansible the network devices themselves

Part 2

Agent-based vs agentless

This single architectural choice decides which tool fits which estate. An agent-based tool installs a small program on every managed device; that agent periodically contacts a central server, pulls the policy it should apply, and converges the device. An agentless tool installs nothing at all — the tool itself connects in over SSH and pushes the change when you run it.

Two models · select one to highlight it
Agent-based (pull) Master / Chef server holds the desired state Agent Agent each agent pulls on a schedule Agentless (push) Control node runs the playbook No agent No agent pushes over SSH

Exam tip. The single most tested fact here: Ansible is agentless (uses SSH, no agent); Puppet and Chef are agent-based (an agent is installed on each device). If a question mentions “no software required on the managed device” or “uses SSH”, the answer is Ansible. If it mentions an agent pulling from a master, it is Puppet or Chef.
Part 3

Puppet

Puppet is an agent-based configuration-management tool. Each managed device runs the Puppet agent, which contacts a central Puppet master on a schedule and pulls the configuration it should apply. Puppet is written in Ruby and uses its own declarative language.

# Puppet manifest (declarative desired state)
package { 'ntp':
  ensure => installed,
}
service { 'ntpd':
  ensure => running,
  enable => true,
}
Definition — Puppet manifest. A declarative file that states the desired state of resources; the Puppet agent enforces it.
Part 4

Chef

Chef is also agent-based. It uses a central Chef server and an agent called chef-client installed on each managed node. Where Puppet uses manifests, Chef organises its configuration into recipes and cookbooks, and its language (the Chef Infra DSL) is Ruby-based.

# Chef recipe (Ruby-based DSL, declarative resources)
package 'ntp' do
  action :install
end

service 'ntpd' do
  action [:enable, :start]
end
Definition — Chef recipe and cookbook. A recipe is a set of resource declarations; a cookbook is a packaged collection of recipes that configures a role or application.
Part 5

Ansible

Ansible is the odd one out: it is agentless. Nothing is installed on the managed devices. Instead a control node connects to each device over a standard protocol — usually SSH — and pushes the configuration. This is why Ansible is the most popular tool for network automation: routers and switches cannot run a Puppet or Chef agent, but they all support SSH.

Anatomy of an Ansible playbook · select a part

# Ansible playbook (YAML)
- name: Ensure NTP is configured
  hosts: switches
  tasks:
    - name: Enable NTP
      ios_config:
        lines:
          - ntp server 10.0.0.1
Part 6

Comparing the three, and choosing one

FeaturePuppetChefAnsible
ArchitectureAgent-basedAgent-basedAgentless
TransportAgent pulls from masterchef-client pulls from serverControl node pushes over SSH
LanguagePuppet DSL (.pp)Ruby-based DSLYAML (playbooks)
Building blocksManifests/resourcesRecipes/cookbooksPlaybooks/tasks/modules
ModelDeclarativeDeclarativeDeclarative (task order possible)
Network fitLimited (needs agent or proxy)Limited (needs agent or proxy)Strong (SSH is universal)
Note. All three are declarative and all are idempotent — that is what makes them configuration-management tools rather than mere scripts. The memorable difference is purely the agent question, plus the vocabulary: Puppet has manifests, Chef has recipes/cookbooks, and Ansible has playbooks.
Vocabulary check · which tool owns this building block?

For a general-purpose server estate any of the three works well, and the choice often comes down to team skills and existing investment. For a network estate the agent requirement usually decides it: because traditional network devices cannot host agents, the agentless model of Ansible tends to fit naturally. That is why Ansible appears most often in network-automation discussions, and why its YAML playbooks connect straight back to the data-format lesson you just finished.

Whichever tool is used, the goal is the same one established in Lesson 1: express the desired state as code, apply it idempotently, and let the tool keep the network converged — detecting and correcting the configuration drift that manual administration always produces.

Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Key termMeaning
Infrastructure as codeDefining infrastructure in version-controlled text files rather than manual configuration.
Agent-basedModel where software is installed on each managed device (Puppet, Chef).
AgentlessModel where no software is installed; the tool connects in over SSH (Ansible).
Puppet manifestA declarative .pp file of resource declarations.
Chef recipeA set of resource declarations; bundled into cookbooks.
CookbookA packaged collection of Chef recipes for a role or application.
Ansible playbookA YAML file of plays and tasks applied to hosts from an inventory.
Idempotent convergenceMaking only the changes needed so the device reaches the desired state.
Sources & references
  1. Cisco. CCNA (200-301) Exam Topics, Domain 6.0 Automation and Programmability. cisco.com.
  2. Red Hat. What is Ansible? redhat.com.
  3. Puppet. Puppet Documentation. puppet.com/docs.
  4. Chef (Progress). Chef Infra Documentation. docs.chef.io.
  5. Cisco. Ansible Network Automation. developer.cisco.com.
Sources

Sources & references

  1. Cisco. CCNA (200-301) Exam Topics, Domain 6.0 Automation and Programmability. cisco.com.
  2. Red Hat. What is Ansible? redhat.com.
  3. Puppet. Puppet Documentation. puppet.com/docs.
  4. Chef (Progress). Chef Infra Documentation. docs.chef.io.
  5. Cisco. Ansible Network Automation. developer.cisco.com.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.