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

Most backends support named workspaces, but some backends (like the http backend) may have limited or no workspace support.

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

Because all workspaces share the same .tf files, they are best suited for environments with identical or nearly identical infrastructure — not for deeply divergent configurations.

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

Using `terraform.workspace` in a `count` or `for_each` expression is the standard pattern for conditionally deploying resources based on the active workspace.

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

HashiCorp recommends separate configurations when environments diverge significantly, as workspaces are best for parallel deployments of nearly identical infrastructure.

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

A newly created workspace has no state, so `terraform plan` will show all resources as new additions, as if deploying from scratch.

Terraform Associate Practice Test

Terraform Associate Practice Test

HashiCorp Terraform Associate Terraform Workspaces 3