Workspace naming conventions in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use workspace naming conventions in Terraform?

Which of the following is the main reason to use workspace naming conventions in Terraform?

A To organize infrastructure environments clearly and avoid resource conflicts

B To encrypt sensitive variables within each workspace

C To automatically generate resource names without manual input

D To speed up Terraform plan execution by caching workspace names

💡 Hint

Think about how naming helps manage multiple environments like dev, test, and prod.

Workspace naming conventions help clearly separate environments and prevent resource conflicts by giving each workspace a unique, descriptive name.

❓ Architecture

intermediate

Choosing workspace names for multiple regions and environments

You manage infrastructure in two regions (us-east-1 and eu-west-1) and three environments (dev, staging, prod). Which workspace naming convention below best supports clear identification?

A env-region (e.g., dev-us-east-1, prod-eu-west-1)

B env only (e.g., dev, staging, prod)

C region-env (e.g., us-east-1-dev, eu-west-1-prod)

D random unique IDs for each workspace

💡 Hint

Consider which order helps you quickly identify region and environment.

Using region-env (like us-east-1-dev) helps group workspaces by region first, which is useful for managing region-specific resources.

❓ Configuration

advanced

Terraform workspace selection with naming conventions

Given the following Terraform CLI commands, which command correctly switches to the production workspace in the us-west-2 region if the naming convention is region-env?

terraform workspace list
* default
  us-west-2-dev
  us-west-2-prod
  us-east-1-prod

A terraform workspace select prod

B terraform workspace select prod-us-west-2

C terraform workspace select us-east-1-prod

D terraform workspace select us-west-2-prod

💡 Hint

Match the exact workspace name from the list.

The workspace name is us-west-2-prod following the region-env convention, so selecting it requires the exact name.

❓ security

advanced

Security risks of poor workspace naming

What is a potential security risk if Terraform workspaces are named inconsistently or unclearly?

A Accidental deployment of sensitive resources to wrong environments

B Terraform automatically encrypts all workspace data regardless of name

C Workspaces with unclear names run slower due to overhead

D Terraform disables state locking for ambiguous workspace names

💡 Hint

Think about how confusion in naming can cause mistakes.

Unclear workspace names can lead to deploying sensitive resources like databases or secrets into the wrong environment, causing security risks.

❓ service_behavior

expert

Effect of workspace naming on Terraform state storage

In Terraform Cloud, how does the workspace name affect the storage and isolation of state files?

A All workspaces share a single state file regardless of name

B Each workspace name corresponds to a separate state file, isolating resources per workspace

C Workspace names only affect logs, not state storage

D Terraform Cloud merges states of workspaces with similar names automatically

💡 Hint

Consider how Terraform Cloud manages state isolation.

Terraform Cloud creates a separate state file for each workspace name, ensuring resource isolation and preventing conflicts.

Practice

1.

What is the main purpose of using workspace names in Terraform?

easy

A. To store Terraform code files

B. To organize different environments like development and production

C. To define cloud provider credentials

D. To create virtual machines automatically

Solution

1. Step 1: Understand workspace role

   Workspaces in Terraform separate different environments or states, like dev and prod.

2. Step 2: Match purpose to options

   Only To organize different environments like development and production describes organizing environments, which is the workspace's main use.

3. Final Answer:

   To organize different environments like development and production -> Option B

4. Quick Check:

   Workspace names = environment organization [OK]

Hint: Workspaces separate environments, not code or credentials [OK]

Common Mistakes:

• Confusing workspace with code storage
• Thinking workspace manages credentials
• Assuming workspace creates resources directly

2.

Which of the following workspace names follows best naming conventions in Terraform?

terraform workspace new ?

easy

A. staging-1

B. dev_environment

C. Prod-Env

D. TestEnv

Solution

1. Step 1: Review naming rules

   Best practice is lowercase letters, hyphens allowed, no underscores or uppercase.

2. Step 2: Check each option

   staging-1 uses lowercase and hyphen, fitting the rules. Others use uppercase or underscores.

3. Final Answer:

   staging-1 -> Option A

4. Quick Check:

   Lowercase + hyphen = staging-1 [OK]

Hint: Use lowercase and hyphens, avoid underscores and capitals [OK]

Common Mistakes:

• Using uppercase letters
• Using underscores instead of hyphens
• Including spaces or special characters

3.

What will happen if you run the command terraform workspace select prod-env but the workspace prod-env does not exist?

medium

A. Terraform shows an error saying workspace not found

B. Terraform deletes the current workspace

C. Terraform switches to the default workspace

D. Terraform creates a new workspace named prod-env automatically

Solution

1. Step 1: Understand workspace select behavior

   The select command switches to an existing workspace; it does not create one.

2. Step 2: Check command outcome

   If the workspace does not exist, Terraform returns an error message.

3. Final Answer:

   Terraform shows an error saying workspace not found -> Option A

4. Quick Check:

   Select non-existent workspace = error [OK]

Hint: Select only switches; create with 'terraform workspace new' [OK]

Common Mistakes:

• Assuming select creates workspace
• Thinking Terraform switches to default silently
• Believing workspace gets deleted

4.

Identify the error in this workspace creation command:

terraform workspace new Dev_Env

medium

A. Workspace names cannot contain uppercase letters

B. Workspace names must start with a number

C. Workspace names must be longer than 10 characters

D. Workspace names cannot contain underscores

Solution

1. Step 1: Check naming rules for characters

   Workspace names should use lowercase letters and hyphens; underscores are not recommended.

2. Step 2: Analyze the command

   The name 'Dev_Env' contains an underscore, which breaks the naming convention.

3. Final Answer:

   Workspace names cannot contain underscores -> Option D

4. Quick Check:

   Underscores disallowed in workspace names [OK]

Hint: Avoid underscores; use hyphens instead [OK]

Common Mistakes:

• Thinking uppercase letters are forbidden (they are discouraged but allowed)
• Believing names must start with numbers
• Assuming length restrictions apply

5.

You want to create workspaces for three environments: development, testing, and production. Which set of workspace names follows best practices for naming conventions?

hard

A. dev, test_env, production

B. development, testing, production

C. dev-01, test-01, prod-01

D. Dev, Test, Prod

Solution

1. Step 1: Review naming best practices

   Use lowercase letters, hyphens allowed, no underscores or uppercase letters.

2. Step 2: Evaluate each option

   dev-01, test-01, prod-01 uses lowercase and hyphens with numbers, fitting best practices. dev, test_env, production uses underscore, B is long but valid, D uses uppercase.

3. Step 3: Choose best consistent and clear naming

   dev-01, test-01, prod-01 is concise, consistent, and follows all rules.

4. Final Answer:

   dev-01, test-01, prod-01 -> Option C

5. Quick Check:

   Lowercase + hyphens + numbers = best practice [OK]

Hint: Use lowercase, hyphens, and numbers for clarity [OK]

Common Mistakes:

• Using uppercase letters
• Using underscores
• Choosing inconsistent naming styles