Get Unlimited Contributor Access to the all ExamTopics Exams!
Take advantage of PDF Files for 1000+ Exams along with community discussions and pass IT Certification Exams Easily.
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
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."
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
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
1) Example using workspaces.name
This example demonstrates the use of a single remote Terraform Cloud workspace by specifying the workspace name.
terraform {
...
workspaces {
name = "networking-prod"
}
}
}
In this configuration, all the Terraform commands will be applied to the networking-prod workspace in Terraform Cloud.
2) Example using workspaces.prefix
This example demonstrates the use of multiple remote Terraform Cloud workspaces that share a common prefix.
terraform {
...
workspaces {
prefix = "networking-"
}
}
}
In this configuration, Terraform commands will apply to any workspace that starts with networking-, such as networking-dev, networking-prod, networking-test, etc. The specific workspace that the commands apply to is determined by the currently selected Terraform CLI workspace. You can switch between workspaces using the terraform workspace select command.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Want to SAVE BIG on Certification Exam Prep?
Zam88
Highly Voted 2 years agoSpandrop
Highly Voted 6 months, 3 weeks ago090200f
Most Recent 2 hours, 27 minutes agoliuyomz
2 months, 2 weeks ago6957dbd
3 months, 4 weeks agoTigerInTheCloud
6 months, 3 weeks agoluxdolorosa
7 months, 3 weeks agoNKSINGH
8 months agoesuarve
9 months, 1 week agoarnabsinha4u
9 months, 3 weeks agoledjo
10 months, 1 week agoparomanu007
10 months, 3 weeks agoJayanth
11 months, 2 weeks agoBere
11 months, 2 weeks agoBusi57
11 months, 2 weeks agoska_torrent_430
1 year agoabhi6199
1 year, 1 month ago