Declarative vs imperative IaC in Terraform - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Declarative Infrastructure as Code

Which statement best describes the declarative approach in Infrastructure as Code (IaC)?

A You write code that specifies the desired end state of the infrastructure, and the tool figures out how to achieve it.

B You write step-by-step commands to create and configure each resource manually.

C You must manually run each command in sequence to build the infrastructure.

D You write scripts that only describe the current state without any changes.

💡 Hint

Think about whether you describe the final setup or the steps to get there.

Declarative IaC means you declare what you want the infrastructure to look like. The tool then figures out how to make it happen. This is different from imperative, where you specify exact steps.

❓ Architecture

intermediate

Identifying Imperative IaC Characteristics

Which of the following Terraform configurations shows an imperative style rather than declarative?

Note: Terraform is declarative by design, but consider which option mimics imperative behavior.

A Using variables and outputs to parameterize and share data between modules.

B Defining a resource block with desired attributes and letting Terraform manage creation.

C Using <code>provisioner "local-exec" { command = "echo Setup" }</code> to run shell commands during resource creation.

D Writing a Terraform module that describes a reusable infrastructure component.

💡 Hint

Imperative style involves explicit commands or scripts executed step-by-step.

Using local-exec provisioners runs explicit commands during deployment, which is more imperative. Terraform resource blocks are declarative.

❓ service_behavior

advanced

Terraform Plan Behavior in Declarative IaC

What does the terraform plan command do in the context of declarative Infrastructure as Code?

A It deletes all existing resources before creating new ones.

B It immediately applies changes to the cloud infrastructure without confirmation.

C It only validates the syntax of the Terraform files without checking infrastructure state.

D It shows the exact steps Terraform will take to change the infrastructure to match the declared configuration.

💡 Hint

Think about how Terraform previews changes before applying them.

terraform plan compares the current infrastructure state with the desired state declared in code and shows what changes will be made.

❓ security

advanced

Security Implications of Imperative vs Declarative IaC

Which security risk is more likely when using imperative Infrastructure as Code compared to declarative?

A Automatically enforcing consistent security policies across all resources.

B Inadvertently skipping critical configuration steps leading to insecure resources.

C Having a clear, auditable record of desired infrastructure state.

D Using version control to track infrastructure changes.

💡 Hint

Consider how manual steps can cause mistakes.

Imperative IaC requires explicit commands; missing or incorrect steps can cause security gaps. Declarative IaC reduces this risk by defining the desired state.

✅ Best Practice

expert

Choosing Between Declarative and Imperative IaC

You manage a large cloud infrastructure that changes frequently. Which approach is best to ensure reliable, repeatable deployments and why?

A Declarative IaC, because it defines the desired state and lets the tool handle changes, reducing human error.

B Imperative IaC, because writing scripts for each step gives full control over deployment order.

C Imperative IaC, because it requires less upfront planning and is faster to write for small changes.

D Declarative IaC, because it requires manual execution of each command to verify correctness.

💡 Hint

Think about scalability, repeatability, and error reduction.

Declarative IaC is best for large, changing environments because it automates state management and reduces manual errors. Imperative scripts can become complex and error-prone.