Why IaC over manual provisioning in Terraform - Quick Recap

Recall & Review

beginner

What does IaC stand for and what is its main purpose?

IaC stands for Infrastructure as Code. Its main purpose is to manage and provision computing infrastructure through machine-readable configuration files instead of manual setup.

beginner

Name one key advantage of IaC compared to manual provisioning.

IaC allows for automation, which reduces human errors and speeds up infrastructure deployment.

intermediate

How does IaC improve consistency in infrastructure setup?

IaC uses code templates to create identical environments every time, avoiding differences caused by manual steps.

intermediate

Why is version control important in IaC?

Version control tracks changes in infrastructure code, enabling rollback to previous states and collaboration among teams.

beginner

What is a real-life example of manual provisioning risk that IaC helps avoid?

Manually forgetting to open a firewall port can cause downtime. IaC scripts include all settings, preventing such oversights.

What is a main benefit of using IaC over manual provisioning?

A More manual steps to control resources

B Requires no knowledge of cloud services

C Faster and repeatable infrastructure setup

D No need for version control

IaC automates and speeds up infrastructure setup, making it repeatable and less error-prone.

Which tool is commonly used for IaC with Terraform?

A Text editor

B Terraform CLI

C Manual console clicks

D Email

Terraform CLI is the command-line tool used to apply IaC configurations written in Terraform.

How does IaC help teams collaborate better?

A By using different tools for each member

B By working on separate manual setups

C By avoiding documentation

D By sharing code in version control systems

IaC code stored in version control allows teams to share, review, and update infrastructure configurations together.

What problem does IaC reduce compared to manual provisioning?

A Human errors and inconsistencies

B Automation speed

C Infrastructure cost

D Cloud provider availability

IaC reduces human errors and inconsistencies by automating infrastructure setup.

Which of these is NOT a benefit of IaC?

A Manual click-based setup

B Faster recovery from failures

C Repeatable deployments

D Infrastructure versioning

Manual click-based setup is the opposite of IaC benefits, which focus on automation and code-driven provisioning.

Explain why Infrastructure as Code (IaC) is preferred over manual provisioning.

Think about how code helps manage infrastructure like software.

Describe a scenario where manual provisioning could cause problems that IaC would prevent.

Imagine setting up servers by hand and forgetting a step.

Practice

1. Why is Infrastructure as Code (IaC) preferred over manual cloud provisioning?

easy

A. Manual provisioning tracks changes automatically.

B. Manual provisioning is faster for large-scale deployments.

C. IaC requires no knowledge of cloud services.

D. IaC automates setup, saving time and reducing human errors.

Solution

1. Step 1: Understand automation benefits of IaC

   IaC automates cloud setup, which reduces manual work and human mistakes.

2. Step 2: Compare manual provisioning drawbacks

   Manual provisioning is slower and prone to errors, especially at scale.

3. Final Answer:

   IaC automates setup, saving time and reducing human errors. -> Option D

4. Quick Check:

   Automation = IaC advantage [OK]

Hint: IaC automates and reduces errors, unlike manual steps [OK]

Common Mistakes:

• Thinking manual is faster for big setups
• Believing IaC needs no cloud knowledge
• Assuming manual tracks changes automatically

2. Which Terraform command applies your infrastructure code to create resources?

easy

A. terraform apply

B. terraform plan

C. terraform init

D. terraform destroy

Solution

1. Step 1: Identify command to create resources

   terraform apply runs the code and creates or updates infrastructure.

2. Step 2: Differentiate from other commands

   terraform plan shows changes, init sets up, destroy deletes resources.

3. Final Answer:

   terraform apply -> Option A

4. Quick Check:

   Apply = create/update resources [OK]

Hint: Apply means execute changes to infrastructure [OK]

Common Mistakes:

• Confusing plan with apply
• Using init to create resources
• Destroying instead of applying

3. Given this Terraform snippet, what is the main benefit of using it instead of manual setup?

resource "aws_instance" "web" {
  ami           = "ami-123456"
  instance_type = "t2.micro"
}

medium

A. It automatically tracks and applies changes to the instance.

B. It requires manual steps to launch the instance.

C. It disables version control for infrastructure.

D. It prevents reuse of the configuration.

Solution

1. Step 1: Understand Terraform resource block

   This block defines an AWS instance that Terraform can create and manage automatically.

2. Step 2: Compare with manual setup

   Manual setup requires clicking or scripting outside Terraform, no automatic tracking or updates.

3. Final Answer:

   It automatically tracks and applies changes to the instance. -> Option A

4. Quick Check:

   Automatic tracking = IaC benefit [OK]

Hint: Terraform tracks changes; manual does not [OK]

Common Mistakes:

• Thinking manual steps are needed with Terraform
• Believing Terraform disables version control
• Assuming config cannot be reused

4. You wrote Terraform code but it fails to update your cloud resources. What is a common reason for this?

medium

A. Manual provisioning is required after every change.

B. You forgot to run terraform apply after changes.

C. Terraform does not support updating resources.

D. Terraform automatically updates without commands.

Solution

1. Step 1: Identify Terraform workflow

   After editing code, you must run terraform apply to update resources.

2. Step 2: Eliminate incorrect options

   Terraform supports updates but needs apply; manual provisioning is not needed after changes; updates are not automatic without commands.

3. Final Answer:

   You forgot to run terraform apply after changes. -> Option B

4. Quick Check:

   Apply runs updates [OK]

Hint: Always run terraform apply to update resources [OK]

Common Mistakes:

• Assuming Terraform updates automatically
• Thinking manual steps are needed after code changes
• Believing Terraform cannot update resources

5. How does using Terraform as IaC help teams fix problems faster compared to manual provisioning?

hard

A. Manual provisioning is faster to fix because it uses GUIs.

B. Manual provisioning automatically logs all changes for easy fixes.

C. Terraform code is reusable and tracks changes, making troubleshooting easier.

D. Terraform requires no collaboration, so fewer errors occur.

Solution

1. Step 1: Understand Terraform's tracking and reusability

   Terraform stores infrastructure as code, enabling version control and easy sharing.

2. Step 2: Compare with manual provisioning challenges

   Manual provisioning lacks automatic tracking and is harder to reproduce or fix consistently.

3. Final Answer:

   Terraform code is reusable and tracks changes, making troubleshooting easier. -> Option C

4. Quick Check:

   Tracking + reuse = faster fixes [OK]

Hint: Code tracks changes and is reusable for quick fixes [OK]

Common Mistakes:

• Believing manual provisioning logs changes automatically
• Thinking Terraform needs no teamwork
• Assuming GUIs are always faster to fix problems