Question 1040
A server operations team encounters the following situation: A domain-joined Windows server rejects user logins after its time drifts by eight minutes beyond accepted authentication tolerance. Which sustained operational control best reduces the likelihood of this same issue recurring?
Explanation
Correct Answer
This control targets the underlying recurrence risk: Significant clock skew invalidates time-sensitive domain authentication. It builds validation into the affected workflow and supports the expected recovery result: Domain authentication succeeds and system clocks remain within the required skew.
Incorrect Answers
This control addresses a different scenario: An application consumes increasing memory without workload growth after a library upgrade, eventually invoking the OOM killer. That event's root mechanism was a software memory leak accumulates allocations without releasing them. The described incident instead arises from: Significant clock skew invalidates time-sensitive domain authentication.
This control addresses a different scenario: An application hangs after a configuration change that grants too few file descriptors to its service account, while CPU and storage are otherwise healthy. That event's root mechanism was process resource limits can prevent file or socket creation. The described incident instead arises from: Significant clock skew invalidates time-sensitive domain authentication.
This control addresses a different scenario: A Linux service runs properly when launched as root, but fails under systemd because the restricted service account cannot read its configuration directory. That event's root mechanism was execution context differs between privileged manual testing and managed service startup. The described incident instead arises from: Significant clock skew invalidates time-sensitive domain authentication.