Question 360
A server operations team encounters the following situation: An administrator rotates a Linux service log by renaming its file while the daemon continues writing to the old inode and disk space never frees. Which sustained operational control best reduces the likelihood of this same issue recurring?
Explanation
Correct Answer
This control targets the underlying recurrence risk: The process retains an open file handle after a path-level rotation. It builds validation into the affected workflow and supports the expected recovery result: After rotation the service writes to the active log and old space is reclaimed.
Incorrect Answers
This control addresses a different scenario: A remote management dashboard reports a web service as healthy because the TCP port is open although the application returns HTTP 500 errors. That event's root mechanism was transport listener status is not an end-to-end application functionality check. The described incident instead arises from: The process retains an open file handle after a path-level rotation.
This control addresses a different scenario: An application service uses a shared account with no identity attribution in its event logs, obscuring which scheduled integration changed a record. That event's root mechanism was shared credentials eliminate reliable accountability for service operations. The described incident instead arises from: The process retains an open file handle after a path-level rotation.
This control addresses a different scenario: A server's monitoring agent polls every five minutes and misses short CPU saturation bursts that time out API requests. That event's root mechanism was coarse averages hide short resource bottlenecks. The described incident instead arises from: The process retains an open file handle after a path-level rotation.