Your DevOps team is currently using the local backend for your Terraform configuration. You would like to move to a remote backend to begin storing the state file in a central location.
Which of the following backends would not work?
Your DevOps team is currently using the local backend for your Terraform configuration. You would like to move to a remote backend to begin storing the state file in a central location.
Which of the following backends would not work?
Among the given options, Git would not work as a remote backend for Terraform state files. Terraform supports remote backends like Amazon S3 and Terraform Cloud, but Git is not designed for state management due to a lack of necessary features such as state locking and concurrent access handling.
Note: We removed the artifactory, etcd, etcdv3, manta, and swift backends in Terraform v1.3. Information about their behavior in older versions is still available in the Terraform v1.2 documentation. For migration paths from these removed backends, refer to Upgrading to Terraform v1.3. https://developer.hashicorp.com/terraform/language/settings/backends/configuration#available-backends
Thanks for this, as I question why artifactory
With the removal of support for Artifactory in Terraform v1.3 and Git never being a supported backend, both options B and C would not work. However, Git has never been a supported backend for Terraform state files, making it the primary correct answer. The correct answer is: C. Git
https://www.terraform.io/cdktf/concepts/remote-backends
If Everyone knows, that the answer is C why didn't the admin fix it yet?
I believe the administrator is aware of the solution. However, if they merely provide us with answers without encouraging exploration, individuals might resort to memorizing the responses. This could potentially lead to a situation where the company detects and takes action against the website for distributing exam dumps. It's essential for learning and growth that we understand concepts thoroughly through exploration rather than relying solely on pre-supplied answers.
Supported backends: https://developer.hashicorp.com/terraform/cdktf/concepts/remote-backends#supported-backends Git is not a supported backend for Terraform state. While it's possible to store state files in Git, doing so is not recommended because state files can contain sensitive information, and it's not designed for concurrent state management.
Why is answer showing A as the correct answer. C is the answer for sure
C. Git. Git is not a suitable remote backend for Terraform. While it is possible to store Terraform state files in Git, it is not recommended because Git is not designed to manage state files and does not provide the necessary locking mechanisms to prevent concurrent access.
Answer is B. I am using Git as a backend. Artifactory is no longer a valid backend. https://developer.hashicorp.com/terraform/language/settings/backends/configuration#available-backends
git is not official support now, check the doc: https://developer.hashicorp.com/terraform/language/settings/backends/local
https://developer.hashicorp.com/terraform/language/settings/backends/configuration#available-backends
"C" for sure.
Answer is C - Git is not supported to do the remote backend operation
Answer C - Git cannot be used as a backend
answer : B
C is the answer
C. git is not supported
The anwer is C stop kliering
B Note: We removed the artifactory, etcd, etcdv3, manta, and swift backends in Terraform v1.3. Information about their behavior in older versions is still available in the Terraform v1.2 documentation. For migration paths from these removed backends, refer to Upgrading to Terraform v1.3.
With the removal of support for Artifactory in Terraform v1.3 and Git never being a supported backend, both options B and C would not work. However, Git has never been a supported backend for Terraform state files, making it the primary correct answer. The correct answer is: C. Git