HashiCorp Terraform Associate Terraform Workspaces 3

Question 1

Which statement about backend support for Terraform workspaces is accurate?

Accepted Answer

Most backends support workspaces, but not all backends implement workspace functionality

Answer

Only the local backend supports workspaces

Answer

Only remote backends like S3 and Azure Blob support workspaces

Answer

All backends equally and fully support workspaces without restriction

Question 2

What is a key limitation of using workspaces compared to completely separate Terraform configurations?

Accepted Answer

Workspaces share the same configuration code, making large structural differences difficult to manage

Answer

Workspaces cannot use modules or external providers

Answer

Workspaces do not support input variables or local values

Answer

Workspaces cannot be used with any remote backend

Question 3

How can you conditionally create a resource only in the 'production' workspace?

Accepted Answer

By using `count = terraform.workspace == "production" ? 1 : 0` on the resource

Answer

By using a workspace-specific resource file named production.tf

Answer

By adding a workspace argument to the resource block

Answer

By using a workspace-specific provider alias

Question 4

When does HashiCorp recommend using separate directory-based configurations instead of workspaces?

Accepted Answer

When managing environments that have significantly different infrastructure structures

Answer

Whenever Terraform Cloud is used instead of the CLI

Answer

When the number of environments is fewer than three

Answer

Whenever modules are included in the configuration

Question 5

What does `terraform plan` show immediately after running `terraform workspace new myenv`?

Accepted Answer

Terraform plans against an empty state because the new workspace has no existing state

Answer

The plan uses state from the previously active workspace as a baseline

Answer

Terraform automatically imports existing infrastructure resources into the plan

Answer

The plan fails and requires `terraform init` to be run first in the new workspace

Question 6

Which approach is recommended when different workspaces need different values for a variable like instance_type?

Accepted Answer

Use a map variable indexed by workspace name and look up the value with terraform.workspace

Answer

Create separate variable definition files (.tfvars) and select them with -var-file per workspace

Answer

Hard-code the values directly into resource blocks per workspace using conditionals

Answer

Define the variable multiple times with workspace-specific names

Question 7

What happens when you attempt to delete a workspace that still has resources in its state?

Accepted Answer

The delete command fails with an error unless the -force flag is provided

Answer

Terraform automatically runs destroy before deleting the workspace

Answer

The delete command succeeds but orphans the state file on disk

Answer

Terraform prompts you to confirm before proceeding with deletion