Question 290
While investigating an inventory reconciliation for fictional Thornwick Health Trust, the team reports: Parallel infrastructure pipelines apply conflicting ACL changes because state locking was disabled in a shared backend. What should the engineer change first to resolve this specific issue?
Explanation
Correct Answer
Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. This addresses the problem because terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. Confirm success using: The second apply waits or fails safely on an active lock, and state reflects one consistent resource graph after the approved deployment. Applied here, the relevant facts are: Parallel infrastructure pipelines apply conflicting ACL changes because state locking was disabled in a shared backend. The question asks what should the engineer change first to resolve this specific issue.
Incorrect Answers
The proposed action belongs to the mechanism: an access-token lifecycle and authorization scope are distinct concerns; repeated reuse of expired or insufficient tokens cannot resolve them. Here the stated fault follows a different mechanism: terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. The corrective choice is “Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state”.
The offered action targets: hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. The case facts point instead to: terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. Implement “Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state” to address that specific condition.
The proposed action belongs to the mechanism: model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone. Here the stated fault follows a different mechanism: terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. The corrective choice is “Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state”.