A network automation engineer is selecting configuration management tools for an enterprise infrastructure overhaul. Match each configuration management mechanism or artifact on the left with its corresponding operational model, transport mechanism, and configuration language characteristics on the right.
- AnsibleAgentless architecture using a push model over SSH or NETCONF, formatted using YAML data structures.
- PuppetAgent-based pull model communicating over TCP port 8140 to compile manifests written in a proprietary declarative DSL.
- ChefAgent-based pull model communicating over TCP port 443 (HTTPS) to execute recipes written in a Ruby-based DSL.
- Ansible PlaybookA YAML-encoded file containing one or more plays that map managed host inventory groups to specific task executions.
Answer
Ansible matches with the agentless push model using SSH/NETCONF and YAML; Puppet matches with the agent-based pull model communicating over TCP 8140 using Puppet DSL manifests; Chef matches with the agent-based pull model communicating over TCP 443 using Ruby DSL recipes; Ansible Playbook matches with the YAML-encoded file mapping host inventory groups to task executions.
Each automation mechanism exhibits specific architectural and transport signatures. Ansible uses an agentless push architecture over SSH/NETCONF with YAML files (Playbooks). Puppet uses an agent-based pull model communicating over TCP port 8140 with Puppet DSL manifests. Chef uses an agent-based pull model communicating over TCP port 443 (HTTPS) with Ruby DSL recipes.
Step-by-Step Solution
Key Concept
Capabilities and Architectural Differences of Network Configuration Management Tools (Ansible, Puppet, Chef)