Explanation:
Agent-Based: A, C
Agentless: B
Puppet and SaltStack are generally categorized as agent-based automation tools because they normally rely on managed nodes running a local agent or minion process. Puppet uses agents on managed systems to receive catalogs from the Puppet master/server and enforce the desired state. SaltStack commonly uses a Salt master and Salt minions, where the minion runs on the managed node and receives commands or state instructions. Ansible is agentless because it does not require a resident agent on managed devices or servers. Instead, Ansible connects using standard remote access mechanisms such as SSH for Linux/Unix systems, WinRM for Windows, and network-specific connection plugins for network devices. In ENCOR automation topics, this distinction matters because agentless tools reduce endpoint installation overhead, while agent-based systems can provide persistent state enforcement and event-driven control. For Cisco network automation, Ansible is frequently tested as an agentless automation tool using playbooks and modules. References/topics: ENCOR Automation, orchestration tools, Ansible, Puppet, SaltStack, agent-based versus agentless automation.