350-401 · Question #1208
What do Chef and Ansible have in common?
The correct answer is B. They rely on a procedural approach.. While Chef and Ansible differ in their primary configuration paradigms, both tools, at their core, involve a sequence of operations to manage system configurations.
Question
What do Chef and Ansible have in common?
Options
- AThey use YAML as their primary configuration syntax.
- BThey rely on a procedural approach.
- CThey rely on a declarative approach
- DThey are clientless architectures.
How the community answered
(29 responses)- A3% (1)
- B93% (27)
- C3% (1)
Why each option
While Chef and Ansible differ in their primary configuration paradigms, both tools, at their core, involve a sequence of operations to manage system configurations.
Chef uses a Ruby-based DSL for its recipes, not YAML, whereas Ansible primarily uses YAML for its playbooks, making this not a commonality.
While Chef explicitly defines configuration steps using a procedural Ruby DSL, Ansible, despite its declarative playbook syntax, also relies on a sequential execution of tasks (modules) to achieve the desired state on target systems, thus involving a procedural execution flow.
Chef uses a procedural (or imperative) approach where you define *how* to achieve a state, which contrasts with Ansible's declarative approach.
Chef is an agent-based architecture, requiring a chef-client on managed nodes, which means it is not a clientless architecture.
Concept tested: Configuration management tool paradigms
Topics
Community Discussion
No community discussion yet for this question.