Terraform CLI overview - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize a Terraform working directory.

Terraform

terraform [1]

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

Aapply

Bdestroy

Cplan

Dinit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'apply' instead of 'init' to initialize the directory.

Confusing 'plan' with initialization.

The terraform init command initializes the working directory by downloading necessary plugins and preparing the environment.

2fill in blank

medium

Complete the code to see the changes Terraform will make to your infrastructure.

Terraform

terraform [1]

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

Ainit

Bvalidate

Cplan

Dapply

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'apply' when you only want to preview changes.

Confusing 'validate' with planning.

The terraform plan command shows the execution plan, detailing what changes will be made without applying them.

3fill in blank

hard

Fix the error in the command to apply changes to infrastructure.

Terraform

terraform [1] -auto-approve

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

Aapply

Bplan

Cinit

Ddestroy

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'plan' instead of 'apply' to make changes.

Using 'init' which only initializes the directory.

The terraform apply command applies the changes required to reach the desired state of the configuration. The -auto-approve flag skips manual approval.

4fill in blank

hard

Fill both blanks to destroy all managed infrastructure without confirmation.

Terraform

terraform [1] -[2]

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

Adestroy

Bauto-approve

Capply

Dplan

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'apply' instead of 'destroy' to delete resources.

Forgetting the '-auto-approve' flag and getting stuck at confirmation.

The terraform destroy command removes all resources managed by Terraform. The -auto-approve flag skips the confirmation prompt.

5fill in blank

hard

Fill both blanks to validate the Terraform configuration and show detailed output.

Terraform

terraform [1] -[2]

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

Avalidate

Bjson

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'plan' or 'apply' instead of 'validate' for syntax checking.

Misusing the output flag.

The terraform validate command checks the syntax and internal consistency of the configuration files. The -json flag outputs the validation result in JSON format for detailed analysis.

Practice

1. What is the primary purpose of the terraform init command?

easy

A. To show the planned changes without applying them

B. To apply changes to cloud infrastructure

C. To destroy all managed resources

D. To initialize a working directory and download required provider plugins

Solution

1. Step 1: Understand the role of terraform init

   This command sets up the working directory by downloading necessary provider plugins and preparing the environment.

2. Step 2: Differentiate from other commands

   Commands like apply and destroy perform changes, while init only prepares the setup.

3. Final Answer:

   To initialize a working directory and download required provider plugins -> Option D

4. Quick Check:

   terraform init prepares environment [OK]

Hint: Init sets up your folder and downloads plugins [OK]

Common Mistakes:

• Confusing init with apply
• Thinking init changes infrastructure
• Mixing init with destroy

2. Which of the following is the correct syntax to preview changes without applying them?

easy

A. terraform plan

B. terraform apply --preview

C. terraform preview

D. terraform show

Solution

1. Step 1: Identify the command to preview changes

   terraform plan shows what changes will happen without applying them.

2. Step 2: Check other options for correctness

   apply --preview and preview are not valid commands; show displays current state, not planned changes.

3. Final Answer:

   terraform plan -> Option A

4. Quick Check:

   Preview changes = terraform plan [OK]

Hint: Plan shows changes without applying [OK]

Common Mistakes:

• Using apply --preview which is invalid
• Confusing show with plan
• Assuming preview is a Terraform command

3. Given the following sequence of commands:

terraform init
tf plan
terraform apply

What will happen when you run these commands?

medium

A. Only initialize the directory and apply changes, skipping the plan

B. Initialize the directory, show planned changes, then apply those changes

C. Initialize the directory, apply changes immediately, then show the plan

D. Show planned changes without initializing or applying

Solution

1. Step 1: Understand each command's role

   terraform init sets up the environment, terraform plan shows what will change, and terraform apply makes those changes.

2. Step 2: Analyze the sequence

   The commands run in order: initialize, plan, then apply, which is the recommended workflow.

3. Final Answer:

   Initialize the directory, show planned changes, then apply those changes -> Option B

4. Quick Check:

   Init -> Plan -> Apply = safe workflow [OK]

Hint: Init, then plan, then apply changes [OK]

Common Mistakes:

• Running apply before plan
• Skipping init before plan
• Confusing plan and apply order

4. You run terraform apply but get an error saying the backend is not configured. What is the most likely cause?

medium

A. You need to run terraform destroy first

B. You used the wrong syntax for apply

C. You forgot to run terraform init first

D. Your cloud provider credentials are missing

Solution

1. Step 1: Understand backend configuration role

   The backend stores state remotely and must be set up before applying changes.

2. Step 2: Identify how backend is configured

   terraform init configures the backend; skipping it causes errors.

3. Final Answer:

   You forgot to run terraform init first -> Option C

4. Quick Check:

   Init configures backend before apply [OK]

Hint: Always run init before apply to configure backend [OK]

Common Mistakes:

• Skipping init and running apply directly
• Assuming credentials cause backend error
• Thinking destroy fixes backend issues

5. You want to safely remove all cloud resources managed by Terraform. Which command sequence ensures this with minimal risk?

hard

A. terraform destroy after terraform plan to review changes

B. terraform apply followed by terraform destroy

C. terraform init then terraform apply

D. terraform plan then terraform init

Solution

1. Step 1: Understand the purpose of terraform destroy

   This command deletes all resources managed by Terraform.

2. Step 2: Use terraform plan before destroy

   Planning shows what will be destroyed, helping avoid mistakes.

3. Step 3: Confirm the sequence

   Running terraform plan first, then terraform destroy is the safest approach.

4. Final Answer:

   terraform destroy after terraform plan to review changes -> Option A

5. Quick Check:

   Plan before destroy to avoid surprises [OK]

Hint: Plan first, then destroy to confirm changes [OK]

Common Mistakes:

• Destroying without planning first
• Applying changes before destroying
• Running init after plan