Auto-approve flag and its danger in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to run Terraform apply without manual approval.

Terraform

terraform apply [1]

Drag options to blanks, or click blank then click option'

A-force

B-auto-approve

C-no-confirm

D-skip-approval

Attempts:

3 left

💡 Hint

Common Mistakes

Using flags that do not exist in Terraform like -force or -no-confirm.

Forgetting to add any flag and expecting no prompt.

The -auto-approve flag runs Terraform apply without asking for confirmation.

2fill in blank

medium

Complete the command to safely plan changes before applying.

Terraform

terraform [1]

Drag options to blanks, or click blank then click option'

Aplan

Bdestroy

Capply

Dinit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'apply' directly without planning.

Confusing 'destroy' with planning.

terraform plan shows what changes will happen without applying them.

3fill in blank

hard

Fix the error in the command that tries to auto-approve but uses wrong flag.

Terraform

terraform apply [1]

Drag options to blanks, or click blank then click option'

A-auto-approve

B-force

C-yes

D-skip

Attempts:

3 left

💡 Hint

Common Mistakes

Using '-yes' which is not a valid Terraform flag.

Using '-force' which does not exist.

The correct flag to auto-approve is -auto-approve. Others cause errors.

4fill in blank

hard

Fill both blanks to explain the danger of using auto-approve in production.

Terraform

Using [1] can cause [2] changes without review.

Drag options to blanks, or click blank then click option'

A-auto-approve

Bmanual

Cunexpected

Dsafe

Attempts:

3 left

💡 Hint

Common Mistakes

Saying 'manual' instead of the flag name.

Saying 'safe' which is opposite of the danger.

Using -auto-approve can cause unexpected changes without review, which is risky.

5fill in blank

hard

Fill all three blanks to complete the best practice for Terraform apply.

Terraform

Always run [1] first, then [2] without [3] in production.

Drag options to blanks, or click blank then click option'

Aterraform plan

Bterraform apply

C-auto-approve

Dterraform init

Attempts:

3 left

💡 Hint

Common Mistakes

Using '-auto-approve' in production.

Skipping the plan step.

Best practice is to run terraform plan first, then terraform apply without -auto-approve in production to avoid mistakes.

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