Question 280
At Keystone BioLabs, the Linux security team maintains research compute and private lab hosts under requirements for protected datasets and observable system behavior. Following a proposed correction, the team checks: A slow boot is blamed on CPU saturation, but no one checks which unit actually delayed the system reaching its normal target. Which observed result BEST demonstrates that the correction works?
Explanation
Correct Answer
The revised boot trace identifies the corrected bottleneck and the intended target completes within the measured deadline. This measurable outcome verifies correction of: A slow boot is blamed on CPU saturation, but no one checks which unit actually delayed the system reaching its normal target. The associated technical action is: Use systemd-analyze critical-chain and blame results to identify the actual startup dependency before changing unit ordering. The Keystone BioLabs review checks actual behavior rather than an untested change claim.
Incorrect Answers
The account reports the approved expiry and a login after the test expiry is rejected without deleting historical files. This evidence pertains to an unrelated remediation: Set the account expiration using chage or the distribution-supported account tool and preserve an audit record of the change. The alternative issue is: A contractor retains login access after the agreed end date because the account expiration field was never applied. The current Keystone BioLabs problem is: A slow boot is blamed on CPU saturation, but no one checks which unit actually delayed the system reaching its normal target. The decisive expected evidence is instead: The revised boot trace identifies the corrected bottleneck and the intended target completes within the measured deadline.
The upgraded service retains the intended settings and the configuration diff clearly records the final values. This evidence pertains to an unrelated remediation: Use the package manager's supported configuration-file handling and preserve reviewed changes or a maintained drop-in file. The alternative issue is: A distribution upgrade replaces a locally edited service configuration without an archived copy or recorded diff. The current Keystone BioLabs problem is: A slow boot is blamed on CPU saturation, but no one checks which unit actually delayed the system reaching its normal target. The decisive expected evidence is instead: The revised boot trace identifies the corrected bottleneck and the intended target completes within the measured deadline.
A package query selects the approved production repository and an attempted untrusted build is not installed. This evidence pertains to an unrelated remediation: Disable the unapproved repository and enforce the documented trusted package source priorities and exclusions. The alternative issue is: A production server installs software from a development repository because a temporary package source remains enabled after testing. The current Keystone BioLabs problem is: A slow boot is blamed on CPU saturation, but no one checks which unit actually delayed the system reaching its normal target. The decisive expected evidence is instead: The revised boot trace identifies the corrected bottleneck and the intended target completes within the measured deadline.