Implementing and Operating Cisco Enterprise Network Core Technologies (ENCOR) v1.2AutomationMedium
A network automation engineer is designing a highly available and scalable solution for managing network devices across multiple vendors. The solution requires an orchestration tool that can interact with devices using various protocols (SSH, NETCONF, RESTCONF), maintain a desired state, and support custom modules for new device types. Which orchestration tool is best suited for these requirements?
- ASaltStack
- BPuppet
- CChef
- DAnsible
Show answer & explanationAnswer & explanation
Correct answer: D. Ansible
Ansible is an agentless automation engine that uses SSH by default but supports various plugins for NETCONF, RESTCONF, and other protocols. It excels at maintaining a desired state and is highly extensible through custom modules, making it ideal for multi-vendor network automation.
Why the other options are wrong
- A. SaltStack is an agent-based (or agentless via SSH) configuration management tool with good scalability, but Ansible is often preferred for its simplicity and broad network automation ecosystem.
- B. Puppet is an agent-based configuration management tool, primarily focused on server configuration and less flexible for multi-vendor network protocols out-of-the-box.
- C. Chef is an agent-based configuration management tool, similar to Puppet, and not as natively versatile for diverse network protocols as Ansible.
Ansible for Network Automation
An agentless automation engine that uses SSH by default, supports various network protocols via modules, and is highly extensible for multi-vendor network device management and desired state configuration.
- Agentless (uses SSH by default).
- Supports multiple network protocols (NETCONF, RESTCONF, CLI).
- Idempotent: defines desired state.
- Highly extensible with custom modules and roles.
- YAML-based playbooks for readability.
Memory trick: Ansible is the versatile conductor, managing all instruments without needing them to install software.