Question 230
In a Linux incident, an engineer reports: A machine's boot partition is on an encrypted device but early userspace lacks unlock integration. What is the correct interpretation?
Explanation
Correct Answer
A correct LUKS passphrase is insufficient if boot cannot prompt or find the mapper. This mechanism fits the stated evidence. Validate it by checking that the encrypted root unlocks during normal boot.
Incorrect Answers
The alternative describes a raw partition without a recognized filesystem cannot mount as existing data, which is relevant when a disk appears in lsblk but mounts fail with unknown filesystem type. It does not explain this case because a correct LUKS passphrase is insufficient if boot cannot prompt or find the mapper.
It would account for a storage upgrade leaves /boot full and a new kernel installation fails, not the current evidence. For this incident, a correct LUKS passphrase is insufficient if boot cannot prompt or find the mapper; the alternative mechanism leaves that distinction unexplained.
A stale boot menu cannot load a nonexistent kernel. That can explain why a GRUB update left a boot entry pointing to a kernel image that was removed, whereas the current evidence supports boot-time decryption requires initramfs support and valid crypttab or equivalent integration.





CompTIA Linux+ (XK0-006) Practice Tests