Exam Terraform Associate topic 1 question 2 discussion

correct B

1 workspace -> 1 backend 1 backend -> multiple workspaces

A single remote backend configuration can support multiple remote workspaces. In Terraform, remote backends like Terraform Cloud or remote state storage solutions can manage multiple workspaces, each representing a different environment or set of infrastructure, all within the same backend configuration.

The remote backend can work with either a single remote Terraform Cloud workspace, or with multiple similarly-named remote workspaces (like networking-dev and networking-prod). The workspaces block of the backend configuration determines which mode it uses: To use a single remote Terraform Cloud workspace, set workspaces.name to the remote workspace's full name (like networking-prod). To use multiple remote workspaces, set workspaces.prefix to a prefix used in all of the desired remote workspace names. For example, set prefix = "networking-" to use Terraform cloud workspaces with names like networking-dev and networking-prod. This is helpful when mapping multiple Terraform CLI workspaces used in a single Terraform configuration to multiple Terraform Cloud workspaces. https://developer.hashicorp.com/terraform/language/settings/backends/remote

Answer should be B False. Workspaces (offical documentation --> https://developer.hashicorp.com/terraform/language/settings/backends/remote#workspaces) The remote backend can work with either a single remote HCP Terraform workspace, or with multiple similarly-named remote workspaces (like networking-dev and networking-prod). The workspaces block of the backend configuration determines which mode it uses: To use a single remote HCP Terraform workspace, set workspaces.name to the remote workspace's full name (like networking-prod). To use multiple remote workspaces, set workspaces.prefix to a prefix used in all of the desired remote workspace names. For example, set prefix = "networking-" to use HCP Terraform workspaces with names like networking-dev and networking-prod. This is helpful when mapping multiple Terraform CLI workspaces used in a single Terraform configuration to multiple HCP Terraform workspaces.

vote for B. False

The remote backend can work with either a single remote HCP Terraform workspace, or with multiple similarly-named remote workspaces, so B is correct answer

B. prefix switching

The prefix switch is key here: prefix - (Optional) A prefix used in the names of one or more remote workspaces, all of which can be used with this configuration. The full workspace names are used in Terraform Cloud, and the short names (minus the prefix) are used on the command line for Terraform CLI workspaces. If omitted, only the default workspace can be used. This option conflicts with name. To use multiple remote workspaces, set workspaces.prefix to a prefix used in all of the desired remote workspace names. For example, set prefix = "networking-" to use Terraform cloud workspaces with names like networking-dev and networking-prod. This is helpful when mapping multiple Terraform CLI workspaces used in a single Terraform configuration to multiple Terraform Cloud workspaces. The backend configuration requires either name or prefix. Omitting both or setting both results in a configuration error.

https://developer.hashicorp.com/terraform/language/settings/backends/remote "To use multiple remote workspaces, set workspaces.prefix to a prefix used in all of the desired remote workspace names. For example, set prefix = "networking-" to use Terraform cloud workspaces with names like networking-dev and networking-prod. This is helpful when mapping multiple Terraform CLI workspaces used in a single Terraform configuration to multiple Terraform Cloud workspaces."

I am working with GitLab, and I can create multiple instances within a single backend space

Correct B

Your explanation actually states that a remote backend can work with multiple similarly-named remote workspaces (like networking-dev and networking-prod) The answer A would not allow this

correct B https://developer.hashicorp.com/terraform/language/settings/backends/remote#workspaces

B. A remote backend configuration is used to define where the Terraform state is stored, and it can be shared by multiple workspaces, each of which maintains its own separate state.

The remote backend can work with either a single remote Terraform Cloud workspace, or with multiple similarly-named remote workspaces (like networking-dev and networking-prod). The workspaces block of the backend configuration determines which mode it uses: Correct B

B. False