A. Both rely on a declarative approach.
Here's a breakdown of the other options:
B. Both are used for mutable infrastructure: While both Ansible and Chef can be used for mutable infrastructure, they are not exclusively tied to it. They can also be used for immutable infrastructure, depending on the specific use case.
C. Both require a client to be installed on hosts: This is not true for Ansible. Ansible uses a push-based approach, where the control node sends commands to managed nodes using SSH or other protocols. Chef, on the other hand, requires an agent to be installed on managed nodes.
D. Both rely on NETCONF: NETCONF is a configuration management protocol primarily used for network devices. Neither Ansible nor Chef relies on NETCONF for their core functionalities.
Therefore, the common trait between Ansible and Chef is their use of a declarative approach. This means that you define the desired state of your infrastructure, and the tools will automatically make the necessary changes to achieve that state.
Ansible uses a procedural programming approach to define the steps needed to reach a desired state. Ansible Playbooks define the actions to be executed line by line. It is not declarative. So B becomes the best answer.
Option B, "Both are used for mutable infrastructure," is not the best choice because Ansible and Chef can be used for both mutable and immutable infrastructure.
Answer is B
Configuration management tools such as Chef, Puppet, and Ansible typically default to a mutable infrastructure paradigm.
Chef and Ansible encourage a procedural style where you write code that specifies, step-by-step, how to to achieve some desired end state.
https://blog.gruntwork.io/why-we-use-terraform-and-not-chef-puppet-ansible-saltstack-or-cloudformation-7989dad2865c
Answer is B:
Chef and Ansible(mostly hybrid) are based on a procedural or imperative style where you write code that specifies a complete step-by-step process on how to achieve the desired end state
The trait mentioned in option B, "Both are used for mutable infrastructure," does not apply to both Ansible and Chef. While it is true that both tools are used for configuration management and automation, the statement about mutable infrastructure does not accurately represent a common trait between Ansible and Chef. Therefore, the correct common trait is that both rely on a declarative approach (option A). If you have any more questions or need further explanations, feel free to ask!
Let me start by saying this question is weird. I think you are wrong because A says that they RELY on declarative. Not sure about chef, but ansible doesn't rely on it, it can be both procedural and declarative.
B says they are used in mutable but it doesn't say it is ONLY used in mutable infrastructure. So B is the more correct answer.
given answer seems to be correct
https://blog.gruntwork.io/why-we-use-terraform-and-not-chef-puppet-ansible-saltstack-or-cloudformation-7989dad2865c#:~:text=Configuration%20management%20tools%20such%20as%20Chef%2C%20Puppet%2C%20and%20Ansible%20typically%20default%20to%20a%20mutable%20infrastructure%20paradigm.
- revisited -
Chef uses procedural with cookbook - B seems better.
-Sorry
upvoted 1 times
...
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
cjoyce1980
2 months, 3 weeks agoBeehurls
2 months, 1 week ago77a59d0
5 months, 3 weeks agoShri_Fcb10
7 months, 2 weeks agoShri_Fcb10
3 months, 2 weeks ago[Removed]
7 months, 3 weeks agoc05e44e
8 months agomasrur
8 months, 1 week agoAdalberto
8 months, 1 week agoReavr
5 months agostefanxradu
8 months, 2 weeks agoAdalberto
8 months, 2 weeks agoMarcinko
8 months, 2 weeks agoRickAO76
8 months, 3 weeks agoRickAO76
8 months, 3 weeks agobabanaber
9 months agoleehyoeun
9 months agoshefo1
9 months agoMike_93
6 months agoRickAO76
9 months agoRickAO76
8 months, 3 weeks ago