Why the workflow matters in Terraform - Performance Analysis

Time Complexity: Why the workflow matters

O(n)

Understanding Time Complexity

When using Terraform, the order of steps affects how long it takes to set up or change resources.

We want to see how the workflow impacts the number of actions Terraform performs.

Scenario Under Consideration

Analyze the time complexity of this Terraform workflow.

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

output "instance_ids" {
  value = aws_instance.example[*].id
}
    

This creates multiple instances based on a count variable and outputs their IDs.

Identify Repeating Operations

Look at what repeats when we increase the number of instances.

• Primary operation: Creating each AWS instance resource.
• How many times: Once per instance, equal to var.instance_count.

How Execution Grows With Input

As you ask for more instances, Terraform creates more resources one by one.

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

Pattern observation: The number of operations grows directly with the number of instances.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete grows in a straight line as you add more instances.

Common Mistake

[X] Wrong: "Adding more instances won't change the time much because Terraform handles all at once."

[OK] Correct: Each instance requires a separate API call and setup, so more instances mean more work and longer time.

Interview Connect

Understanding how workflows affect time helps you plan and explain infrastructure changes clearly and confidently.

Self-Check

"What if we used modules to create instances instead of count? How would the time complexity change?"

Practice

1. Why is it important to run terraform plan before terraform apply?

easy

A. It shows the changes Terraform will make before applying them

B. It automatically applies changes without confirmation

C. It deletes all existing resources immediately

D. It skips validation of the configuration files

Solution

1. Step 1: Understand the purpose of terraform plan

   This command previews the changes Terraform will make to your infrastructure without applying them.

2. Step 2: Compare with terraform apply

   terraform apply actually makes the changes, so planning first helps avoid mistakes.

3. Final Answer:

   It shows the changes Terraform will make before applying them -> Option A

4. Quick Check:

   Plan previews changes = D [OK]

Hint: Plan first to preview changes, avoid surprises [OK]

Common Mistakes:

• Skipping plan and applying directly
• Thinking plan applies changes
• Confusing plan with destroy

2. Which command correctly initializes a Terraform working directory before planning or applying?

easy

A. terraform init

B. terraform start

C. terraform deploy

D. terraform configure

Solution

1. Step 1: Identify the initialization command

   terraform init sets up the working directory by downloading providers and preparing backend.

2. Step 2: Check other options

   Commands like terraform start, deploy, or configure do not exist in Terraform.

3. Final Answer:

   terraform init -> Option A

4. Quick Check:

   Initialize with init = B [OK]

Hint: Init first to prepare your workspace [OK]

Common Mistakes:

• Using non-existent commands
• Trying to apply before init
• Confusing init with plan

3. Given this Terraform workflow:

terraform init
tf plan
tf apply

What will happen if you run terraform apply without running terraform plan first?

medium

A. Terraform will apply changes immediately without preview

B. Terraform will show an error and stop

C. Terraform will automatically run plan before apply

D. Terraform will delete all resources

Solution

1. Step 1: Understand terraform apply behavior

   Terraform always performs an internal plan, shows the execution plan (preview of changes), and prompts for confirmation before applying.

2. Step 2: Check if plan is mandatory

   Running terraform plan first is recommended for detailed review and saving plans, but terraform apply automatically runs the plan step.

3. Final Answer:

   Terraform will automatically run plan before apply -> Option C

4. Quick Check:

   Apply auto-runs plan [OK]

Hint: Apply always plans first internally [OK]

Common Mistakes:

• Assuming apply always errors without plan
• Thinking apply auto-runs plan silently
• Believing apply deletes resources by default

4. You ran terraform apply but noticed unexpected resource deletions. What is the most likely cause related to workflow?

medium

A. Running terraform init twice

B. Skipping terraform plan and not reviewing changes

C. Using an outdated Terraform version

D. Not setting environment variables

Solution

1. Step 1: Identify workflow mistake

   Skipping terraform plan means you miss previewing changes, leading to surprises like deletions.

2. Step 2: Evaluate other options

   Running init twice, outdated version, or missing env vars usually cause errors, not unexpected deletions.

3. Final Answer:

   Skipping terraform plan and not reviewing changes -> Option B

4. Quick Check:

   Skip plan = risk of unwanted deletions [OK]

Hint: Always plan and review before applying [OK]

Common Mistakes:

• Ignoring plan output
• Blaming init for deletions
• Assuming version causes deletions

5. You want to safely update your cloud infrastructure with Terraform. Which workflow sequence best prevents downtime and mistakes?

hard

A. terraform plan -> terraform apply -> terraform init

B. terraform apply -> terraform plan -> terraform init

C. terraform apply -> terraform init -> terraform plan

D. terraform init -> terraform plan -> review plan -> terraform apply

Solution

1. Step 1: Understand the correct workflow order

   First, terraform init prepares the workspace, then terraform plan previews changes, followed by reviewing the plan carefully.

2. Step 2: Apply changes only after review

   Applying changes after review ensures safety and avoids downtime or mistakes.

3. Final Answer:

   terraform init -> terraform plan -> review plan -> terraform apply -> Option D

4. Quick Check:

   Init, plan, review, apply = C [OK]

Hint: Init, plan, review, then apply for safe updates [OK]

Common Mistakes:

• Applying before planning
• Skipping plan review
• Running commands in wrong order