How do Terraform workspaces work and when should you use them?
Interviewer Expectations for this Question
01
Core Competency
Assesses fundamental understanding of Terraform & IaC conventions, runtime behavior, and memory/performance considerations.
02
Evaluation Criteria
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
Comprehensive Model Answer
Verified Solution
Workspaces let one configuration manage multiple, separate states. terraform.workspace is a variable naming the active workspace, and the default workspace always exists.
terraform workspace new dev
terraform workspace new prod
terraform workspace select prod
terraform workspace list
Each workspace has its own state, so resources are isolated. With the S3 backend, state goes to different keys per workspace.
Use cases:
- Ephemeral environments for testing or feature branches.
- Lightweight separation of dev, staging, and prod from one codebase.
Cautions:
- Workspaces share the same configuration and variables, so environment differences must be parameterised.
- They are easy to confuse, and a wrong selection can target production.
- They do not provide strong isolation or separate credentials.
For serious environments, prefer separate directories or repositories with distinct backends and accounts. Use workspaces for temporary or closely related environments.
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.