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

Question 580

A RAID1 array shows a failed device but the volume remains accessible. What should the operator prioritize?

  1. Verify md array state and replace the failed member
  2. Available filesystem inodes
  3. Create a supported filesystem before mounting
  4. Failing storage hardware

Explanation

Correct Answer

A:

RAID1 can remain active in degraded mode while mirror redundancy is lost. Array health and a controlled rebuild should be confirmed promptly.

Incorrect Answers

B:

An inode shortage prevents creating new files despite free block capacity, so inode utilization must be checked independently. df -i distinguishes inode exhaustion from block capacity; that is not equivalent to restoring redundancy in a degraded mirror.

C:

A block device with no recognized filesystem cannot be mounted as ext4 or XFS until formatted appropriately; the administrator instead needs restoring redundancy in a degraded mirror; this option serves a different purpose.

D:

Increasing device errors and sector remapping suggest media degradation; it answers a neighboring question rather than restoring redundancy in a degraded mirror.

Question 581

A Linux VM lacks a reported CPU virtualization extension while the physical host supports it. Which hypervisor setting may be disabled?

  1. Nested virtualization exposure
  2. CPU, memory, or platform hardware fault
  3. Inspect BMC power and hardware sensor events
  4. Cooling, airflow and fan health

Explanation

Correct Answer

A:

Guests need virtualization extensions exposed by the host hypervisor to run nested accelerated VMs. Hardware support alone does not imply guest availability.

Incorrect Answers

B:

Machine-check records can report low-level hardware errors rather than application exceptions; it will not provide enabling virtual CPU extensions inside a guest under these conditions.

C:

Out-of-band management can report chassis power, thermal and hardware faults even when the OS is unavailable; using it would leave enabling virtual CPU extensions inside a guest unresolved.

D:

Thermal throttling reduces frequency to protect silicon; the requirement is enabling virtual CPU extensions inside a guest, outside the effect of this choice.

Question 582

An administrator sees repeated machine-check hardware errors in the kernel journal. Which class of failure should be considered?

  1. Controller driver binding and dmesg errors
  2. Firmware memory map and DIMM hardware status
  3. Nested virtualization exposure
  4. CPU, memory, or platform hardware fault

Explanation

Correct Answer

D:

Machine-check records can report low-level hardware errors rather than application exceptions. Decode the event and correlate with vendor diagnostics.

Incorrect Answers

A:

PCI enumeration proves the hardware is discovered, not that a driver has initialized attached storage; the evidence calls for investigating low-level machine-check records, not merely this separate operation.

B:

Incorrectly seated or failed DIMMs can reduce memory visible to Linux; the task involves investigating low-level machine-check records, whereas this addresses another subsystem.

C:

Guests need virtualization extensions exposed by the host hypervisor to run nested accelerated VMs; its scope differs from investigating low-level machine-check records, so it cannot meet the stated requirement.

Question 583

A daemon remains in D state and ignores SIGKILL during a blocked filesystem operation. What does D state usually indicate?

  1. Parent process child-reaping behavior
  2. Uninterruptible sleep waiting on kernel I/O
  3. Invalid process memory access
  4. Invalid ExecStart path or inability to execute it
  5. Service shutdown handler and TimeoutStopSec

Explanation

Correct Answer

B:

Processes in uninterruptible sleep cannot complete signal handling until the kernel wait ends. Investigate blocked storage or network filesystem I/O.

Incorrect Answers

A:

A zombie persists until its parent collects exit status or it is reparented and reaped; it answers a neighboring question rather than diagnosing an unkillable task in D state.

C:

A segmentation fault occurs when a process accesses memory in violation of protection rules; this does not achieve diagnosing an unkillable task in D state on the system described.

D:

Systemd's 203/EXEC commonly indicates the configured executable could not be started; it will not provide diagnosing an unkillable task in D state under these conditions.

E:

Slow cleanup or a stuck process can exceed systemd's grace period; using it would leave diagnosing an unkillable task in D state unresolved.

Question 584

During startup the console says kernel panic - not syncing after storage probing. Which evidence should be captured before another reboot?

  1. Incorrect GRUB boot-path references
  2. Last kernel console messages and panic context
  3. Different PATH and execution environment
  4. UEFI firmware boot entry or EFI path

Explanation

Correct Answer

B:

Panic logs, call traces and boot parameters narrow the failing driver or subsystem. Repeated rebooting without preserving evidence can hide the original cause.

Incorrect Answers

A:

The bootloader may no longer find its modules or configuration after a partition change; the requirement is collecting evidence from a kernel panic, outside the effect of this choice.

C:

Systemd services receive a controlled environment that may omit interactive profile additions; the evidence calls for collecting evidence from a kernel panic, not merely this separate operation.

D:

UEFI firmware entries locate an EFI executable by device and path; the task involves collecting evidence from a kernel panic, whereas this addresses another subsystem.

Question 585

A server boots but takes over two minutes at a network filesystem mount that is optional. What is the likely configuration weakness?

  1. UEFI firmware boot entry or EFI path
  2. /etc/fstab entry for /data
  3. Hard dependency on an unavailable network mount
  4. Different PATH and execution environment
  5. systemctl list-dependencies and failed units
  6. Boot the prior known-good kernel

Explanation

Correct Answer

C:

Required remote mounts can delay or block boot when their network endpoint is unavailable. Automount or nonfatal mount options can reduce coupling.

Incorrect Answers

A:

UEFI firmware entries locate an EFI executable by device and path; that is not equivalent to removing boot's dependency on optional remote storage.

B:

Incorrect identifiers, mount types or required mounts can push boot into emergency mode; the administrator instead needs removing boot's dependency on optional remote storage; this option serves a different purpose.

D:

Systemd services receive a controlled environment that may omit interactive profile additions; that changes a different part of the system; the requested outcome is removing boot's dependency on optional remote storage.

E:

Systemd dependency inspection reveals which required unit blocked target activation; this does not achieve removing boot's dependency on optional remote storage on the system described.

F:

A working older kernel isolates the regression and restores service without immediately rebuilding disks; it will not provide removing boot's dependency on optional remote storage under these conditions.

Question 586

A recently updated service exits with status 203/EXEC under systemd. Which issue is most likely?

  1. Parent process child-reaping behavior
  2. Service shutdown handler and TimeoutStopSec
  3. Invalid ExecStart path or inability to execute it
  4. Uninterruptible sleep waiting on kernel I/O

Explanation

Correct Answer

C:

Systemd's 203/EXEC commonly indicates the configured executable could not be started. Check path existence, permissions and interpreter dependencies.

Incorrect Answers

A:

A zombie persists until its parent collects exit status or it is reparented and reaped; it will not provide diagnosing systemd executable startup failure under these conditions.

B:

Slow cleanup or a stuck process can exceed systemd's grace period; using it would leave diagnosing systemd executable startup failure unresolved.

D:

Processes in uninterruptible sleep cannot complete signal handling until the kernel wait ends; it does not deliver diagnosing systemd executable startup failure, which is decisive in this scenario.

Question 587

A volume group has free extents and its logical volume was enlarged, yet df still reports the old size. What remains to do?

  1. Container writable-layer or quota capacity
  2. Grow the filesystem on the extended LV
  3. Filesystem user or project quota enforcement
  4. Mount point hides its underlying directory contents when active

Explanation

Correct Answer

B:

Increasing the LVM block device does not always resize the filesystem. Use the filesystem-specific expansion tool after verifying the mounted type.

Incorrect Answers

A:

A container's storage driver or configured filesystem quota can limit writes independently of other host mounts; the task involves completing filesystem growth after an LV resize, whereas this addresses another subsystem.

C:

Quotas may deny additional allocation even when the filesystem has free blocks and ordinary permissions allow writes; that is not equivalent to completing filesystem growth after an LV resize.

D:

Mounting a filesystem overlays the directory used as a mount point; the administrator instead needs completing filesystem growth after an LV resize; this option serves a different purpose.

Question 588

The system inventory shows only half the expected RAM after maintenance. Which evidence is most useful?

  1. Nested virtualization exposure
  2. CPU, memory, or platform hardware fault
  3. Firmware memory map and DIMM hardware status
  4. Inspect BMC power and hardware sensor events

Explanation

Correct Answer

C:

Incorrectly seated or failed DIMMs can reduce memory visible to Linux. Compare firmware records and kernel memory ranges with hardware diagnostics.

Incorrect Answers

A:

Guests need virtualization extensions exposed by the host hypervisor to run nested accelerated VMs; that changes a different part of the system; the requested outcome is diagnosing physically missing installed memory.

B:

Machine-check records can report low-level hardware errors rather than application exceptions; this does not achieve diagnosing physically missing installed memory on the system described.

D:

Out-of-band management can report chassis power, thermal and hardware faults even when the OS is unavailable; using it would leave diagnosing physically missing installed memory unresolved.

Question 589

lsblk shows a new disk, but mount rejects it with unknown filesystem type and there is no partition data to preserve. What step may be missing?

  1. Create a supported filesystem before mounting
  2. Container writable-layer or quota capacity
  3. Mount point hides its underlying directory contents when active
  4. Processes holding files or working directories on the mount

Explanation

Correct Answer

A:

A block device with no recognized filesystem cannot be mounted as ext4 or XFS until formatted appropriately. Formatting destroys previous logical contents.

Incorrect Answers

B:

A container's storage driver or configured filesystem quota can limit writes independently of other host mounts; the evidence calls for diagnosing a blank unformatted volume, not merely this separate operation.

C:

Mounting a filesystem overlays the directory used as a mount point; the task involves diagnosing a blank unformatted volume, whereas this addresses another subsystem.

D:

Open file descriptors and current working directories can keep a filesystem busy; its scope differs from diagnosing a blank unformatted volume, so it cannot meet the stated requirement.

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.

CompTIA Linux+ (XK0-006) Practice Tests