350-401 · Question #946
What is one difference between SaltStack and Ansible?
The correct answer is D. SaltStack is agent based, whereas Ansible is agentless.. SaltStack and Ansible are both configuration management tools, but they differ fundamentally in their operational architecture regarding agent deployment.
Question
Options
- ASaltStack uses the Ansible agent on the box, whereas Ansible uses a Telnet server on the box.
- BSaltStack uses an API proxy agent to program Cisco boxes in agent mode, whereas Ansible uses
- CSaltStack uses SSH to interact with Cisco devices, whereas Ansible uses an event bus.
- DSaltStack is agent based, whereas Ansible is agentless.
How the community answered
(51 responses)- B2% (1)
- C6% (3)
- D92% (47)
Why each option
SaltStack and Ansible are both configuration management tools, but they differ fundamentally in their operational architecture regarding agent deployment.
SaltStack does not use an Ansible agent; they are distinct platforms, and Ansible uses SSH or WinRM, not a Telnet server.
This statement inaccurately describes how either SaltStack or Ansible interact with Cisco devices and misrepresents their core architectures.
SaltStack typically uses a message bus for communication between master and minion, not solely SSH; Ansible primarily uses SSH for device interaction, but it is not an event bus for its core communication with targets.
SaltStack employs an agent-based architecture, requiring a 'minion' agent to be installed on each managed node, whereas Ansible is agentless, relying on standard protocols like SSH for communication and execution on managed systems.
Concept tested: Configuration Management Agent vs. Agentless
Source: https://docs.saltproject.io/en/latest/topics/architecture/index.html
Topics
Community Discussion
No community discussion yet for this question.