What is the first step to recover from a stuck state lock?

Run terraform force-unlock with the lock ID

Wait for the lock to expire automatically

Run terraform init to reset the backend

Delete the state file and re-import resources

You are troubleshooting a Terraform state lock issue. The error message indicates that the lock is held by a process with a specific ID. You have confirmed that no team member is running Terraform. However, you are unsure if the lock is stale or if it is held by a legitimate process that you cannot see. What is the safest course of action?

Investigate the lock ID to determine if it corresponds to a known process or a stale lock from a crashed operation.

Wait for a few minutes to see if the lock is released automatically.

Run `terraform force-unlock` immediately to release the lock and proceed.

Delete the state file and recreate it from scratch.

Your team is migrating from a local backend to a remote backend. You need to ensure that state locking is supported to prevent concurrent modifications. You are considering two options: the `s3` backend with DynamoDB and the `consul` backend. What is a key difference in how these two backends handle locking?

The Consul backend supports locking, but the S3 backend does not.

The S3 backend supports locking, but the Consul backend does not.

The S3 backend uses a separate DynamoDB table for locks, while the Consul backend uses a key-value entry in the Consul cluster.

Both backends use the same mechanism for locking, which is a file in the state storage.

HashiCorp Certified:Terraform Associate

Domain 6Objective 2

6b Describe State Locking TERRAFORM-ASSOCIATE-004 Practice Questions (Page 4)

Part of the Terraform state management domain, which makes up ~10% of our current practice bank. HashiCorp does not publish an official question count, but from its 60-minute exam (~25–40 total, ~3–4 in this domain), expect 1–1 from this objective — we provide 19 practice questions to prepare you well beyond it. (estimate)

19questions here

4free pages

5concepts

Questions 16–19

16foundation · easy
Which backend does NOT support state locking?
Select an answer first
17foundation · easy
What is the first step to recover from a stuck state lock?
Select an answer first
18expert · hard
You are troubleshooting a Terraform state lock issue. The error message indicates that the lock is held by a process with a specific ID. You have confirmed that no team member is running Terraform. However, you are unsure if the lock is stale or if it is held by a legitimate process that you cannot see. What is the safest course of action?
Select an answer first
19expert · hard
Your team is migrating from a local backend to a remote backend. You need to ensure that state locking is supported to prevent concurrent modifications. You are considering two options: the `s3` backend with DynamoDB and the `consul` backend. What is a key difference in how these two backends handle locking?
Select an answer first

Finished these 4 questions?

Review the revealed explanations, or continue through the curriculum.

No more pagesBack to TERRAFORM-ASSOCIATE-004

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by HashiCorp. “TERRAFORM-ASSOCIATE-004” is a trademark of its owner, used for identification only.

6b Describe State Locking TERRAFORM-ASSOCIATE-004 Practice Questions (Page 4)

Questions 16–19

Which backend does NOT support state locking?

What is the first step to recover from a stuck state lock?

Keep studying — Terraform state management