Exam Terraform Associate topic 1 question 264 discussion

I would appreciate comments on my thoughts: this would be a case of choose 2 right? A is also not a benefit, right?

Remote state wasn't made for sharing modules because that's module registry's job. :)

Answer: B Terraform remote state stores information about infrastructure resources and does not contain any of the configuration code used to create it.

Saw this on another test engine,, worded slightly different. "The Terraform State file does not contain the actual module code"

It's B. Like another person mentioned, sharing reusable code modules is the module registry's job. https://developer.hashicorp.com/terraform/language/state/remote

https://developer.hashicorp.com/terraform/language/state/remote

The answer is D. Delegate output to other teams. Remote state is a feature of Terraform that allows you to store the state of your infrastructure in a remote location. This can be beneficial for a number of reasons, including: Keeping unencrypted sensitive information off disk Easily sharing reusable code modules Working in a team Enabling version control and auditing However, remote state does not allow you to delegate output to other teams. This is because the state file contains the full state of your infrastructure, including all of the resources that have been created. If you want to delegate output to other teams, you will need to use a different mechanism, such as a configuration management tool or a messaging system.

itssss BBBBBBB!!!!!!

Why not A

The answer B. https://developer.hashicorp.com/terraform/language/state/remote With remote state, Terraform writes the state data to a remote data store, which can then be shared between all members of a team. Remote state allows you to share output values with other configurations. For fully-featured remote backends, Terraform can also use state locking to prevent concurrent runs of Terraform against the same state.