Which concept describes where Terraform stores the state and how it's locked?

• A. State locking
• B. Version control
• C. Backend types
• D. Provider constraints

Answer: (C)

Backend types define where Terraform stores its state and how locking is managed. The state is the source of truth for your infrastructure, and you can keep it locally with a local backend or remotely with a remote backend (such as cloud storage). Remote backends not only store the state but also provide locking to prevent concurrent writes, which helps avoid corruption when multiple people or processes apply changes at the same time. Different backends offer different locking mechanisms or requirements, like using a DynamoDB table with S3 for safe locking.

State locking by itself describes the protection mechanism, but it’s the backend that governs both storage location and how locking is implemented. Version control is about tracking code changes and is not used to manage Terraform state, and provider constraints specify which provider versions are allowed, not how state is stored or locked. Together, this makes backend types the correct concept for describing where the state lives and how it is locked.