Why IaC over manual provisioning in Terraform - Performance Analysis

Time Complexity: Why IaC over manual provisioning

O(n)

Understanding Time Complexity

We want to understand how the time to set up cloud resources changes when using Infrastructure as Code (IaC) compared to doing it manually.

Specifically, how does the number of steps grow as we add more resources?

Scenario Under Consideration

Analyze the time complexity of provisioning multiple cloud resources using Terraform.

resource "aws_instance" "example" {
  count         = var.instance_count
  ami           = "ami-123456"
  instance_type = "t2.micro"
}

variable "instance_count" {
  type    = number
  default = 3
}

This code creates a number of virtual machines equal to instance_count automatically.

Identify Repeating Operations

Look at what happens repeatedly when this code runs.

• Primary operation: Creating each virtual machine (API call to cloud provider)
• How many times: Once per instance, so equal to instance_count

How Execution Grows With Input

As you increase the number of instances, the number of API calls grows directly with it.

Input Size (n)	Approx. API Calls/Operations
10	10
100	100
1000	1000

Pattern observation: The number of operations grows in a straight line with the number of resources.

Final Time Complexity

Time Complexity: O(n)

This means the time to provision grows directly with how many resources you create.

Common Mistake

[X] Wrong: "Using IaC means provisioning time stays the same no matter how many resources I add."

[OK] Correct: Each resource still needs to be created, so time grows with the number of resources, but IaC automates and manages this growth efficiently.

Interview Connect

Understanding how provisioning time grows helps you explain why automation with IaC is better than manual steps, showing you grasp practical cloud operations.

Self-Check

"What if we added a module that provisions multiple resources in parallel? How would the time complexity change?"

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