Why the workflow matters in Terraform - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is the Terraform workflow important?

Terraform has a specific workflow: write configuration, plan changes, and apply them. Why does following this workflow matter?

A It requires manual editing of cloud provider consoles to sync with Terraform state.

B It allows Terraform to skip the planning phase and apply changes immediately for speed.

C It automatically deletes all resources before creating new ones to avoid conflicts.

D It ensures changes are previewed before applying, preventing unexpected infrastructure updates.

💡 Hint

Think about how seeing changes before applying helps avoid mistakes.

The Terraform workflow helps you preview changes with terraform plan before applying them. This prevents surprises and accidental resource changes.

❓ service_behavior

intermediate

What happens if you skip 'terraform plan'?

You run terraform apply directly without running terraform plan first. What is the likely result?

A Terraform deletes the state file to reset infrastructure tracking.

B Terraform applies changes immediately, which may cause unexpected resource modifications.

C Terraform automatically creates a plan and applies it without showing details.

D Terraform refuses to apply changes and shows an error requiring a plan first.

💡 Hint

Consider what happens when you don't preview changes.

Skipping terraform plan means you don't see what will change. Applying directly can cause unexpected updates or deletions.

❓ Architecture

advanced

How does remote state storage improve Terraform workflow?

Terraform can store its state file locally or remotely. How does using remote state storage improve the workflow in a team environment?

A It disables the need for <code>terraform plan</code> by syncing changes instantly.

B It automatically encrypts all Terraform code to prevent unauthorized access.

C It allows multiple team members to share and lock the state file, preventing conflicts during concurrent changes.

D It forces Terraform to recreate all resources on every apply to ensure consistency.

💡 Hint

Think about how teams avoid overwriting each other's work.

Remote state storage enables state sharing and locking, so team members don't overwrite each other's changes and can coordinate safely.

❓ security

advanced

Why should Terraform state files be secured?

Terraform state files contain detailed information about your infrastructure. Why is it important to secure these files?

A Because state files may contain sensitive data like passwords, keys, or resource details that could be exploited if exposed.

B Because unsecured state files cause Terraform to crash during apply.

C Because state files are automatically deleted if not secured, causing loss of infrastructure tracking.

D Because securing state files speeds up Terraform plan execution.

💡 Hint

Consider what kind of information Terraform stores about your resources.

State files can include sensitive info like passwords or API keys. If exposed, attackers could misuse this data.

✅ Best Practice

expert

What is the best practice for managing Terraform workflow in a CI/CD pipeline?

In a continuous integration/continuous deployment (CI/CD) pipeline, what is the best practice to handle Terraform workflow steps?

A Run <code>terraform plan</code> to generate a plan, review it manually, then run <code>terraform apply</code> automatically only after approval.

B Skip Terraform commands and manually update cloud resources in the console during deployment.

C Run <code>terraform apply</code> directly on every code push to speed up deployments.

D Store Terraform state locally on the CI server and delete it after each run.

💡 Hint

Think about safety and automation balance in pipelines.

Generating a plan and requiring manual approval before applying changes ensures safe, controlled infrastructure updates in CI/CD.