What distinguishes Chef from Ansible in automation architecture?
Choose an answer
Tap an option to check your answer.
Correct answer: Chef is agent-based and uses cookbooks; Ansible is agentless and uses playbooks..
Why this is the answer
The correct answer highlights a key architectural difference. Chef is an agent-based configuration management tool, meaning a client (agent) must be installed on each managed node to communicate with the Chef server. It uses "cookbooks" to define desired states. In contrast, Ansible is agentless, connecting to managed nodes typically via SSH (or WinRM for Windows) and pushing configurations. Ansible uses "playbooks" written in YAML to orchestrate tasks. The first incorrect option reverses the roles of Chef and Ansible regarding agent-based/agentless and their respective configuration units (cookbooks/playbooks). The second incorrect option incorrectly describes SaltStack's architecture and misattributes the primary/minion model. The fourth option compares Chef and Puppet's language choices, which, while true, doesn't address the agent-based vs. agentless distinction between Chef and Ansible.
Pass your exam — without the endless answer hunt
Get every verified question and explanation for this exam in one place, and save hours of prep. 1,000+ certifications · 20+ languages · free to start.
Pass your exam faster → No card needed