Workspaces and remote state in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Terraform Workspaces

What is the primary purpose of Terraform workspaces?

A To store Terraform configuration files remotely for team collaboration.

B To encrypt sensitive variables in Terraform configurations.

C To automatically back up state files to cloud storage.

D To manage multiple distinct state files within the same configuration, allowing isolated environments like dev and prod.

💡 Hint

Think about how Terraform separates environments using the same code.

Terraform workspaces allow you to use the same configuration but keep separate state files for different environments or instances.

❓ Configuration

intermediate

Remote State Backend Configuration

Which backend configuration snippet correctly sets up Terraform to use an AWS S3 bucket for remote state storage with state locking?

A

terraform {
  backend "s3" {
    bucket = "my-terraform-state"
    key    = "prod/terraform.tfstate"
    region = "us-east-1"
    dynamodb_table = "terraform-lock"
    encrypt = true
  }
}

B

terraform {
  backend "local" {
    path = "./terraform.tfstate"
  }
}

C

terraform {
  backend "s3" {
    bucket = "my-terraform-state"
    key    = "prod/terraform.tfstate"
    region = "us-east-1"
    encrypt = false
  }
}

D

terraform {
  backend "s3" {
    bucket = "my-terraform-state"
    key    = "prod/terraform.tfstate"
    region = "us-east-1"
    dynamodb_table = ""
    encrypt = true
  }
}

💡 Hint

Look for the option that includes state locking and encryption.

Option A correctly configures the S3 backend with encryption and DynamoDB table for state locking, which prevents concurrent state modifications.

❓ Architecture

advanced

Choosing Workspace Strategy for Multiple Environments

You have a Terraform configuration for a web app. You want to deploy it to dev, staging, and production environments. Which approach best uses Terraform workspaces to manage these environments?

A Create three workspaces named dev, staging, and prod. Use the same configuration and switch workspaces to deploy to each environment.

B Create separate Terraform configurations for each environment and use only the default workspace.

C Use a single workspace and pass environment variables to differentiate environments during deployment.

D Use local state files for each environment and avoid workspaces.

💡 Hint

Think about how workspaces isolate state but share configuration.

Using separate workspaces for each environment allows you to reuse the same configuration while keeping state isolated per environment.

❓ security

advanced

Securing Remote State Access

Which practice best secures access to Terraform remote state stored in an AWS S3 bucket?

A Store the state file locally and share it via email to avoid cloud exposure.

B Make the S3 bucket public so all team members can access the state file easily.

C Use IAM policies to restrict access to the S3 bucket and DynamoDB table only to authorized users and roles.

D Disable encryption on the S3 bucket to improve performance.

💡 Hint

Consider AWS best practices for securing sensitive data.

Restricting access with IAM policies ensures only authorized users can read or modify the remote state, protecting sensitive infrastructure data.

❓ service_behavior

expert

Effect of Workspace Switch on Terraform State

Given a Terraform configuration with multiple workspaces, what happens to the state when you run terraform workspace select staging?

A Terraform deletes the current workspace state and replaces it with the 'staging' workspace state.

B Terraform switches to the 'staging' workspace and loads its separate state file, isolating resources from other workspaces.

C Terraform ignores the workspace switch and continues using the default workspace state.

D Terraform merges the 'staging' workspace state with the default workspace state into a single file.

💡 Hint

Think about how workspaces isolate state files.

Switching workspaces loads the state specific to that workspace, keeping resources isolated per environment.