Which of the following is not a benefit of remote state?

• A. Keeping unencrypted sensitive information off disk
• B. Easily share reusable code modules
• C. Working in a team
• D. Delegate output to other teams

Answer: (B)

Remote state backends centralize Terraform state so teams can coordinate changes and work from a single source of truth. This setup enables collaboration by keeping the state in one place and often providing locking to prevent concurrent updates. It also helps protect sensitive data by not storing the state locally on each developer’s machine, especially when the backend enforces encryption at rest and in transit. Outputs in the remote state can be consumed by other teams or automation pipelines, aiding handoffs and integration.

Sharing reusable code modules, however, is not a benefit provided by remote state. Modules are shared through registries or direct module sources, not via the state backend.