350-401 question 101: Drag and drop the characteristics on the left to the orchestration-…

Q90Automation and Artificial Intelligence

Drag and drop the characteristics on the left to the orchestration-tool classifications on the right. <DragDrop items={["mutable infrastructure","immutable infrastructure","designed to provision the servers","designed to install and manage software on existing servers"]} slots={[{"answer":"mutable infrastructure","id":"configuration_management_1","group":"Configuration Management"},{"answer":"designed to install and manage software on existing servers","id":"configuration_management_2","group":"Configuration Management"},{"answer":"immutable infrastructure","id":"orchestration_1","group":"Orchestration"},{"answer":"designed to provision the servers","id":"orchestration_2","group":"Orchestration"}]} explanation={"Configuration management changes and maintains software configuration on existing servers, making it associated with mutable infrastructure. Orchestration provisions and coordinates infrastructure resources, fitting immutable infrastructure and server provisioning.\n\n**Learn more:** [Red Hat: Configuration Management](https://www.redhat.com/en/technologies/management/ansible/configuration-management) · [Red Hat: Orchestration](https://www.redhat.com/en/technologies/management/ansible/orchestration)"} reuse={false} />

← → navigate · a answer

Discussion · 12

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 mention: 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 - designed to install and manage software on existing servers My 0,02 cents

Mutable infrastructure refers to infrastructure that can be changed after it is provisioned. In mutable infrastructure, configuration management tools are commonly used 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

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

should be the other way round

I agree with you here.

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

That's correct.

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

thx for the correction

In the end, I don't know why configuration management should be linked to immutable infrastructure

Mutable infrastructure is often tied to Configuration Management tools, since these are meant to manage and apply changes to existing systems, updating their state over time. Immutable infrastructure usually fits with Orchestration tools, which are used to provision servers and often replace entire server instances instead of updating them in place. The characteristic "designed to provision the servers" points to a focus on creating and managing the lifecycle of servers and therefore also lines up with Orchestration tools. The characteristic "designed to install and manage software on existing servers" points to a Configuration Management function, since these tools are used to maintain and manage software states on existing infrastructure.

Agree: Configuration Management (CM) Definition: Configuration Management tools are used to automate the setup, configuration, and maintenance of systems (usually servers). Popular tools include Ansible, Puppet, Chef, and SaltStack. Purpose: Install and configure software Manage dependencies and services Ensure systems stay in a defined state over time (idempotence) Traditional Use: Mostly used in mutable infrastructure, where servers are modified after creation.