Auto-approve flag and its danger in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What does the auto-approve flag do in Terraform?

When you run terraform apply with the -auto-approve flag, what happens?

A Terraform applies changes immediately without asking for confirmation.

B Terraform asks for manual approval before applying changes.

C Terraform only plans changes but does not apply them.

D Terraform destroys all resources without confirmation.

💡 Hint

Think about what 'auto' and 'approve' mean together.

The -auto-approve flag skips the manual confirmation step and applies changes right away.

❓ security

intermediate

What is a key risk of using the auto-approve flag in Terraform?

Why can using -auto-approve be dangerous in production environments?

A It can apply unintended destructive changes without manual review.

B It prevents Terraform from creating any resources.

C It disables logging of Terraform actions.

D It causes Terraform to ignore the state file.

💡 Hint

Consider what happens if you skip the manual check step.

Using -auto-approve skips the confirmation, so mistakes or destructive changes can be applied without review.

❓ service_behavior

advanced

What happens if you run terraform apply -auto-approve after modifying a resource to be destroyed?

Given a Terraform configuration where a resource is changed to be removed, what is the behavior when applying with -auto-approve?

Terraform

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

# Later, this resource is removed from the config

# Running: terraform apply -auto-approve

A Terraform throws an error and stops.

B Terraform plans the destruction but waits for manual approval.

C Terraform ignores the removal and keeps the resource.

D Terraform immediately destroys the resource without asking for confirmation.

💡 Hint

Think about what skipping approval means for destructive actions.

The -auto-approve flag causes Terraform to apply all changes, including resource destruction, without confirmation.

✅ Best Practice

advanced

Which practice helps reduce risks when using the auto-approve flag?

To safely use -auto-approve in automation, what should you do?

A Always run <code>terraform apply -auto-approve</code> without planning.

B Disable state locking to speed up apply.

C Run <code>terraform plan</code> separately and review output before applying.

D Use <code>-auto-approve</code> only on destroy commands.

💡 Hint

Think about how to catch mistakes before applying changes.

Running terraform plan first lets you review changes and catch errors before applying with -auto-approve.

❓ Architecture

expert

In a CI/CD pipeline, what is a safe way to use the auto-approve flag?

You want to automate Terraform deployments in a pipeline but avoid accidental destructive changes. Which approach is safest?

A Run <code>terraform apply -auto-approve</code> directly on every commit.

B Run <code>terraform plan</code> and require manual approval before running <code>terraform apply -auto-approve</code>.

C Disable state locking to allow parallel applies with auto-approve.

D Use <code>-auto-approve</code> only on the destroy stage without planning.

💡 Hint

Consider how to balance automation and safety in pipelines.

Running plan and requiring manual approval before auto-approve apply prevents accidental destructive changes in automation.

Practice

1. What does the -auto-approve flag do when running terraform apply?

easy

A. It cancels the apply process automatically.

B. It shows a detailed plan before applying changes.

C. It skips the confirmation prompt and applies changes immediately.

D. It only validates the configuration without applying changes.

Solution

1. Step 1: Understand the purpose of the -auto-approve flag

   This flag is designed to skip the manual confirmation step during terraform apply.

2. Step 2: Identify the effect on the apply process

   By skipping confirmation, Terraform applies changes immediately without waiting for user input.

3. Final Answer:

   It skips the confirmation prompt and applies changes immediately. -> Option C

4. Quick Check:

   -auto-approve skips confirmation [OK]

Hint: Remember: auto-approve means no manual confirmation [OK]

Common Mistakes:

• Thinking it shows the plan before applying
• Assuming it cancels the apply
• Confusing it with validation only

2. Which is the correct syntax to apply Terraform changes without confirmation?

easy

A. terraform apply --force-apply

B. terraform apply --skip-confirm

C. terraform apply --no-approve

D. terraform apply -auto-approve

Solution

1. Step 1: Recall the exact flag name for skipping confirmation

   The correct flag is -auto-approve, which tells Terraform to apply changes without asking.

2. Step 2: Check the options for correct syntax

   Only terraform apply -auto-approve uses the correct flag -auto-approve with proper syntax.

3. Final Answer:

   terraform apply -auto-approve -> Option D

4. Quick Check:

   Correct flag syntax is -auto-approve [OK]

Hint: Flag always spelled exactly as -auto-approve [OK]

Common Mistakes:

• Using --skip-confirm which does not exist
• Confusing with --no-approve or --force-apply
• Adding extra dashes or misspelling the flag

3. Given this command: terraform apply -auto-approve, what is the main risk involved?

medium

A. Changes will be applied without reviewing the plan first.

B. Terraform will only validate the configuration.

C. Terraform will prompt twice for confirmation.

D. Terraform will not apply any changes.

Solution

1. Step 1: Understand what -auto-approve does

   This flag skips the manual confirmation step, so Terraform applies changes immediately.

2. Step 2: Identify the risk of skipping confirmation

   Without reviewing the plan, unintended or harmful changes might be applied automatically.

3. Final Answer:

   Changes will be applied without reviewing the plan first. -> Option A

4. Quick Check:

   Auto-approve skips review, causing risk [OK]

Hint: Auto-approve skips review, so risk is blind apply [OK]

Common Mistakes:

• Thinking no changes will apply
• Assuming double confirmation happens
• Believing it only validates without applying

4. You ran terraform apply -auto-approve and accidentally deleted a critical resource. What is the best way to prevent this in the future?

medium

A. Always run terraform apply without any flags.

B. Use -auto-approve only after reviewing the plan with terraform plan.

C. Disable Terraform state locking.

D. Run terraform apply -auto-approve twice to confirm.

Solution

1. Step 1: Identify the cause of accidental deletion

   Using -auto-approve without reviewing the plan can cause unintended changes.

2. Step 2: Find the best practice to avoid mistakes

   Always review the plan output with terraform plan before applying changes automatically.

3. Final Answer:

   Use -auto-approve only after reviewing the plan with terraform plan. -> Option B

4. Quick Check:

   Review plan before auto-approve prevents mistakes [OK]

Hint: Review plan first, then auto-approve safely [OK]

Common Mistakes:

• Thinking running apply without flags always prevents errors
• Disabling state locking which is unrelated
• Running auto-approve twice does not add confirmation

5. In an automated CI/CD pipeline, you want to safely use terraform apply -auto-approve. Which practice reduces the danger of unintended changes?

hard

A. Run terraform plan and save the plan output, then apply only if the plan matches expectations.

B. Use -auto-approve with terraform destroy to clean up resources automatically.

C. Skip the plan step and apply directly to save time.

D. Run terraform apply manually after the pipeline finishes.

Solution

1. Step 1: Understand the risk of auto-approve in automation

   Auto-approve skips manual review, so unintended changes can happen if the plan is not checked.

2. Step 2: Identify a safe automation practice

   Running terraform plan first and saving its output allows verification before applying changes automatically.

3. Step 3: Confirm the best option

   Run terraform plan and save the plan output, then apply only if the plan matches expectations. describes this safe practice, reducing risk in CI/CD pipelines.

4. Final Answer:

   Run terraform plan and save the plan output, then apply only if the plan matches expectations. -> Option A

5. Quick Check:

   Plan then apply ensures safe automation [OK]

Hint: Always plan and verify before auto-approve in pipelines [OK]

Common Mistakes:

• Skipping plan to save time
• Using auto-approve with destroy carelessly
• Running apply manually defeats automation purpose