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'.