A network architect is designing an automated configuration management solution for a large Enterprise network containing hundreds of Cisco IOS XE routers and NX-OS switches. The architecture requirements mandate minimizing device-level software overhead by avoiding persistent agent installations, using standard SSH/NETCONF protocol transport, leveraging YAML-formatted state files, and initiating configuration updates using a push-based model from a control node. Which configuration management tool satisfies all specified requirements, and which operational characteristics define its framework?
- Ansible, because it functions agentlessly over SSH or NETCONF using a push-based model to execute YAML-defined playbooks without requiring client software on managed devices.Cevap
- BPuppet, because it natively uses an agentless push architecture over TCP port 8140 to execute YAML playbooks across managed network devices.
- CChef, because it employs an agentless push mechanism using HTTPS on TCP port 443 to send Ruby-based Cookbook recipes to managed network nodes.
- DAnsible, because it relies on an agent daemon running locally on network switches to periodically pull configuration states formatted as Ruby manifests.
Cevap
Ansible satisfies all requirements because it operates agentlessly over standard SSH or NETCONF transport, uses a push model initiated by the control node, and defines configuration tasks using YAML playbooks.
The correct answer accurately identifies Ansible's core architectural traits: it is agentless, uses SSH or NETCONF transport protocols, operates on a push model initiated by the administrator/control node, and uses readable YAML-formatted playbooks.
Adım Adım Çözüm
Anahtar Kavram
Core architectural differences between Ansible (agentless, push, SSH/NETCONF, YAML), Puppet (agent-based/pull, TCP 8140, Puppet DSL), and Chef (agent-based/pull, TCP 443, Ruby DSL).
Tahmini Süre:1m 30s