Question 370
During a remote branch provisioning pilot at fictional Northshore Cloud, the change record states: Two automation jobs modify the same Cisco network resource inventory from separate local Terraform state files, each unaware of the other's last apply. Which result most directly verifies that the proposed correction worked?
Explanation
Correct Answer
The second apply waits or fails safely on an active lock, and state reflects one consistent resource graph after the approved deployment. This directly verifies the related correction: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. It checks the technical distinction: Terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. Applied here, the relevant facts are: Two automation jobs modify the same Cisco network resource inventory from separate local Terraform state files, each unaware of the other's last apply. The question asks which result most directly verifies that the proposed correction worked.
Incorrect Answers
This alternative is a response to another technical cause: This directly verifies the related correction: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. The reported case instead depends on: This directly verifies the related correction: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. The action that directly addresses it is “The second apply waits or fails safely on an active lock, and state reflects one consistent resource graph after the approved deployment”.
The proposed action belongs to the mechanism: This directly verifies the related correction: Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely. Here the stated fault follows a different mechanism: This directly verifies the related correction: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. The corrective choice is “The second apply waits or fails safely on an active lock, and state reflects one consistent resource graph after the approved deployment”.
The offered action targets: This directly verifies the related correction: Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models. The case facts point instead to: This directly verifies the related correction: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. Implement “The second apply waits or fails safely on an active lock, and state reflects one consistent resource graph after the approved deployment” to address that specific condition.