Question 270
At Bluehaven Transit, the operations engineering team maintains rail scheduling application servers under requirements for bounded incidents and careful patch windows. The acceptance reviewer must validate: A security-sensitive daemon is merely disabled at boot but an operator can still start it through a dependency or manual systemctl command. Which observed result BEST demonstrates that the correction works?
Explanation
Correct Answer
A controlled activation request fails while masked and succeeds only after the authorized unit is unmasked. This measurable outcome verifies correction of: A security-sensitive daemon is merely disabled at boot but an operator can still start it through a dependency or manual systemctl command. The associated technical action is: Mask the unit where policy requires preventing activation, documenting and testing controlled unmask recovery. The Bluehaven Transit review checks actual behavior rather than an untested change claim.
Incorrect Answers
The container can write within its authorized mounted directory and a separate forbidden host path remains inaccessible. This evidence pertains to an unrelated remediation: Apply an appropriate supported SELinux volume-label option and host ownership for the rootless container without disabling SELinux globally. The alternative issue is: A rootless Podman container fails to write to a bind-mounted SELinux-enforcing host directory despite ordinary Unix permissions being correct. The current Bluehaven Transit problem is: A security-sensitive daemon is merely disabled at boot but an operator can still start it through a dependency or manual systemctl command. The decisive expected evidence is instead: A controlled activation request fails while masked and succeeds only after the authorized unit is unmasked.
The service flushes pending work, exits with a recorded graceful status and restarts without data inconsistency. This evidence pertains to an unrelated remediation: Send a graceful TERM signal and allow the documented drain interval, escalating only if the process cannot exit safely. The alternative issue is: A production worker ignores a graceful shutdown command because the operator sends SIGKILL immediately and leaves partially written data. The current Bluehaven Transit problem is: A security-sensitive daemon is merely disabled at boot but an operator can still start it through a dependency or manual systemctl command. The decisive expected evidence is instead: A controlled activation request fails while masked and succeeds only after the authorized unit is unmasked.
A controlled newly created file appears in the live search and the indexed query behaves as expected after refresh. This evidence pertains to an unrelated remediation: Use find for a live filesystem search or refresh the locate index through the approved distribution mechanism. The alternative issue is: A report cannot locate recently created files because the locate database has not been refreshed since deployment. The current Bluehaven Transit problem is: A security-sensitive daemon is merely disabled at boot but an operator can still start it through a dependency or manual systemctl command. The decisive expected evidence is instead: A controlled activation request fails while masked and succeeds only after the authorized unit is unmasked.