Exam Terraform Associate topic 1 question 66 discussion

B. False Backend types: Enhanced Backend – Additional operations like plan, apply, etc. on remote. Standard backend – Simple State file storage and lock facility

The answer is False. Not all standard backend types support state locking and remote operations. The following standard backend types do not support state locking: AzureRM AzureKeyVault Consul Docker Google Cloud Storage Kubernetes MySQL Oracle PostgreSQL Vault The following standard backend types support state locking but not remote operations: AWS S3

Note: In Terraform versions before 1.1.0, we classified backends as standard or enhanced. The enhanced label differentiated the remote backend, which could both store state and perform Terraform operations. This classification has been removed. https://developer.hashicorp.com/terraform/language/settings/backends/configuration another deprecated feature and question..

A. True Explanation: All standard backend types in Terraform support state storage, locking, and remote operations such as plan, apply, and destroy. Terraform backends are responsible for storing the Terraform state file, managing concurrent access to the state, and facilitating collaboration among team members. Different backend types may have additional features or considerations, but these fundamental capabilities are common across all standard backends.

https://digitalvarys.com/complete-terraform-tutorial-part-6-terraform-backends/ its B

Terraform Documentation - Not all backends support locking. The documentation for each backend includes details about whether it supports locking or not.

This question is outdated https://developer.hashicorp.com/terraform/language/settings/backends/configuration : In Terraform versions before 1.1.0, we classified backends as standard or enhanced. The enhanced label differentiated the remote backend, which could both store state and perform Terraform operations. This classification has been removed. " "Some of these backends act like plain remote disks for state files, while others support locking the state while operations are being performed"

AAAAAAAAAAAAA

Answer is B

B. Artefactory is a standard backend and has not locking feature. Also, etcd has not locking feature (only etcdv3).

not all of them so False

https://www.terraform.io/language/settings/backends/configuration "Some of these backends act like plain remote disks for state files, while others support locking the state while operations are being performed. This helps prevent conflicts and inconsistencies. The built-in backends listed are the only backends. You cannot load additional backends as plugins."

Not all backend encrypt , B false = correct

B is correct answer : False. "By default, Terraform uses a backend called local, which stores state as a local file on disk. You can also configure one of the built-in backends listed in the documentation sidebar. Some of these backends act like plain remote disks for state files, while others support locking the state while operations are being performed. This helps prevent conflicts and inconsistencies. The built-in backends listed are the only backends. You cannot load additional backends as plugins." https://www.terraform.io/language/settings/backends/configuration#available-backends

What Backends Do Backends primarily determine where Terraform stores its state. Terraform uses this persisted state data to keep track of the resources it manages. Since it needs the state in order to know which real-world infrastructure objects correspond to the resources in a configuration, everyone working with a given collection of infrastructure resources must be able to access the same state data. By default, Terraform implicitly uses a backend called local to store state as a local file on disk. Every other backend stores state in a remote service of some kind, which allows multiple people to access it. Accessing state in a remote service generally requires some kind of access credentials, since state data contains extremely sensitive information. Some backends act like plain "remote disks" for state files; others support locking the state while operations are being performed, which helps prevent conflicts and inconsistencies.

answer is B

Some backends act like plain "remote disks" for state files; others support locking the state while operations are being performed, which helps prevent conflicts and inconsistencies.