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?
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
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
The backend that would not work for storing Terraform state files is C. Git. Git is not designed to handle the dynamic state file that Terraform requires for tracking infrastructure. Terraform needs backends that support locking and consistent state management, such as A. Amazon S3, B. Artifactory, or D. Terraform Cloud, which are suitable for remote state storage and ensure safe concurrent access to the state file.
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
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.
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.
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
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.
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.
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.
Reet
Highly Voted 1 year, 3 months agoray320x
5 months, 3 weeks agoTyler2023
1 year agonez15
Highly Voted 2 years, 6 months agoAlgol
Most Recent 2 months, 1 week agoray320x
5 months, 3 weeks agoAbsence379
8 months, 3 weeks agoKLIERKO
1 year, 1 month agogofavad926
1 year, 1 month agoBere
1 year, 3 months agoTlakmini
1 year, 3 months agosumnear
1 year, 3 months agowheelan
1 year, 4 months agokingfighers
7 months, 3 weeks agocedry87
1 year, 7 months agocamps
1 year, 7 months agoArnaldoW
1 year, 7 months agokapara
1 year, 3 months agovadeemkaa
1 year, 11 months agoStiffler1
1 year, 11 months agovikramvlr
1 year, 11 months ago