When workspaces are appropriate in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Terraform Workspaces

Which scenario best describes when to use Terraform workspaces?

A Managing multiple environments like dev, staging, and prod within the same configuration.

B Storing sensitive variables securely outside of Terraform state files.

C Running Terraform commands faster by caching resources locally.

D Automatically scaling cloud resources based on traffic.

💡 Hint

Think about how Terraform separates state for different deployments.

Terraform workspaces allow you to keep separate state files for different environments using the same configuration code.

❓ Architecture

intermediate

Workspace Usage in Infrastructure Architecture

You have a Terraform configuration for a web app. You want to deploy it to two AWS accounts: one for testing and one for production. How should you use workspaces?

A Use one workspace and change the AWS provider credentials manually before each deploy.

B Create separate workspaces named 'test' and 'prod' and switch between them to deploy to each account.

C Create multiple Terraform configurations, one per account, without using workspaces.

D Use workspaces only for different regions, not accounts.

💡 Hint

Workspaces help manage multiple states but consider provider credentials.

Workspaces isolate state files, so you can deploy the same config to different accounts by switching workspaces and setting provider credentials accordingly.

❓ service_behavior

advanced

Effect of Workspace Switch on Terraform State

What happens to the Terraform state when you switch from the 'default' workspace to a new workspace named 'feature'?

A Terraform loads a separate state file for 'feature', isolating its resources from 'default'.

B Terraform merges the 'feature' workspace state with the 'default' workspace state.

C Terraform deletes the 'default' workspace state and replaces it with 'feature' state.

D Terraform keeps using the 'default' workspace state regardless of the switch.

💡 Hint

Think about how workspaces isolate state files.

Each workspace has its own state file. Switching to 'feature' loads its own state, separate from 'default'.

❓ security

advanced

Security Considerations with Terraform Workspaces

Which statement about security when using Terraform workspaces is true?

A Workspaces store sensitive data separately from the state file to enhance security.

B Workspaces automatically encrypt all sensitive variables in the state file.

C Using multiple workspaces prevents unauthorized access to any state files by default.

D Workspaces do not encrypt state files; sensitive data must be protected by backend encryption or access controls.

💡 Hint

Consider how Terraform stores state and sensitive data.

Workspaces separate state files but do not encrypt them. Encryption and access control depend on the backend used.

✅ Best Practice

expert

Best Practice for Using Workspaces in Large Teams

In a large team managing multiple environments with Terraform, what is the best practice regarding workspaces?

A Use a single workspace for all environments to simplify management.

B Create one workspace per team member to avoid conflicts.

C Use workspaces only for short-lived feature branches; use separate configurations or backends for long-term environments.

D Avoid workspaces entirely and manage state files manually.

💡 Hint

Think about state isolation and team collaboration challenges.

Workspaces are good for temporary isolation like feature branches. For stable environments, separate configurations or backends reduce risk of accidental changes.

Practice

1. What is the main purpose of using terraform workspaces?

easy

A. To store Terraform modules

B. To write Terraform code faster

C. To manage multiple environments like development and production with one configuration

D. To increase the speed of Terraform apply

Solution

1. Step 1: Understand workspace purpose

   Workspaces allow you to keep separate states for different environments using the same Terraform code.

2. Step 2: Compare options

   Options A, B, and C do not relate to managing environments or state separation.

3. Final Answer:

   To manage multiple environments like development and production with one configuration -> Option C

4. Quick Check:

   Workspaces = separate environment states [OK]

Hint: Workspaces separate states for different environments [OK]

Common Mistakes:

• Thinking workspaces speed up Terraform runs
• Confusing workspaces with modules
• Believing workspaces store code

2. Which command correctly switches to a workspace named testing?

easy

A. terraform workspace select testing

B. terraform switch workspace testing

C. terraform workspace switch testing

D. terraform use workspace testing

Solution

1. Step 1: Recall correct workspace switch syntax

   The correct command to switch workspaces is terraform workspace select [name].

2. Step 2: Validate options

   Options A, B, and D use incorrect command syntax not recognized by Terraform.

3. Final Answer:

   terraform workspace select testing -> Option A

4. Quick Check:

   Switch workspace = terraform workspace select [name] [OK]

Hint: Use 'terraform workspace select <name>' to switch [OK]

Common Mistakes:

• Using 'switch' instead of 'select'
• Mixing command order
• Adding extra words like 'workspace' twice

3. Given the commands below, what will be the output of terraform workspace show after these steps?

terraform workspace new dev
terraform workspace select dev
terraform workspace new prod
terraform workspace select prod
terraform workspace show

medium

A. prod

B. dev

C. default

D. Error: workspace not found

Solution

1. Step 1: Follow workspace creation and switching

   First, 'dev' workspace is created and switched to. Then 'prod' workspace is created and switched to.

2. Step 2: Check current workspace

   After switching to 'prod', running 'terraform workspace show' outputs the current workspace name, which is 'prod'.

3. Final Answer:

   prod -> Option A

4. Quick Check:

   Last switched workspace = prod [OK]

Hint: Last 'terraform workspace select' sets current workspace [OK]

Common Mistakes:

• Assuming default workspace remains active
• Confusing creation with switching
• Expecting error without reason

4. You run terraform workspace select staging but get an error saying the workspace does not exist. What should you do to fix this?

medium

A. Rename the workspace to default

B. Run terraform init again

C. Delete the current workspace and try again

D. Run terraform workspace new staging to create it first

Solution

1. Step 1: Understand error cause

   The error means the workspace 'staging' does not exist yet in Terraform state.

2. Step 2: Create the missing workspace

   Use terraform workspace new staging to create it before switching.

3. Final Answer:

   Run terraform workspace new staging to create it first -> Option D

4. Quick Check:

   Workspace must exist before select [OK]

Hint: Create workspace before using it [OK]

Common Mistakes:

• Trying to switch without creating workspace
• Reinitializing Terraform unnecessarily
• Deleting workspaces without cause

5. You want to manage three environments: dev, test, and prod using one Terraform configuration. Which approach best uses workspaces to achieve this safely?

hard

A. Use one workspace and manually change resource names for each environment

B. Create separate workspaces named dev, test, prod and switch before applying changes

C. Create three separate Terraform configurations for each environment

D. Use workspaces only for prod and dev, but not test

Solution

1. Step 1: Identify workspace use for multiple environments

   Workspaces allow managing multiple environment states with one config by switching between them.

2. Step 2: Evaluate options for safety and simplicity

   Create separate workspaces named dev, test, prod and switch before applying changes uses separate workspaces for each environment, which is safe and clean. Use one workspace and manually change resource names for each environment risks conflicts. Create three separate Terraform configurations for each environment duplicates code. Use workspaces only for prod and dev, but not test is inconsistent.

3. Final Answer:

   Create separate workspaces named dev, test, prod and switch before applying changes -> Option B

4. Quick Check:

   Separate workspaces = safe multi-env management [OK]

Hint: Use one workspace per environment for safety [OK]

Common Mistakes:

• Mixing environments in one workspace
• Duplicating configs unnecessarily
• Ignoring test environment