Question 350
An electric utility network group is working on substation telemetry and critical management routing. The team found that a controller returns HTTP 429 but an automation worker immediately retries in a tight loop. After remediation, which observation is the strongest evidence that this particular fault is resolved?
Explanation
Correct Answer
This evidence directly verifies the scoped correction, honor Retry-After and apply bounded exponential backoff with jitter, for the underlying issue: retry logic disregards rate-limiting headers and backoff. It should be checked against actual device or pipeline output.
Incorrect Answers
This would confirm recovery from an OAuth access token expires midway through a long provisioning transaction, not necessarily from the reported incident. For the specified issue the relevant confirmation is: requests resume at controlled rate and error rates decline in load tests.
This would confirm recovery from a service token can read devices but POST to a change endpoint returns 403, not necessarily from the reported incident. For the specified issue the relevant confirmation is: requests resume at controlled rate and error rates decline in load tests.
This would confirm recovery from an API responds with an ETag but automation overwrites concurrent operator changes, not necessarily from the reported incident. For the specified issue the relevant confirmation is: requests resume at controlled rate and error rates decline in load tests.