Local state behavior in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does Terraform local state behave after resource deletion?

Consider a Terraform configuration where a resource is created and then manually deleted outside Terraform (e.g., via cloud console). What will Terraform's local state file reflect after this manual deletion?

A The local state still shows the resource as existing until you run 'terraform refresh' or 'terraform apply'.

B The local state automatically updates and removes the resource immediately after manual deletion.

C Terraform local state deletes the resource entry only after running 'terraform destroy'.

D Terraform local state never tracks resource existence and only stores configuration.

💡 Hint

Think about how Terraform tracks resources and when it updates its local state file.

Terraform's local state file keeps track of resources it manages. If a resource is deleted outside Terraform, the local state still shows it as existing until you run 'terraform refresh' or 'terraform apply', which updates the state to match reality.

❓ Architecture

intermediate

What happens to local state when multiple users run Terraform independently?

Two team members run Terraform commands independently on the same infrastructure but on their own local machines using local state files. What is the likely outcome?

A Terraform automatically merges local state files from different users to keep them consistent.

B Terraform locks the infrastructure to prevent multiple users from running commands simultaneously.

C Local state files are shared automatically via cloud provider APIs to avoid conflicts.

D Each local state file may become out of sync, causing conflicts and potential resource duplication or deletion.

💡 Hint

Consider how local state files are stored and shared.

Local state files are stored on each user's machine and are not shared. Running Terraform independently can cause state drift and conflicts because each user has their own view of the infrastructure.

❓ Configuration

advanced

What error occurs when Terraform local state file is corrupted?

After a failed Terraform operation, the local state file becomes corrupted. What error message will Terraform most likely show when you try to run 'terraform plan'?

A Error: Terraform configuration syntax error

B Error: Failed to load state: invalid character '<' looking for beginning of value

C Error: No changes. Infrastructure is up-to-date

D Error: Resource not found in cloud provider

💡 Hint

Think about what happens if the state file content is unreadable or malformed JSON.

If the local state file is corrupted or contains invalid JSON, Terraform will fail to parse it and show an error indicating invalid characters or failure to load state.

❓ security

advanced

What is a security risk of storing Terraform local state on a shared network drive?

Storing Terraform local state files on a shared network drive accessible by multiple users can cause which security risk?

A Unauthorized users may access sensitive data like passwords or keys stored in the state file.

B Terraform will automatically encrypt the state file, so no risk exists.

C Storing state on a shared drive improves security by centralizing access control.

D The state file will be deleted automatically after each run to prevent leaks.

💡 Hint

Consider what kind of data Terraform state files contain.

Terraform state files often contain sensitive information such as resource IDs, IP addresses, and sometimes secrets. Storing them on a shared drive without proper access controls risks unauthorized data exposure.

✅ Best Practice

expert

Which approach best prevents local state conflicts in a team environment?

Your team manages infrastructure with Terraform. To avoid local state conflicts and ensure consistent state, which approach is best?

A Disable state locking and rely on manual communication to avoid conflicts.

B Each user keeps their own local state file and manually merges changes.

C Use a remote state backend like Terraform Cloud or S3 with state locking enabled.

D Store local state files on a shared network drive without locking.

💡 Hint

Think about how to share state safely and avoid conflicts.

Using a remote state backend with locking ensures only one user can modify state at a time, preventing conflicts and keeping state consistent across the team.