Question 770
A pharmaceutical operations group is working on strict change control for laboratory connectivity. The team found that API tokens appear in the logged request headers during authentication errors. After remediation, which observation is the strongest evidence that this particular fault is resolved?
Explanation
Correct Answer
This evidence directly verifies the scoped correction, redact Authorization headers and secret fields before shipping logs, for the underlying issue: logging serializes full HTTP headers without redaction. It should be checked against actual device or pipeline output.
Incorrect Answers
This would confirm recovery from the automation runner logs changes locally but central operations cannot trace a failed deployment, not necessarily from the reported incident. For the specified issue the relevant confirmation is: controlled failures produce traceable logs with no secret-bearing values.
This would confirm recovery from a monitoring webhook silently loses events after its receiver briefly becomes unavailable, not necessarily from the reported incident. For the specified issue the relevant confirmation is: controlled failures produce traceable logs with no secret-bearing values.
This would confirm recovery from the retention policy deletes required rollback records after two days, not necessarily from the reported incident. For the specified issue the relevant confirmation is: controlled failures produce traceable logs with no secret-bearing values.