Question 220
At Northgate Telecom, the Linux platform reliability team maintains multi-region Linux gateways and monitoring servers under requirements for stable network connectivity and verified change records. Following a proposed correction, the team checks: A scheduled one-time data repair is accidentally entered as a recurring cron job and executes every morning. Which observed result BEST demonstrates that the correction works?
Explanation
Correct Answer
The repair executes once in the test schedule and no subsequent unexpected run appears in scheduling history. This measurable outcome verifies correction of: A scheduled one-time data repair is accidentally entered as a recurring cron job and executes every morning. The associated technical action is: Use the appropriate one-shot at job or a clearly bounded systemd timer instead of a recurring crontab entry. The Northgate Telecom review checks actual behavior rather than an untested change claim.
Incorrect Answers
A controlled upgrade resolves all required dependencies and the service launches without unmet-library errors. This evidence pertains to an unrelated remediation: Inspect package-manager dependency and version resolution, then align the enabled repositories and compatible package versions. The alternative issue is: An application update fails with broken dependencies because conflicting package versions were pinned across enabled repositories. The current Northgate Telecom problem is: A scheduled one-time data repair is accidentally entered as a recurring cron job and executes every morning. The decisive expected evidence is instead: The repair executes once in the test schedule and no subsequent unexpected run appears in scheduling history.
A deliberate one-byte modification is detected, and an unchanged copy passes the comparison. This evidence pertains to an unrelated remediation: Use a supported byte-level or checksum comparison rather than comparing filenames or timestamps alone. The alternative issue is: A script reports that two files are identical based solely on their filenames, while their content changed after deployment. The current Northgate Telecom problem is: A scheduled one-time data repair is accidentally entered as a recurring cron job and executes every morning. The decisive expected evidence is instead: The repair executes once in the test schedule and no subsequent unexpected run appears in scheduling history.
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 Northgate Telecom problem is: A scheduled one-time data repair is accidentally entered as a recurring cron job and executes every morning. The decisive expected evidence is instead: The repair executes once in the test schedule and no subsequent unexpected run appears in scheduling history.