Which backend feature enables sharing state and applying state operations remotely?

• A. Local state
• B. State locking
• C. Remote state
• D. Version control

Answer: (C)

Backends determine where Terraform stores its state and how operations run. Using a remote backend places the state file in a centralized, shareable location (such as S3, GCS, Azure Blob, Consul, or Terraform Cloud), so multiple people and machines can access the same state and run plan/apply against it. This is what enables collaboration and remote execution of state operations, without needing the state to live only on a single local machine. Local state keeps the state on your own machine, while version control stores only configuration code, not the live state. State locking is a helpful safeguard that remote backends often provide, but the core enabler of sharing and remote execution here is the remote state itself.