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

Questions 6–10

1. 6application · medium

   You are running `terraform plan` against a remote backend that supports locking. Another engineer is currently running `terraform apply` on the same state. What will happen when your `terraform plan` command executes?

   • AYour plan will fail with a lock error, and you will need to wait for the other engineer's apply to complete.
   • BYour plan will run, and it will overwrite the other engineer's lock.
   • CYour plan will run successfully because `terraform plan` does not acquire a lock.
   • DYour plan will run, but it will use a cached copy of the state from your local machine.
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   What is the primary purpose of state locking in Terraform?

   • ATo speed up Terraform operations by caching state
   • BTo prevent concurrent modifications that could corrupt the state file
   • CTo encrypt the state file at rest
   • DTo automatically resolve merge conflicts in state
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   What information does the terraform force-unlock command require?

   • AThe workspace name
   • BThe backend type
   • CThe lock ID
   • DThe name of the state file
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   When should you use the terraform force-unlock command?

   • AWhen you want to change the backend configuration
   • BWhen you want to prevent other users from running operations
   • CWhen a previous operation crashed and left a stale lock
   • DWhen you need to delete the state file
   Reveal Solution Discussion Select an answer first
6. 10expert · hard

   Your team uses an S3 backend with DynamoDB for locking. You notice that `terraform plan` is failing with a lock error, but you can see in the DynamoDB table that there is no lock item present. What is the most likely explanation for this behavior?

   • AThe lock item was created and then deleted by a previous operation, but the lock is still considered held.
   • BThe lock item exists but is not visible due to DynamoDB's eventual consistency.
   • CThe DynamoDB table is not configured correctly, so Terraform cannot acquire a lock.
   • DThe lock is held by another process that is not using the same DynamoDB table.
   Reveal Solution Discussion Select an answer first