State management

Workspaces enable a single Terraform configuration to manage multiple distinct state files, making it easy to isolate environments like development and production. Option A is incorrect because using multiple workspaces is optional, as Terraform automatically uses a single default workspace if none are created.

Configuring an S3 backend with a DynamoDB table allows teams to store the Terraform state file remotely in S3 while using DynamoDB to prevent concurrent runs via state locking. This setup is designed for state management rather than hosting the Terraform binary or storing application-level database records.

Terraform stores state locally in a 'terraform.tfstate' file by default, but teams should use remote backends like Amazon S3 for secure, shared access and state locking. A diagram for this topic isn't available yet — the worked example below walks the same reasoning step by step.

• !Storing state only locally is risky for teams because it can easily lead to conflicts and overwritten changes.
• !Option A is incorrect because using multiple workspaces is optional, as Terraform automatically uses a single default workspace if none are created.

Answer each from memory — you'll see instantly whether you're right and why.

Run a focused 10-question mini-mock on State management and see it stick.