Workspaces vs directory-based separation in Terraform - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Terraform Workspaces

What is the primary purpose of Terraform workspaces?

A To manage multiple distinct state files within the same configuration for different environments

B To separate Terraform configurations into different directories for better organization

C To create isolated virtual machines in the cloud

D To automatically backup Terraform state files to cloud storage

💡 Hint

Think about how Terraform handles state files for different environments.

Terraform workspaces allow you to use the same configuration but keep separate state files, which is useful for managing multiple environments like dev, staging, and prod.

❓ Architecture

intermediate

Directory-based Separation in Terraform

Which statement best describes directory-based separation in Terraform?

A Using separate directories with their own Terraform configurations and state files for different environments or projects

B Using Terraform modules to share code between environments

C Using workspaces to switch between environments within the same directory

D Using a single directory with multiple state files stored remotely

💡 Hint

Consider how physical file organization affects Terraform state and configuration.

Directory-based separation means creating separate folders each with its own Terraform files and state, isolating environments or projects physically on disk.

✅ Best Practice

advanced

Choosing Between Workspaces and Directory Separation

Which scenario is best suited for using Terraform workspaces instead of directory-based separation?

A When you want to share state files across multiple teams

B When you want to keep all environment configurations in separate version control repositories

C Managing completely different projects with unrelated infrastructure

D Managing multiple similar environments with mostly identical infrastructure and small differences

💡 Hint

Think about when sharing the same configuration but separating state is helpful.

Workspaces are ideal when environments share the same code but need separate states, like dev and prod with minor differences.

❓ security

advanced

Security Implications of Workspaces vs Directory Separation

Which security risk is more likely when using Terraform workspaces compared to directory-based separation?

A Difficulty in managing access controls on state files stored locally

B State file corruption from multiple directories accessing the same backend

C Accidental modification of the wrong environment's infrastructure due to shared configuration

D Increased risk of code duplication leading to inconsistent security policies

💡 Hint

Consider how workspaces share the same configuration but differ only by state.

Because workspaces use the same configuration, a user might accidentally apply changes to the wrong workspace, affecting the wrong environment.

❓ service_behavior

expert

Terraform Workspace State Behavior

Given the following Terraform commands run in sequence, what is the output of terraform workspace show after the last command?

terraform workspace new staging
terraform workspace select default
terraform workspace list
terraform workspace show

A staging

B default

C Error: workspace does not exist

D No workspace selected

💡 Hint

Remember the effect of terraform workspace select on the active workspace.

The commands create a new workspace named 'staging', then switch back to 'default'. The list shows both workspaces. The last command shows the currently selected workspace, which is 'default'.

Practice

1. What is the main difference between Terraform workspaces and directory-based separation?

easy

A. Workspaces require separate folders; directory-based uses one folder with multiple states.

B. Workspaces store state remotely; directory-based stores state locally only.

C. Workspaces and directory-based separation are exactly the same.

D. Workspaces use one folder with multiple states; directory-based uses separate folders for each environment.

Solution

1. Step 1: Understand workspace concept

   Workspaces allow multiple states inside the same folder by switching context.

2. Step 2: Understand directory-based separation

   Directory-based separation uses different folders, each with its own code and state files.

3. Final Answer:

   Workspaces use one folder with multiple states; directory-based uses separate folders for each environment. -> Option D

4. Quick Check:

   Workspaces = one folder, multiple states [OK]

Hint: Workspaces = one folder, directory = multiple folders [OK]

Common Mistakes:

• Confusing workspace with directory-based separation
• Thinking workspaces require multiple folders
• Assuming directory-based uses one state file

2. Which Terraform command correctly switches to a workspace named dev?

easy

A. terraform workspace select dev

B. terraform select workspace dev

C. terraform switch workspace dev

D. terraform workspace change dev

Solution

1. Step 1: Recall Terraform workspace commands

   The correct command to switch workspace is terraform workspace select <name>.

2. Step 2: Match command to options

   Only terraform workspace select dev matches the correct syntax exactly.

3. Final Answer:

   terraform workspace select dev -> Option A

4. Quick Check:

   Switch workspace = terraform workspace select [OK]

Hint: Use 'terraform workspace select' to switch workspaces [OK]

Common Mistakes:

• Using incorrect command order
• Using non-existent commands like 'switch' or 'change'
• Confusing workspace commands with other terraform commands

3. Given this folder structure:

envs/
  ├─ dev/
  │    └─ main.tf
  └─ prod/
       └─ main.tf

and using directory-based separation, what happens if you run terraform apply inside envs/dev?

medium

A. Terraform applies changes to both dev and prod environments simultaneously.

B. Terraform applies changes only to the dev environment using its own state.

C. Terraform throws an error because state is missing.

D. Terraform applies changes to the prod environment instead.

Solution

1. Step 1: Understand directory-based separation behavior

   Each folder has its own Terraform code and state, so running inside envs/dev affects only dev.

2. Step 2: Analyze command effect

   terraform apply in envs/dev applies changes only to dev environment's resources.

3. Final Answer:

   Terraform applies changes only to the dev environment using its own state. -> Option B

4. Quick Check:

   Directory-based apply affects current folder environment [OK]

Hint: Apply runs in current folder's environment only [OK]

Common Mistakes:

• Assuming apply affects all environments
• Thinking state is shared across folders
• Expecting errors due to missing state

4. You created a new workspace named staging but when running terraform apply, changes apply to the default workspace instead. What is the likely cause?

medium

A. You forgot to run terraform workspace select staging before applying.

B. The staging workspace does not exist.

C. Terraform does not support multiple workspaces.

D. You need to rename the default workspace to staging.

Solution

1. Step 1: Check workspace usage

   Creating a workspace does not switch to it automatically; you must select it explicitly.

2. Step 2: Identify missing command

   If you don't run terraform workspace select staging, Terraform stays in default workspace.

3. Final Answer:

   You forgot to run terraform workspace select staging before applying. -> Option A

4. Quick Check:

   Must select workspace before apply [OK]

Hint: Always select workspace before applying changes [OK]

Common Mistakes:

• Assuming workspace auto-switches after creation
• Thinking workspace names must be renamed
• Believing Terraform lacks workspace support

5. You want to manage three environments: dev, staging, and prod. You want to keep code DRY (Don't Repeat Yourself) and share most configuration but keep states isolated. Which approach is best?

hard

A. Use one folder and switch backend configuration files for each environment.

B. Create three separate folders, each with full copies of code and state.

C. Use one folder with Terraform workspaces for each environment.

D. Use one folder and manually rename state files for each environment.

Solution

1. Step 1: Analyze DRY and state isolation needs

   Sharing code but isolating state fits well with workspaces, which share code folder but separate states.

2. Step 2: Compare options

   Use one folder with Terraform workspaces for each environment uses workspaces to keep one codebase and separate states per environment, avoiding code duplication.

3. Step 3: Evaluate other options

   Create three separate folders, each with full copies of code and state duplicates code, violating DRY. Use one folder and manually rename state files for each environment is error-prone and manual. Use one folder and switch backend configuration files for each environment requires backend changes, complex to manage.

4. Final Answer:

   Use one folder with Terraform workspaces for each environment. -> Option C

5. Quick Check:

   Workspaces = shared code, separate states [OK]

Hint: Workspaces share code, separate states for DRY environments [OK]

Common Mistakes:

• Duplicating code in multiple folders unnecessarily
• Trying manual state file renaming
• Switching backend configs frequently