Imagine you manage 500 network devices and you want to automate their configuration.
Before you pick a tool, one question matters:
Do you need to install software on every device, or not?Agent-based tools require software on each device. Agentless tools do not.
The blueprint compares four tools on this axis: Chef, Puppet, Ansible, and SaltStack.Agentless Architecture
An agentless tool manages devices without installing any dedicated software on them.
The control node connects to each device using a standard protocol like SSH and pushes commands directly.
Figure 1 – Agentless architecture
This approach has three clear benefits:
Nothing to install, so deployment is fast
Works with devices that cannot run third-party software, which covers most network equipment
Lower resource footprint on the managed device
Agentless is the natural choice for network automation.
A router or switch rarely accepts custom software installed by a third party, but almost every network device supports SSH.Answer the question below
Which standard protocol is typically used by agentless tools to reach managed devices?
Agent-Based Architecture
An agent-based tool requires a small software component, called the agent, installed on every managed device.
The agent runs in the background and communicates with a central server, usually called the master.
Figure 2 – Agent-based architecture
Because the agent is always there, it can enforce the desired state continuously.
If someone makes a manual change on the device, the agent notices the difference and reverts it to the expected configuration.But the agent comes with a cost.
You must install and maintain it on every device, which is rarely practical on network equipment.
This is why agent-based tools are most common on servers and virtual machines, not on routers and switches.Answer the question below
Which model requires software to be installed on each managed device?
Answer the question below
You manage 200 Cisco IOS-XE routers and want to automate their configuration. Which architecture fits your network?
When a change must be applied, who picks up the phone first: the controller or the device?
This is a different question from agent vs agentless, but the two axes usually come as a pair.
Agentless tools use push, and agent-based tools use pull.Push Model
In a push model, the control node initiates the connection and sends the configuration to the device.
The device waits and only acts when a change arrives from the controller.
Figure 3 – Push model
This model is simple and predictable.
You run a command on the control node, and the change is applied immediately on the target devices.Push is the natural choice when the device has no agent to initiate a connection itself.
The device only needs an open SSH port and valid credentials, nothing more.Answer the question below
In a push model, who initiates the connection?
Pull Model
In a pull model, the managed device initiates the connection itself.
The agent on the device periodically contacts the master, asks for the desired state, and applies any change needed.
Figure 4 – Pull model
The pull model is the natural partner of the agent-based architecture.
Since the agent is already running on the device, it can wake up every few minutes, check in with the master, and self-correct if the configuration has drifted.This approach scales to thousands of nodes without overloading the master, because each agent works independently on its own schedule.
Answer the question below
In a pull model, who initiates the connection to the master?
Answer the question below
Which model is a natural partner of the agentless architecture?
You now have the two axes you need: agent vs agentless, and push vs pull.
Let's place the four tools from the blueprint on this map.The Four-Tool Matrix
Each of the four tools picks a position on both axes.
The figure below shows where they land.
Figure 5 – The four-tool matrix
Three of the four tools sit on the agent-based side of the matrix.
Puppet and Chef are strictly agent-based and use pull. SaltStack is agent-based too, but supports both push and pull, plus an agentless mode when needed.Ansible is the only tool that sits in the agentless, push quadrant.
That is exactly what makes it the default choice for network automation.Answer the question below
Puppet and Chef are agent-based. Do they use the push or the pull model?
Comparison Table
The table below summarizes the key facts you need to remember about each tool.
Tool
Architecture
Model
Transport
Language
Ansible
Agentless
Push
SSH
YAML (Playbooks)
Puppet
Agent
Pull
TCP 8140
Puppet DSL (Manifests)
Chef
Agent
Pull
HTTPS / TCP 443
Ruby (Recipes / Cookbooks)
SaltStack
Agent
Push and Pull
ZeroMQ (TCP 4505 / 4506)
YAML (States)
Table 1 – Four-tool comparison
Why Agentless Fits Networking
Puppet and Chef are excellent tools, but they require an agent on every managed device.
Installing a Puppet or Chef agent on a network device is rarely practical, which is why these tools stay on the server side.Ansible uses SSH and does not need an agent, so it runs against any device that accepts an SSH session.
This is why Ansible became the reference for network automation, while Puppet and Chef remained strong in server and cloud infrastructure.SaltStack is the flexible one.
It is agent-based like Puppet and Chef, but it is the only tool of the four that supports both push and pull.Answer the question below
Which tool from the list is agentless and uses SSH as transport?
Answer the question below
Which tool supports both push and pull modes, with an optional agentless mode over SSH?
Answer the question below
You need to automate configuration on 50 Cisco IOS-XE switches that cannot run custom software. From the four tools in the blueprint, which one fits best?
Answer the question below
Only TCP 22 and 443 reach the master: which agent-based tool's agents can still check in?