Why the workflow matters in Terraform - Quick Recap

Recall & Review

beginner

What is the main purpose of a workflow in Terraform?

A workflow in Terraform helps organize how infrastructure changes are planned, reviewed, and applied to keep environments stable and predictable.

beginner

Why should you run 'terraform plan' before 'terraform apply'?

Running 'terraform plan' shows what changes will happen before applying them, helping avoid unexpected results and mistakes.

intermediate

How does a good workflow reduce errors in infrastructure management?

It ensures changes are reviewed and tested before applying, preventing accidental disruptions or misconfigurations.

intermediate

What role does version control play in a Terraform workflow?

Version control tracks changes to infrastructure code, enabling collaboration, history tracking, and rollback if needed.

intermediate

Explain why automation is important in a Terraform workflow.

Automation reduces manual steps, speeds up deployments, and ensures consistent application of infrastructure changes.

What does 'terraform plan' do in the workflow?

A Creates a backup of the current state

B Shows the changes Terraform will make before applying

C Deletes all existing infrastructure

D Applies changes to the infrastructure immediately

'terraform plan' previews changes without applying them, helping avoid surprises.

Why is version control important in Terraform workflows?

A It tracks and manages changes to infrastructure code

B It automatically applies infrastructure changes

C It monitors cloud provider costs

D It replaces the need for 'terraform apply'

Version control helps teams collaborate and track changes safely.

What is a key benefit of automating Terraform workflows?

A Prevents any infrastructure changes

B Removes the need for planning changes

C Allows manual editing of cloud resources

D Ensures consistent and faster infrastructure updates

Automation speeds up and standardizes deployments.

What can happen if you skip the 'terraform plan' step?

A Unexpected infrastructure changes may occur

B Terraform will not run at all

C The infrastructure will be deleted

D The state file will be corrupted

Skipping planning risks applying unintended changes.

Which step is NOT part of a good Terraform workflow?

A Reviewing planned changes before applying

B Using version control for code

C Applying changes without any review

D Testing changes in a safe environment

Applying changes without review can cause errors.

Describe why following a workflow is important when managing infrastructure with Terraform.

Think about how a step-by-step process helps keep things safe and predictable.

Explain how automation fits into a Terraform workflow and its benefits.

Consider how machines can help do repetitive tasks better than humans.

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