A network engineering team is evaluating configuration management mechanisms (Ansible, Puppet, and Chef) for automated network device provisioning, compliance auditing, and state enforcement across an enterprise infrastructure. Which of the following statements correctly describe the underlying architectural capabilities, transport protocols, or configuration artifacts of these tools? (Select TWO.)
- Ansible utilizes an agentless architecture that primarily relies on SSH or NETCONF to push configuration playbooks formatted in YAML directly to managed network devices.Answer
- BPuppet operates exclusively as an agentless push-based framework that relies on HTTP GET requests to execute Ruby-based recipes on target routers.
- Chef typically employs an agent-based, pull architecture where target nodes run a client agent to periodically request and apply configuration state defined in Recipes and Cookbooks from a central server over HTTPS.Answer
- DAnsible requires a dedicated client daemon running natively on every managed Cisco IOS XE switch to periodically pull compiled JSON manifests over TCP port 8140.
Answer
Ansible utilizes an agentless push architecture using SSH/NETCONF and YAML playbooks, while Chef relies on an agent-based pull architecture where target nodes pull configuration recipes and cookbooks from a central server over HTTPS.
The statement describing Ansible correctly highlights its agentless nature, push-based workflow via SSH/NETCONF, and use of YAML playbooks. The statement describing Chef correctly identifies its agent-based pull model, where client software queries a central server over HTTPS to fetch Ruby-based recipes and cookbooks.
Step-by-Step Solution
Key Concept
Capabilities and Architectural Differences of Configuration Management Tools (Ansible, Puppet, Chef)
Estimated Time:2m 0s