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.