Question 30
A Linux administrator evaluates: An approved device module was blacklisted and must be enabled only after its compatibility is verified. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (An approved device module was blacklisted and must be enabled only after its compatibility is verified), the acceptance evidence is: The relevant module and required dependencies appear loaded, and the associated device becomes usable without new kernel errors. This verifies the action (Use modprobe and module metadata to load or remove a supported kernel module with dependency resolution, checking lsmod and kernel logs afterward.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Directly inserting a module file without resolving its dependencies may fail or leave a driver nonfunctional.
The observed Linux condition is: An approved device module was blacklisted and must be enabled only after its compatibility is verified. The recommended direct administrative response is: Use modprobe and module metadata to load or remove a supported kernel module with dependency resolution, checking lsmod and kernel logs afterward. The relevant failure or security risk is: Directly inserting a module file without resolving its dependencies may fail or leave a driver nonfunctional. Validate success with: The relevant module and required dependencies appear loaded, and the associated device becomes usable without new kernel errors.
Incorrect Answers
GRUB kernel boot parameter recovery (1.1) addresses another technical failure: An incorrect kernel or root filesystem parameter can stop the host before its normal init process starts. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: The relevant module and required dependencies appear loaded, and the associated device becomes usable without new kernel errors.
Filesystem Hierarchy Standard paths (1.1) would demonstrate or implement: Inspection shows persistent settings in /etc and expected service state or logs in appropriate paths such as /var or /run. This case instead tests Kernel module dependencies with modprobe; the choice measures or changes another part of the system.
Software RAID health and rebuild with mdadm (1.3) would demonstrate or implement: Replacing the wrong disk or trusting a degraded mirror without monitoring rebuild can cause avoidable data loss. The required paired action and test concerns Kernel module dependencies with modprobe; a passing result for this alternative could leave that requirement unresolved.