Question 250
At Harborline Logistics, the platform infrastructure team maintains shipment scanning and routing Linux services under requirements for reliable processing and attributable maintenance. Following a proposed correction, the team checks: A time-sensitive service drifts by several seconds because its NTP synchronization daemon is installed but never enabled or configured. Which observed result BEST demonstrates that the correction works?
Explanation
Correct Answer
The host reports synchronization with the approved source and measured clock offset returns to the permitted bound. This measurable outcome verifies correction of: A time-sensitive service drifts by several seconds because its NTP synchronization daemon is installed but never enabled or configured. The associated technical action is: Configure an approved time source and the supported NTP client or service with persistent startup settings. The Harborline Logistics review checks actual behavior rather than an untested change claim.
Incorrect Answers
A test account inherits the intended safe skeleton files without receiving another user's secrets. This evidence pertains to an unrelated remediation: Repair /etc/skel template content and permissions before creating new user accounts through the standard process. The alternative issue is: A newly created account has insecure default files because the template directory contains broadly readable credential material. The current Harborline Logistics problem is: A time-sensitive service drifts by several seconds because its NTP synchronization daemon is installed but never enabled or configured. The decisive expected evidence is instead: The host reports synchronization with the approved source and measured clock offset returns to the permitted bound.
The revised boot trace identifies the corrected bottleneck and the intended target completes within the measured deadline. This evidence pertains to an unrelated remediation: Use systemd-analyze critical-chain and blame results to identify the actual startup dependency before changing unit ordering. The alternative issue is: A slow boot is blamed on CPU saturation, but no one checks which unit actually delayed the system reaching its normal target. The current Harborline Logistics problem is: A time-sensitive service drifts by several seconds because its NTP synchronization daemon is installed but never enabled or configured. The decisive expected evidence is instead: The host reports synchronization with the approved source and measured clock offset returns to the permitted bound.
After a simulated slow mount the service starts only when its dependency is ready and no premature failure loop occurs. This evidence pertains to an unrelated remediation: Add appropriate systemd ordering and requirement dependencies on the required mount or network-online target. The alternative issue is: A Linux service repeatedly restarts despite a required dependent network mount being unavailable at startup. The current Harborline Logistics problem is: A time-sensitive service drifts by several seconds because its NTP synchronization daemon is installed but never enabled or configured. The decisive expected evidence is instead: The host reports synchronization with the approved source and measured clock offset returns to the permitted bound.