A client is using IBM Cloud Schematics to build Infrastructure as Code using a declarative approach.
When using this approach, what does the declarative approach define?
- Future state
- End state or desired state
- Declarative state
- Start state
Answer(s): B
Explanation:
In Infrastructure as Code (IaC) using IBM Cloud Schematics, a declarative approach defines the "end state" or "desired state" of the infrastructure.
Declarative Approach: In the declarative model, you specify the final desired state of the infrastructure you want, and the IaC tool (IBM Cloud Schematics in this case) takes the responsibility of determining the sequence of steps necessary to achieve that state. This is opposed to an imperative approach, where you explicitly define each step required to reach the desired outcome.
IBM Cloud Schematics: IBM Cloud Schematics is a tool that allows users to define their infrastructure and services as code using Terraform. In a declarative approach, the user creates Terraform configuration files that describe the desired state of all resources, like VMs, networks, databases, etc. Schematics then reconciles the current state with the desired state by applying the appropriate changes.
Reference from IBM Cloud Professional Architect Materials:
According to IBM documentation on IBM Cloud Schematics, it focuses on defining the desired state (end state) of the resources. This is a fundamental concept of Infrastructure as Code (IaC) and the declarative approach in cloud computing.
The other options do not accurately describe the declarative approach:
A . Future state is too vague and not a recognized term in the context of IaC.
C . Declarative state is not a defined term in the IaC context.
D . Start state refers to the initial configuration, not the desired outcome.
Reveal Solution
Next Question