XK0-006 Troubleshooting Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  iostat -d

  Why it's wrong here

  iostat -d displays disk I/O statistics, such as reads and writes per second, for block devices. It is used to monitor disk performance and throughput, not disk space usage. It cannot tell you which directories or files are consuming space, so it is irrelevant to this troubleshooting scenario.

• ✗

  ls -laR /

  Why it's wrong here

  ls -laR recursively lists all files and directories with details. While it shows file sizes, the output is enormous and not sorted, making it impractical to identify the largest space consumers. It does not summarize usage, and the administrator would have to manually scan through thousands of lines, which is inefficient.

• ✓

  du -sh /*

  Why this is correct

  The du command estimates file space usage. The -s option summarizes each argument, and -h makes the output human-readable. Running du -sh /* shows the total size of each top-level directory, quickly identifying which directory is using the most space. This is a fast and effective way to pinpoint the largest consumers.

• ✓

  find / -type f -size +100M -exec ls -lh {} \;

  Why this is correct

  This find command searches for files larger than 100 MB and lists them with human-readable sizes. It helps identify large individual files that may be consuming significant space. While it does not summarize by directory, it is useful for finding large files, which is a common cause of disk space exhaustion. It complements du by pinpointing specific large files.

• ✗

  df -h

  Why it's wrong here

  df -h displays disk space usage for all mounted filesystems in human-readable format. It shows how much space is used and available on each filesystem, but it does not break down usage by directory or file. Therefore, it cannot identify which specific directories are consuming the most space, only that a filesystem is full.

Go deeper

Related to this question