Why Terraform apply for execution? - Purpose & Use Cases

The Big Idea

What if you could build your entire cloud setup with just one simple command?

The Scenario

Imagine you have to set up a whole network of servers, databases, and storage by clicking through dozens of web pages and filling forms one by one.

Every time you want to change something, you must repeat this slow process.

The Problem

This manual way is slow and tiring.

It's easy to make mistakes like forgetting a step or typing wrong values.

Fixing errors means going back and redoing many steps, wasting time and causing frustration.

The Solution

Using Terraform apply lets you tell the computer exactly what you want in a simple file.

Then, with one command, Terraform builds or updates everything automatically and correctly.

This saves time, avoids mistakes, and makes changes easy and safe.

Before vs After

✗ Before

Click through cloud console to create VM, then storage, then network...

✓ After

terraform apply  # Runs all setup from your config file automatically

What It Enables

You can create and change complex cloud setups quickly and reliably with a single command.

Real Life Example

A company launches a new app and needs many servers and databases.

Instead of setting each one by hand, they write a Terraform file and run terraform apply to get everything ready in minutes.

Key Takeaways

Manual cloud setup is slow and error-prone.

Terraform apply automates building and updating infrastructure.

This makes cloud work faster, safer, and repeatable.

Practice

1. What does the terraform apply command do in simple terms?

easy

A. It backs up your cloud resources to local storage.

B. It creates or changes cloud resources based on your configuration.

C. It only shows a list of resources without making changes.

D. It deletes all your cloud resources immediately.

Solution

1. Step 1: Understand the purpose of terraform apply

   The command is used to make your cloud setup real by creating or updating resources defined in your configuration files.

2. Step 2: Compare options with command behavior

   Only It creates or changes cloud resources based on your configuration. correctly describes this behavior. Options A, B, and C describe actions terraform apply does not perform.

3. Final Answer:

   It creates or changes cloud resources based on your configuration. -> Option B

4. Quick Check:

   terraform apply = create/change resources [OK]

Hint: Remember: apply means 'make changes happen' [OK]

Common Mistakes:

• Thinking terraform apply only shows plans without applying
• Confusing terraform apply with terraform destroy
• Assuming terraform apply backs up resources

2. Which of the following is the correct syntax to run terraform apply without asking for approval?

easy

A. terraform apply -skip-confirm

B. terraform apply --no-approval

C. terraform apply -auto-approve

D. terraform apply --force

Solution

1. Step 1: Recall terraform apply options for skipping approval

   The official option to skip manual approval is -auto-approve.

2. Step 2: Verify other options

   Options B, C, and D are not valid terraform flags and will cause errors.

3. Final Answer:

   terraform apply -auto-approve -> Option C

4. Quick Check:

   -auto-approve skips approval [OK]

Hint: Use -auto-approve to skip approval prompt [OK]

Common Mistakes:

• Using incorrect flags like --no-approval
• Trying to use --force which is invalid
• Assuming terraform apply never asks for approval

3. Given this terraform apply output snippet:

Plan: 2 to add, 1 to change, 0 to destroy.

What will happen after you approve the apply?

medium

A. Two resources will be created, one resource will be updated, none deleted.

B. Two resources will be deleted, one created, none updated.

C. One resource will be created, two updated, none deleted.

D. No changes will happen because destroy count is zero.

Solution

1. Step 1: Interpret the plan summary

   The plan says 2 to add means 2 new resources will be created, 1 to change means 1 existing resource will be updated, and 0 to destroy means no resources will be deleted.

2. Step 2: Match the plan to the options

   Only Two resources will be created, one resource will be updated, none deleted. correctly describes this outcome. Options A, C, and D misunderstand the counts.

3. Final Answer:

   Two resources will be created, one resource will be updated, none deleted. -> Option A

4. Quick Check:

   Plan add=2, change=1, destroy=0 [OK]

Hint: Add = create, change = update, destroy = delete [OK]

Common Mistakes:

• Mixing up add and destroy counts
• Assuming zero destroy means no changes at all
• Confusing change with destroy

4. You run terraform apply but get an error: Error: No configuration files found. What is the likely cause?

medium

A. You ran terraform apply in a directory without terraform files.

B. You forgot to initialize terraform with terraform init.

C. You used the wrong terraform version.

D. You did not approve the plan before applying.

Solution

1. Step 1: Understand the error message

   The error says no configuration files found, meaning terraform cannot find any .tf files in the current folder.

2. Step 2: Evaluate options

   You ran terraform apply in a directory without terraform files. matches this cause. You forgot to initialize terraform with terraform init. would cause a different error about initialization. You used the wrong terraform version. is unlikely to cause this specific error. You did not approve the plan before applying. is unrelated because approval happens after plan generation.

3. Final Answer:

   You ran terraform apply in a directory without terraform files. -> Option A

4. Quick Check:

   No .tf files = error [OK]

Hint: Check current folder for .tf files before apply [OK]

Common Mistakes:

• Assuming terraform init missing causes this error
• Thinking approval is needed before apply runs
• Blaming terraform version without checking files

5. You want to automate terraform apply in a CI/CD pipeline but avoid manual approval. Which command and practice is best?

hard

A. Use terraform apply --force to skip all checks.

B. Run terraform apply directly without plan or approval.

C. Run terraform plan only, then manually approve changes later.

D. Use terraform apply -auto-approve after running terraform plan and saving the plan file.

Solution

1. Step 1: Understand CI/CD automation needs

   Automation requires no manual approval and safe application of changes. Saving a plan file ensures the exact changes are applied.

2. Step 2: Evaluate command options

   Use terraform apply -auto-approve after running terraform plan and saving the plan file. correctly uses terraform plan to create a plan file, then applies it with -auto-approve to skip manual confirmation. Run terraform apply directly without plan or approval. skips planning, which is risky. Run terraform plan only, then manually approve changes later. requires manual approval, not automated. Use terraform apply --force to skip all checks. uses an invalid flag.

3. Final Answer:

   Use terraform apply -auto-approve after running terraform plan and saving the plan file. -> Option D

4. Quick Check:

   Plan then apply with -auto-approve for automation [OK]

Hint: Plan first, then apply with -auto-approve in automation [OK]

Common Mistakes:

• Skipping plan step in automation
• Using invalid flags like --force
• Expecting manual approval in CI/CD