Question 1080
A server operations team encounters the following situation: A Linux service runs properly when launched as root, but fails under systemd because the restricted service account cannot read its configuration directory. Which sustained operational control best reduces the likelihood of this same issue recurring?
Explanation
Correct Answer
This control targets the underlying recurrence risk: Execution context differs between privileged manual testing and managed service startup. It builds validation into the affected workflow and supports the expected recovery result: The service starts via systemd without running as root.
Incorrect Answers
This control addresses a different scenario: A Windows Server feature was removed by Group Policy but a dependent scheduled task continues trying to invoke its binary and logs recurring failures. That event's root mechanism was retired application components still have active automation dependencies. The described incident instead arises from: Execution context differs between privileged manual testing and managed service startup.
This control addresses a different scenario: A system update fills the root filesystem with package cache files and prevents syslog from writing, making the host appear frozen. That event's root mechanism was insufficient system volume space blocks processes needing new writes. The described incident instead arises from: Execution context differs between privileged manual testing and managed service startup.
This control addresses a different scenario: A file server rejects access to a newly created share because permissions were granted only at the share layer and NTFS ACLs still deny users. That event's root mechanism was effective access depends on overlapping share and filesystem restrictions. The described incident instead arises from: Execution context differs between privileged manual testing and managed service startup.