⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Terraform & IaC Interview Questions Scenario 18 of 120 in Terraform & IaC
Senior DevOps / SRE [L2] Terraform Workspaces & CI/CD Production Scenario [L2]
🎯 Target Role / Context: Terraform Scenario #13 (L2) · Workspaces & CI/CD

Q: What is a Terraform workspace and what are its limitations?

Workspaces let you maintain multiple state files for the same configuration. terraform workspace new staging creates a staging workspace with its own state.

#Terraform #Workspaces & CI/CD #L2 #IaC #Cloud Infrastructure #S3
🎙️ Candidate Opening & Architectural Context
""Managing infrastructure as code across multiple teams requires disciplined state management and locking. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix.""
Advertisement
⚡ Recommended Practice Lab

Want to master this scenario in a live sandbox? KodeKloud's HashiCorp Certified Terraform Associate (003) Interactive Labs covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: "Managing infrastructure as code across multiple teams requires disciplined state management and locking. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."

1️⃣

Initial Diagnostics & Root Cause Analysis

Workspaces let you maintain multiple state files for the same configuration. terraform workspace new staging creates a staging workspace with its own state.

  • All workspaces use the same code — config differences between environments are hard (you'd use terraform.workspace variable conditionals, which gets messy).
  • Same backend — all workspace state files are in the same S3 bucket, just different keys.
  • No access control — you can't restrict who applies to production workspace vs dev workspace.
2️⃣

Remediation & Permanent Safeguards

Limitations: Use workspaces for: small teams, temporary environments, exactly-same-config use cases. Don't use workspaces for: production vs staging (different configs, different access controls).

  • Better alternative for multiple environments: separate directories/modules, not workspaces.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: All workspaces use the same code — config differences between environments are hard (you'd use terraform.workspace variable condit."
⚡ 60-Second Elevator Pitch Talking Points
  • All workspaces use the same code — config differences between environments are hard (you'd use te...
  • Same backend — all workspace state files are in the same S3 bucket, just different keys.
  • No access control — you can't restrict who applies to production workspace vs dev workspace.
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Relying on legacy bucket ACLs instead of modern S3 Block Public Access and IAM bucket policies when configuring Terraform workspace limitations AWS recommends disabling ACLs (Bucket Owner Enforced) in favor of centralized declarative bucket policies and account-level Block Public Access controls.
  2. Confusing SSE-S3 encryption with KMS customer-managed key (SSE-KMS) authorization policies when configuring Terraform workspace limitations Accessing SSE-KMS encrypted objects requires both s3:GetObject and kms:Decrypt permissions; neglecting KMS key policies causes silent 403 Forbidden errors.
  3. Using sequential timestamps or predictable prefixes for high-throughput S3 read and write keys when configuring Terraform workspace limitations Sequential key prefixes limit S3 horizontal partitioning; randomized hash prefixes distribute workloads across partitions to achieve 3,500 PUT and 5,500 GET requests/sec.
  4. Failing to audit S3 object delete markers when troubleshooting missing versioned objects when configuring Terraform workspace limitations Issuing a DELETE on a versioned bucket only adds a delete marker; engineers must retrieve previous versions or purge markers to restore data.
Advertisement
Want more Terraform & IaC scenarios?
Explore our complete collection of scenario-based Terraform & IaC interview runbooks.
Browse All Terraform & IaC Questions →