Question

Your team uses CLI workspaces with an S3 remote backend to manage separate state for dev, staging, and prod. A colleague asks where the state for the non-default workspaces is physically stored relative to the default workspace's state. Which statement correctly describes how Terraform stores workspace state with a remote backend?

Accepted Answer

Non-default workspace states are stored in a separate 'env:/<workspace_name>/' path within the same backend, isolated from the default workspace's state.

Answer

All workspaces share a single state file, and Terraform uses in-file namespacing to separate resources by workspace.

Answer

Each workspace requires a completely separate backend configuration block defined in its own directory.

Answer

Workspace states are only stored locally in the terraform.tfstate.d directory; remote backends ignore workspaces entirely.