You want to share Terraform state with your team, store it securely, and provide state locking.
How would you do this? (Choose three.)
You want to share Terraform state with your team, store it securely, and provide state locking.
How would you do this? (Choose three.)
Sharing Terraform state securely with your team and providing state locking can be achieved using the following three methods: 1) Using the remote Terraform backend with Terraform Cloud or Terraform Enterprise provides managed services for state storage, access control, and collaboration tools, ensuring secure and efficient state management. 2) Using an S3 Terraform backend with an appropriate IAM policy and the DynamoDB field option configured allows secure storage of state files in an S3 bucket, while using DynamoDB for state locking to prevent concurrent modifications. 3) Using the Consul Terraform backend stores the state file in Consul, a distributed key-value store that supports state locking and secure access controls, offering a reliable solution for team collaboration.
A. Using the remote Terraform backend with Terraform Cloud / Terraform Enterprise. This option allows you to store your Terraform state file securely in a managed service provided by HashiCorp. Terraform Cloud and Terraform Enterprise offer additional features such as access controls, remote execution, and collaboration tools. D. Using an s3 terraform backend with an appropriate IAM policy and dynamodb_field option configured. This option enables you to store your Terraform state file in an Amazon S3 bucket, which provides secure storage with access controls. By configuring an appropriate IAM policy, you can ensure that only authorized users and services can access the state file. Additionally, using the dynamodb_field option allows you to enable state file locking with Amazon DynamoDB, preventing multiple users from concurrently modifying the state. E. Using the consul Terraform backend. This option allows you to store your Terraform state file in a Consul cluster, a distributed key-value store. Consul provides features like access control lists (ACLs) and TLS encryption to help you secure your state file.
A. Using the remote Terraform backend with Terraform Cloud / Terraform Enterprise. D. Using an s3 terraform backend with an appropriate IAM policy and dynamodb_field option configured. E. Using the consul Terraform backend. To share Terraform state with your team, store it securely, and provide state locking, you can use the following options: A. Remote Terraform backend with Terraform Cloud or Terraform Enterprise provides state storage, versioning, locking, and integration with workspaces. D. An S3 backend with an appropriate IAM policy and the dynamodb_field option configured allows you to store your state file in an S3 bucket and use DynamoDB for state locking. E. The Consul Terraform backend enables you to store the state file in Consul, a distributed key-value store, and provides state locking as well.
Dynamo DB flag? I don't think so.
https://developer.hashicorp.com/terraform/language/settings/backends/s3 flag needs to be enabled
It is not C because without dynamo_db enabled, it does not provide state locking
The correct answers are A, D, and E