Question 40
At Oakridge Public Services, the IT operations team maintains municipal web and records servers under requirements for safe change approvals and retained activity logs. Following a proposed correction, the team checks: A newly attached USB device is reported missing even though the kernel logged repeated enumeration errors during plug-in. Which observed result BEST demonstrates that the correction works?
Explanation
Correct Answer
The repeated enumeration errors cease and lsusb identifies the device with a usable driver binding. This measurable outcome verifies correction of: A newly attached USB device is reported missing even though the kernel logged repeated enumeration errors during plug-in. The associated technical action is: Inspect dmesg and lsusb events for the specific device and correct the evidenced port, power or driver problem. The Oakridge Public Services review checks actual behavior rather than an untested change claim.
Incorrect Answers
The scheduled test invocation finds the correct executable under an intentionally minimal cron environment. This evidence pertains to an unrelated remediation: Set a controlled PATH or use approved absolute executable paths in the scheduled shell environment. The alternative issue is: A cron-invoked shell command works interactively but fails because its executable directory is missing from the noninteractive PATH. The current Oakridge Public Services problem is: A newly attached USB device is reported missing even though the kernel logged repeated enumeration errors during plug-in. The decisive expected evidence is instead: The repeated enumeration errors cease and lsusb identifies the device with a usable driver binding.
The RAID status reports both members active and a verified test read succeeds after resynchronization. This evidence pertains to an unrelated remediation: Identify the failed member using mdadm and /proc/mdstat, then replace and resynchronize the mirror through the supported procedure. The alternative issue is: A Linux RAID1 member has failed but an administrator replaces the disk without checking mdadm metadata or rebuilding the degraded array. The current Oakridge Public Services problem is: A newly attached USB device is reported missing even though the kernel logged repeated enumeration errors during plug-in. The decisive expected evidence is instead: The repeated enumeration errors cease and lsusb identifies the device with a usable driver binding.
resolvectl or equivalent reports the approved resolver and name lookups continue to work after a reboot. This evidence pertains to an unrelated remediation: Configure the active name-resolution manager's persistent DNS settings instead of repeatedly editing its generated file. The alternative issue is: DNS resolution fails for one Linux server because a manually edited resolv.conf is overwritten by systemd-resolved on restart. The current Oakridge Public Services problem is: A newly attached USB device is reported missing even though the kernel logged repeated enumeration errors during plug-in. The decisive expected evidence is instead: The repeated enumeration errors cease and lsusb identifies the device with a usable driver binding.