Select Two (Multi-Select) Questions

Use an initramfs with minimal drivers.

Why it fails: initramfs is required; minimizing it helps but not as effective as other options.

Increase the kernel log level to debug.

Why it fails: Debug logging adds overhead and increases boot time.

Use ext2 instead of ext4 as the root filesystem.

Why it fails: ext2 lacks journaling but not a significant boot time improvement.

ss

Why it fails: Socket statistics.

ping

Why it fails: Ping uses ICMP, not DNS query.

traceroute

Why it fails: Traces network path.

755

Why it fails: 755 is octal notation, not a symbolic mode expression. Symbolic modes combine who (u, g, o, a), an operator (+, -, =) and permissions (r, w, x). Octal would be the correct form when setting absolute permission bits directly rather than modifying existing ones.

c+r

Why it fails: c+r uses an invalid who value; symbolic modes accept only u, g, o and a before the operator. It would be correct if the intended class were others, written as o+r. The letter c denotes no permission class in chmod syntax, so the expression is rejected.

`apt-get install curl`

Why it fails: Apt-get is not used on RHEL.

`zypper install curl`

Why it fails: Zypper is used on SUSE Linux.

ifconfig eth0 192.168.1.10 netmask 255.255.255.0

Why it fails: ifconfig is deprecated; also not part of ip command.

echo 'nameserver 8.8.8.8' > /etc/resolv.conf

Why it fails: Configures DNS, not part of ip command for static IP.

/etc/network/interfaces

Why it fails: This is for the legacy ifupdown system, not systemd-networkd.

/etc/sysconfig/network-scripts/ifcfg-eth0

Why it fails: This is used by Red Hat legacy network scripts, not systemd-networkd.

grep

Why it fails: grep matches and prints lines containing a pattern; it cannot substitute matched text with replacement content, so it produces no modified output. It is tempting because it is the standard tool for pattern searching, and would be correct if the task were merely locating matching lines rather than replacing them.

tr

Why it fails: tr translates or deletes individual characters from standard input; it cannot match multi-character patterns or edit a file in place. It tempts because character substitution resembles replacement, but it is correct only for tasks such as deleting or squeezing single characters in a stream.

cut

Why it fails: cut extracts selected fields or character ranges by delimiter or position; it never substitutes matched text. It tempts because it processes file content and writes to stdout, but it is correct only for column extraction, not for replacing patterns with new strings.

It is formatted with the ext4 filesystem.

Why it fails: /proc is a virtual pseudo-filesystem with no on-disk block device, so it cannot be formatted with ext4 or any disk filesystem. It is tempting because ext4 is the common Linux root filesystem, but /proc is mounted by the kernel and exists only in memory.

It is a network filesystem.

Why it fails: /proc is a kernel-generated virtual filesystem local to each host; it is not exported or accessed over a network. It is tempting because network filesystems like NFS also appear under /proc/mounts, but /proc itself is mounted from the kernel, not a remote server.

It is used to store persistent configuration data.

Why it fails: /proc is a virtual, in-memory pseudo-filesystem generated by the kernel at runtime; nothing written there persists across reboots. It is tempting because /proc/sys accepts tuning values, but those are runtime kernel parameters, whereas persistent configuration belongs in /etc on a real disk filesystem.

df -T

Why it fails: df -T reports filesystem type and usage per mount point, not the UUID stored in the filesystem superblock. It is tempting because it lists mounted block devices, and would be correct when confirming which filesystem type a mounted volume uses.

fdisk -l

Why it fails: fdisk -l lists partition tables, sizes and type codes, but omits filesystem UUIDs. It is tempting because it enumerates block devices and partitions, and would be correct when inspecting or editing partition layout rather than identifying filesystems by UUID.

parted /dev/sda print

Why it fails: parted's print output shows partition geometry, flags and filesystem type, but not filesystem UUIDs. It is tempting because parted inspects block devices directly, and would be correct when creating, resizing or inspecting partition tables rather than querying UUIDs.

dmesg | grep module

Why it fails: dmesg prints kernel ring-buffer messages, which may mention modules during boot but never enumerate currently loaded ones. It is tempting because module-loading messages appear there, yet lsmod or /proc/modules is what actually lists loaded modules.

modprobe -l

Why it fails: modprobe -l was removed in kmod; it listed available module files on disk, not loaded ones, and now errors out. It is tempting because modprobe manages modules, but listing loaded modules requires lsmod or reading /proc/modules, which reflect current kernel state.

modinfo

Why it fails: modinfo only displays metadata about a single module (author, licence, parameters, dependencies); it does not enumerate loaded modules. It is tempting because it inspects kernel modules, but it answers "what is this module?" rather than "what is loaded?", which lsmod or /proc/modules provide.

initctl restart sshd

Why it fails: initctl is the Upstart control command, so it cannot manage units on a systemd-based system and typically reports no such job. It is tempting because it restarted services on older Ubuntu releases, and would be correct on an Upstart host, but systemd uses systemctl restart sshd instead.

rc.d restart sshd

Why it fails: rc.d is the SysV init wrapper; on a systemd host it delegates inconsistently or fails outright, since sshd is managed as an sshd.service unit. It tempts because rc.d scripts remain valid on legacy SysV systems, where restarting services through init scripts is the standard mechanism.

/etc/init.d/sshd restart

Why it fails: On a systemd-based system, /etc/init.d/sshd restart invokes the legacy SysV wrapper, which may be absent or bypass systemd's unit state tracking. It is tempting because it worked on SysV init systems, and would be correct there, but systemd requires systemctl restart sshd or sshd.service.

gzip -d file.gz

Why it fails: gzip -d decompresses file.gz to disk, deleting the compressed original, so nothing is displayed without writing to storage. It tempts because gzip is the standard GNU compression utility, and would be correct where the task is restoring a compressed file for further processing rather than viewing its contents in place.

tar -xzf file.tar.gz

Why it fails: tar -xzf extracts the archive to disk, writing every member to the filesystem, which is precisely what the question excludes. It tempts because tar handles compressed archives natively and is the standard tool for listing contents, but listing requires -t (tar -tzf), not extraction with -x.

uncompress file.Z

Why it fails: uncompress file.Z restores the file to disk, replacing the compressed original, so contents are not displayed without writing to storage. It tempts because it is the canonical tool for .Z archives, and would be correct where the task is decompressing a file for subsequent use rather than viewing it in place.

user

Why it fails: The user option permits an unprivileged account to mount the filesystem, but boot mounting is governed by the noauto option and the pass field. It is tempting because it changes mount behaviour, and would be correct for removable media a desktop user mounts on demand.

defaults

Why it fails: The defaults option expands to rw,suid,dev,exec,auto,nouser,async, so it enables automatic mounting rather than preventing it; the question asks which options affect whether mounting occurs. It is tempting as the common baseline entry, and would be correct when no special mount behaviour is required.

ro

Why it fails: The ro option controls write permission on the mounted filesystem, not whether systemd or mount mounts it during boot. It is tempting because it appears in the same options field, and would be the correct choice if the question asked how to protect a recovery partition from modification.

fdisk

Why it fails: fdisk partitions block devices by writing partition tables; it never writes filesystem metadata, so mkfs remains necessary afterwards. It is tempting because partitioning is the usual precursor step, and fdisk would be the right tool when creating or resizing partitions before any filesystem exists.

parted

Why it fails: parted partitions disks and can set a partition's type, but it does not write a filesystem; mkfs and mke2fs do. It is tempting because partitioning is the step immediately preceding filesystem creation, and parted would be correct if the task were creating or resizing the partition itself.

fsck

Why it fails: fsck checks and repairs existing filesystem structures; it cannot lay down new superblocks, inodes or journals on a blank partition. It is tempting because it operates on filesystems, and would be correct when an existing filesystem has corruption needing repair rather than creation.

mkfs.btrfs /dev/sdb1

Why it fails: mkfs.btrfs creates a Btrfs filesystem, not ext4, so it cannot satisfy the requirement. It is tempting because mkfs.btrfs is the correct tool when Btrfs features such as snapshots, subvolumes or checksumming are wanted, but the stem explicitly asks for ext4, which requires mkfs.ext4 or mke2fs -t ext4.

mkfs.msdos /dev/sdb1

Why it fails: mkfs.msdos writes FAT filesystems, so it cannot create ext4 regardless of the target partition. It is tempting because mkfs front-ends share identical syntax, and mkfs.msdos is the right tool when a partition must be readable by Windows or embedded devices requiring FAT16/FAT32.

mkfs.xfs /dev/sdb1

Why it fails: mkfs.xfs writes an XFS filesystem, so it cannot create ext4 regardless of the target partition. It is tempting because mkfs.xfs is the correct tool when the requirement is an XFS filesystem, for example on RHEL default installations, but here the stem specifies ext4, which mkfs.xfs never produces.

yum

Why it fails: yum resolves and installs RPM packages on Red Hat-derived distributions, so it cannot read Debian's .deb format or APT repositories. It is tempting because it performs equivalent dependency handling and repository management, and would be correct on RHEL, CentOS or Fedora systems.

rpm

Why it fails: rpm is the Red Hat package manager, handling .rpm packages on RHEL-family systems; it cannot install or query .deb packages, so it fails this Debian requirement. It is tempting because it is a genuine low-level package tool, and would be correct on CentOS, Fedora or RHEL hosts.

zypper

Why it fails: zypper manages packages on SUSE and openSUSE via RPM, so it cannot handle .deb archives or Debian's dpkg/APT metadata. It is tempting because it offers the same install, update and dependency-resolution workflow, and would be the right answer for a SUSE-based question.

/etc/network/interfaces

Why it fails: This file is specific to Debian networking; not essential on all systems.

/etc/sysctl.conf

Why it fails: Configures kernel parameters, not directly for networking basics.

/etc/apt.conf.d/

Why it fails: This directory holds APT configuration snippets, not repository definitions.

/etc/pacman.d/

Why it fails: Pacman is used by Arch Linux, not covered in LPIC-1.

password

Why it fails: Passwords are set in /etc/grub.d/ files, not directly in grub.cfg.

chainloader

Why it fails: While chainloader is valid, it's less common in standard linux boot entries; but it can appear. However, I'll mark as false to have exactly three correct. Actually, chainloader can appear for booting other OS. But to avoid ambiguity, I'll pick 'set default' instead? No, I have three with A,C,D. So E false.

`dpkg --info curl.deb`

Why it fails: Displays info from a .deb file, not the installed package.

`apt-get check`

Why it fails: Checks for broken dependencies system-wide, not for a specific package.