According to: https://www.ibm.com/cloud/blog/chef-ansible-puppet-terraform and https://blog.gruntwork.io/why-we-use-terraform-and-not-chef-puppet-ansible-saltstack-or-cloudformation-7989dad2865c#b264 They write about: Configuration management tools such as Chef, Puppet, and Ansible typically default to a mutable infrastructure paradigm. and Generally, Ansible, Puppet, SaltStack, and Chef are considered to be configuration management (CM) tools and were created to install and manage software on existing server instances So I would say: Configuration Management Tool - mutable infrastructure - design to install and manage softwareon existing servers My 0,02 cents

My vote. I don't have a link to prove it, but it does make a lot of sense. Configuration Management: - Mutable - Designed to install and manage software on existing servers Orchestration: - Immutable - Designed to provision the servers

Mutable infrastructure refers to infrastructure that can be modified or changed after it is provisioned. In mutable infrastructure, configuration management tools are commonly employed to automate and manage the configuration, deployment, and maintenance of the infrastructure components. These tools help ensure consistency, enforce desired configurations, and facilitate updates or changes to the infrastructure over time. For immutable infrastructure, while the focus is on building and deploying new instances rather than modifying existing ones, orchestration tools can still play a role. In this context, orchestration tools are often used to automate the creation, deployment, and scaling of immutable infrastructure instances. These tools enable the streamlined provisioning of pre-configured and consistent instances, ensuring the rapid deployment of identical infrastructure components. So, Configuration Management: - Mutable - Designed to install and manage software on existing servers Orchestration: - Immutable - Designed to provision the servers

should be other way round

given answers are incorrect Configuration Management: - mutable infrastructure - designed to install and manage software on existing servers Orchestration: - immutable infrastructure - designed to provision the servers

Configuration Management: Mutable infrastructure Designed to install and manage software on existing servers Orchestration: Immutable infrastructure Designed to provision the servers

Mutable infrastructure is often associated with Configuration Management tools, as these are designed to manage and apply changes to existing systems, updating their state over time. Immutable infrastructure typically aligns with Orchestration tools, which are used to provision servers and often to replace entire server instances rather than update them in place. The characteristic "designed to provision the servers" suggests a focus on creating and managing the lifecycle of servers and thus also aligns with Orchestration tools. The characteristic "designed to install and manage software on existing servers" indicates a function of Configuration Management tools, as they are used to maintain and manage software states on existing infrastructure.

Incorrect: Orchestration ....In this blog we’ll discuss Terraform’s paradigm of immutable deployment Configuration Management .....We will also demonstrate how Ansible – with its mutable approach to managing infrastructure and applications – masterfully manages configuration management and application software provisioning for initial and ongoing deployments. ....*Configuration management tools such as Chef, Puppet, and Ansible typically default to a mutable infrastructure paradigm. https://blogs.cisco.com/developer/choosingtools01

Correct