Default workspace in Terraform - Time & Space Complexity

Time Complexity: Default workspace

O(n)

Understanding Time Complexity

When using Terraform, the default workspace manages your infrastructure state. Understanding how operations scale with workspace use helps us know how long deployments take.

We want to see how the number of API calls changes as we use the default workspace for multiple resources.

Scenario Under Consideration

Analyze the time complexity of the following Terraform configuration using the default workspace.

resource "aws_instance" "example" {
  count         = var.instance_count
  ami           = "ami-12345678"
  instance_type = "t2.micro"
}
    

This code creates multiple AWS instances in the default workspace based on the count variable.

Identify Repeating Operations

Each instance creation triggers API calls to AWS.

• Primary operation: API call to create each AWS instance.
• How many times: Once per instance, equal to the count variable.

How Execution Grows With Input

As you increase the number of instances, the number of API calls grows directly with it.

Input Size (n)	Approx. API Calls/Operations
10	10 API calls
100	100 API calls
1000	1000 API calls

Pattern observation: The number of API calls grows linearly with the number of instances.

Final Time Complexity

Time Complexity: O(n)

This means the time to create resources grows directly in proportion to how many you create.

Common Mistake

[X] Wrong: "Using the default workspace means all resources are created with a single API call regardless of count."

[OK] Correct: Each resource still requires its own API call; the workspace just manages state, not batching.

Interview Connect

Knowing how resource count affects API calls helps you plan deployments and understand Terraform's behavior in real projects.

Self-Check

"What if we switched from the default workspace to multiple named workspaces? How would the time complexity change?"

Practice

1. What is the default workspace in Terraform?

easy

A. A workspace only for remote backends

B. A workspace you must create manually before use

C. A temporary workspace that deletes after each run

D. The main workspace Terraform uses automatically to store state

Solution

1. Step 1: Understand Terraform workspaces

   Terraform uses workspaces to manage different states. The default workspace is created automatically.

2. Step 2: Identify the role of the default workspace

   The default workspace stores the state unless you create and switch to others.

3. Final Answer:

   The main workspace Terraform uses automatically to store state -> Option D

4. Quick Check:

   Default workspace = main automatic workspace [OK]

Hint: Default workspace is automatic and stores state by default [OK]

Common Mistakes:

• Thinking default workspace must be created manually
• Assuming default workspace deletes after runs
• Confusing default workspace with remote backend only

2. Which command shows the current active workspace in Terraform?

easy

A. terraform workspace list

B. terraform workspace show

C. terraform workspace current

D. terraform workspace status

Solution

1. Step 1: Recall Terraform workspace commands

   Common commands include list to see all workspaces and show to display the current one.

2. Step 2: Identify the command to show active workspace

   terraform workspace show outputs the current active workspace name.

3. Final Answer:

   terraform workspace show -> Option B

4. Quick Check:

   Show current workspace = terraform workspace show [OK]

Hint: Use 'terraform workspace show' to see active workspace [OK]

Common Mistakes:

• Using 'terraform workspace list' to show current workspace
• Assuming 'terraform workspace current' is valid
• Confusing 'status' with workspace commands

3. Given this Terraform CLI output after running terraform workspace list:

  default
* dev
  staging

Which workspace is currently active?

medium

A. default

B. staging

C. dev

D. No workspace is active

Solution

1. Step 1: Understand workspace list output format

   The asterisk (*) marks the currently active workspace in the list.

2. Step 2: Identify the active workspace

   The workspace with * is dev, so it is active.

3. Final Answer:

   dev -> Option C

4. Quick Check:

   Asterisk marks active workspace = dev [OK]

Hint: Look for * in workspace list to find active workspace [OK]

Common Mistakes:

• Choosing 'default' because it sounds like default
• Ignoring the asterisk symbol
• Assuming no workspace is active if not obvious

4. You run terraform workspace new test but get an error: "Workspace 'test' already exists." What should you do next?

medium

A. Run terraform workspace select test to switch to it

B. Delete the existing workspace with terraform workspace delete test

C. Rename the existing workspace before creating a new one

D. Run terraform init again to fix the error

Solution

1. Step 1: Understand the error message

   The error says the workspace already exists, so you cannot create it again.

2. Step 2: Choose the correct action

   Since it exists, you should switch to it using terraform workspace select test.

3. Final Answer:

   Run terraform workspace select test to switch to it -> Option A

4. Quick Check:

   Workspace exists? Select it, don't create [OK]

Hint: Select existing workspace instead of creating it again [OK]

Common Mistakes:

• Trying to create workspace again without switching
• Deleting workspace unnecessarily
• Running init does not fix workspace existence

5. You want to manage two environments, prod and dev, using Terraform workspaces. Which approach correctly uses the default workspace?

hard

A. Use default workspace for dev and create/select prod workspace

B. Create both prod and dev workspaces and never use default

C. Rename default workspace to prod and create dev workspace

D. Use the default workspace for prod and create/select dev workspace

Solution

1. Step 1: Understand default workspace role

   The default workspace is ready to use and often used for simpler or initial environments.

2. Step 2: Apply best practice for environment separation

   Use default for dev (development) and create/select a separate workspace for prod (production) to isolate states.

3. Final Answer:

   Use default workspace for dev and create/select prod workspace -> Option A

4. Quick Check:

   Default workspace = dev environment [OK]

Hint: Use default for dev, create prod workspace for safety [OK]

Common Mistakes:

• Using default for prod which risks accidental changes
• Ignoring default workspace and creating all manually
• Trying to rename default workspace (not supported)