CompTIA XK0-006 (CompTIA Linux+) Practice Test 60

Question 590

A filesystem is reported read-only after I/O errors even though fstab specifies rw. What is the likely protective response?

  1. Container writable-layer or quota capacity
  2. Offline filesystem consistency check after backup
  3. Failing storage hardware
  4. Kernel remounted filesystem read-only after errors
  5. NFS server or network path availability

Explanation

Correct Answer

D:

Some filesystems remount read-only after serious consistency or storage faults. The underlying device and filesystem need diagnosis before forcing writes.

Incorrect Answers

A:

A container's storage driver or configured filesystem quota can limit writes independently of other host mounts; the administrator instead needs explaining an unexpected read-only remount; this option serves a different purpose.

B:

Repair tools may alter filesystem structures, so preserve data and unmount the affected filesystem first; it answers a neighboring question rather than explaining an unexpected read-only remount.

C:

Increasing device errors and sector remapping suggest media degradation; that changes a different part of the system; the requested outcome is explaining an unexpected read-only remount.

E:

A hard network mount can wait on unavailable remote I/O; it will not provide explaining an unexpected read-only remount under these conditions.

Question 591

The server will not power on and no local keyboard response appears, but the BMC is reachable. What is a sensible next diagnostic?

  1. Missing or failed kernel driver module
  2. Inspect BMC power and hardware sensor events
  3. Controller driver binding and dmesg errors
  4. Nested virtualization exposure

Explanation

Correct Answer

B:

Out-of-band management can report chassis power, thermal and hardware faults even when the OS is unavailable. It is more relevant than checking sshd.

Incorrect Answers

A:

A changed kernel or module package can leave a controller without its expected driver; using it would leave diagnosing physical power state outside the OS unresolved.

C:

PCI enumeration proves the hardware is discovered, not that a driver has initialized attached storage; it does not deliver diagnosing physical power state outside the OS, which is decisive in this scenario.

D:

Guests need virtualization extensions exposed by the host hypervisor to run nested accelerated VMs; the evidence calls for diagnosing physical power state outside the OS, not merely this separate operation.

Question 592

A Linux server fails to mount its root filesystem after migrating to new storage. The team should verify both the root identifier in boot arguments and early-boot access to the required storage driver. Which TWO checks matter? Choose TWO.

  1. Actual filesystem UUIDs against the root boot argument
  2. /etc/fstab entry for /data
  3. Initramfs with the needed storage module
  4. Incorrect GRUB boot-path references
  5. Boot the prior known-good kernel

Explanation

Correct Answers

A:

A stale UUID can point to a nonexistent root volume. Matching boot parameters to the installed filesystems resolves the mismatch.

C:

A driver stored only on the unavailable root filesystem cannot be loaded in time to mount that filesystem. The initramfs must already include the necessary storage support, alongside a correct root-device identifier.

Incorrect Answers

B:

Incorrect identifiers, mount types or required mounts can push boot into emergency mode; that is not equivalent to checking the root reference and early storage-driver availability.

D:

The bootloader may no longer find its modules or configuration after a partition change; it answers a neighboring question rather than checking the root reference and early storage-driver availability.

E:

A working older kernel isolates the regression and restores service without immediately rebuilding disks; that changes a different part of the system; the requested outcome is checking the root reference and early storage-driver availability.

Question 593

A new USB peripheral appears in lsusb but its application cannot communicate with it. What should be checked next?

  1. Driver binding and /dev node permissions
  2. Inspect BMC power and hardware sensor events
  3. CPU, memory, or platform hardware fault
  4. Cooling, airflow and fan health

Explanation

Correct Answer

A:

USB enumeration confirms discovery but not successful driver operation or user access. Kernel logs and device-node attributes help isolate the failure.

Incorrect Answers

B:

Out-of-band management can report chassis power, thermal and hardware faults even when the OS is unavailable; it will not provide separating USB discovery from device usability under these conditions.

C:

Machine-check records can report low-level hardware errors rather than application exceptions; using it would leave separating USB discovery from device usability unresolved.

D:

Thermal throttling reduces frequency to protect silicon; the requirement is separating USB discovery from device usability, outside the effect of this choice.

Question 594

A thermal monitor reports CPUs throttling as temperature rises under load. What should be verified first?

  1. CPU, memory, or platform hardware fault
  2. Driver binding and /dev node permissions
  3. Cooling, airflow and fan health
  4. Inspect BMC power and hardware sensor events

Explanation

Correct Answer

C:

Thermal throttling reduces frequency to protect silicon. Check actual sensor values and cooling before tuning scheduler priorities.

Incorrect Answers

A:

Machine-check records can report low-level hardware errors rather than application exceptions; the evidence calls for resolving CPU frequency throttling from heat, not merely this separate operation.

B:

USB enumeration confirms discovery but not successful driver operation or user access; the task involves resolving CPU frequency throttling from heat, whereas this addresses another subsystem.

D:

Out-of-band management can report chassis power, thermal and hardware faults even when the OS is unavailable; that is not equivalent to resolving CPU frequency throttling from heat.

Question 595

An application was terminated unexpectedly and the kernel journal records out of memory: Killed process. Which subsystem acted?

  1. Installed shared libraries and dynamic loader paths
  2. User= identity in the service unit
  3. Service shutdown handler and TimeoutStopSec
  4. Linux out-of-memory killer

Explanation

Correct Answer

D:

The OOM killer selects processes when memory reclaim cannot meet allocations under policy and cgroup limits. Its log identifies the victim and memory context.

Incorrect Answers

A:

The executable cannot start when a required shared object cannot be located or loaded; it answers a neighboring question rather than attributing unexpected process death to OOM protection.

B:

Systemd switches to the configured identity before starting a process; that changes a different part of the system; the requested outcome is attributing unexpected process death to OOM protection.

C:

Slow cleanup or a stuck process can exceed systemd's grace period; this does not achieve attributing unexpected process death to OOM protection on the system described.

Question 596

The application reports disk full only inside a container, while host df reports plenty of space. Which layer should be inspected?

  1. Grow the filesystem on the extended LV
  2. Create a supported filesystem before mounting
  3. Container writable-layer or quota capacity
  4. Verify md array state and replace the failed member
  5. NFS server or network path availability

Explanation

Correct Answer

C:

A container's storage driver or configured filesystem quota can limit writes independently of other host mounts. Check the container's relevant mount and upper layer.

Incorrect Answers

A:

Increasing the LVM block device does not always resize the filesystem; the requirement is finding container-specific storage capacity limits, outside the effect of this choice.

B:

A block device with no recognized filesystem cannot be mounted as ext4 or XFS until formatted appropriately; it does not deliver finding container-specific storage capacity limits, which is decisive in this scenario.

D:

RAID1 can remain active in degraded mode while mirror redundancy is lost; the task involves finding container-specific storage capacity limits, whereas this addresses another subsystem.

E:

A hard network mount can wait on unavailable remote I/O; its scope differs from finding container-specific storage capacity limits, so it cannot meet the stated requirement.

Question 597

GRUB displays a rescue prompt after the boot partition was moved, but Linux filesystems remain intact. Which root cause is likely?

  1. Different PATH and execution environment
  2. Incorrect GRUB boot-path references
  3. Last kernel console messages and panic context
  4. /etc/fstab entry for /data

Explanation

Correct Answer

B:

The bootloader may no longer find its modules or configuration after a partition change. Correcting boot references is safer than reformatting intact data.

Incorrect Answers

A:

Systemd services receive a controlled environment that may omit interactive profile additions; that is not equivalent to repairing loader references after partition changes.

C:

Panic logs, call traces and boot parameters narrow the failing driver or subsystem; it answers a neighboring question rather than repairing loader references after partition changes.

D:

Incorrect identifiers, mount types or required mounts can push boot into emergency mode; that changes a different part of the system; the requested outcome is repairing loader references after partition changes.

Question 598

A mounted directory suddenly displays underlying empty files after a storage mount fails. What mechanism explains the difference?

  1. Processes holding files or working directories on the mount
  2. Offline filesystem consistency check after backup
  3. Failing storage hardware
  4. Grow the filesystem on the extended LV
  5. Mount point hides its underlying directory contents when active
  6. Create a supported filesystem before mounting

Explanation

Correct Answer

E:

Mounting a filesystem overlays the directory used as a mount point. If the mount is absent, the original underlying files are visible instead.

Incorrect Answers

A:

Open file descriptors and current working directories can keep a filesystem busy; it will not provide distinguishing mount content from underlying directory content under these conditions.

B:

Repair tools may alter filesystem structures, so preserve data and unmount the affected filesystem first; using it would leave distinguishing mount content from underlying directory content unresolved.

C:

Increasing device errors and sector remapping suggest media degradation; the requirement is distinguishing mount content from underlying directory content, outside the effect of this choice.

D:

Increasing the LVM block device does not always resize the filesystem; it does not deliver distinguishing mount content from underlying directory content, which is decisive in this scenario.

F:

A block device with no recognized filesystem cannot be mounted as ext4 or XFS until formatted appropriately; the task involves distinguishing mount content from underlying directory content, whereas this addresses another subsystem.

Question 599

A Linux host enters emergency mode because /data cannot be mounted, but the root filesystem is healthy. What should be checked first?

  1. Boot the prior known-good kernel
  2. /etc/fstab entry for /data
  3. Actual filesystem UUIDs against the root boot argument
  4. Hard dependency on an unavailable network mount

Explanation

Correct Answer

B:

Incorrect identifiers, mount types or required mounts can push boot into emergency mode. Inspecting the named entry and systemd journal narrows the failure.

Incorrect Answers

A:

A working older kernel isolates the regression and restores service without immediately rebuilding disks; the task involves identifying a non-root mount that breaks startup, whereas this addresses another subsystem.

C:

A stale UUID can point to a nonexistent root volume; that is not equivalent to identifying a non-root mount that breaks startup.

D:

Required remote mounts can delay or block boot when their network endpoint is unavailable; the administrator instead needs identifying a non-root mount that breaks startup; this option serves a different purpose.

Question 600

An NFS client hangs when opening /mnt/share and a remote server is unreachable. Which dependency is probably failing?

  1. Offline filesystem consistency check after backup
  2. NFS server or network path availability
  3. Container writable-layer or quota capacity
  4. Create a supported filesystem before mounting

Explanation

Correct Answer

B:

A hard network mount can wait on unavailable remote I/O. Confirm server reachability and mount options before assuming local disk corruption.

Incorrect Answers

A:

Repair tools may alter filesystem structures, so preserve data and unmount the affected filesystem first; that changes a different part of the system; the requested outcome is recognizing remote filesystem access stalls.

C:

A container's storage driver or configured filesystem quota can limit writes independently of other host mounts; it will not provide recognizing remote filesystem access stalls under these conditions.

D:

A block device with no recognized filesystem cannot be mounted as ext4 or XFS until formatted appropriately; using it would leave recognizing remote filesystem access stalls unresolved.

CompTIA Linux+ (XK0-006) Practice Tests