Default workspace in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Terraform Default Workspace Behavior

What is the default workspace name when you initialize a new Terraform configuration without creating any additional workspaces?

A terraform

B main

C default

D prod

💡 Hint

Think about the workspace Terraform uses if you never switch or create a new one.

Terraform uses a workspace named default automatically if no other workspace is selected or created.

❓ service_behavior

intermediate

Effect of Workspace on Terraform State Files

When you switch from the default workspace to a new workspace named dev, what happens to the Terraform state files?

A Terraform creates a separate state file for the <code>dev</code> workspace.

B Terraform merges the <code>dev</code> workspace state with the default workspace state file.

C Terraform overwrites the existing default workspace state file with the <code>dev</code> workspace state.

D Terraform deletes the default workspace state file.

💡 Hint

Think about how Terraform isolates environments using workspaces.

Each workspace has its own separate state file to isolate infrastructure states.

❓ Architecture

advanced

Workspace Usage in Multi-Environment Terraform Architecture

You want to manage production and staging environments using Terraform workspaces. Which approach correctly uses workspaces to separate these environments?

A Create separate Terraform configurations for production and staging without using workspaces.

B Create two workspaces named <code>production</code> and <code>staging</code>, and switch between them to apply changes to each environment.

C Use the default workspace for production and create a <code>staging</code> workspace for staging environment.

D Use one workspace and manage both environments by passing different variables during apply.

💡 Hint

Workspaces are designed to isolate state for different environments.

Creating separate workspaces for production and staging allows isolated state management and easy switching.

❓ security

advanced

Security Implications of Using Default Workspace

What is a potential security risk of using the default workspace for multiple environments in Terraform?

A State files for different environments can overwrite each other, leading to accidental resource changes.

B Default workspace encrypts state files with weak encryption.

C Default workspace automatically exposes state files publicly.

D Default workspace disables Terraform state locking.

💡 Hint

Consider what happens if multiple environments share the same state file.

Using the default workspace for multiple environments risks overwriting state files, causing unintended resource changes.

✅ Best Practice

expert

Best Practice for Managing Terraform Workspaces in Team Environments

In a team environment, what is the best practice to manage Terraform workspaces to avoid conflicts and ensure smooth collaboration?

A Use the default workspace only and manually rename state files to separate environments.

B Each team member uses their own local default workspace without sharing state remotely.

C Avoid using workspaces and manage environments by duplicating Terraform code for each environment.

D Use remote backend with workspace support and enforce workspace naming conventions for each environment.

💡 Hint

Think about how teams can share state safely and avoid conflicts.

Using a remote backend with workspace support and naming conventions helps teams collaborate safely and avoid state conflicts.