Hard Difficulty Questions

single

Why wrong: Legacy runlevel, not the preferred systemd method.

init=/bin/bash

Why wrong: Bypasses init, not recommended for rescue.

quiet splash

Why wrong: Hides boot messages, does not change runlevel.

modinfo

Why wrong: Shows info about a specific module.

dmesg

Why wrong: Shows kernel messages, not a direct list of loaded modules.

modprobe -l

Why wrong: Lists available modules, not loaded ones.

RUN --mount=type=cache

Why wrong: Used for cache mounts, not multi-stage.

Layer caching

Why wrong: Helps build speed, not image size reduction.

Using a smaller base image like Alpine

Why wrong: Helps but not the feature for combining stages.

Run 'fuser 4444/tcp' to find the PID and then use 'systemctl stop' to stop the service.

Why wrong: fuser can find the PID, but systemctl cannot stop a non-systemd service.

Run 'lsof -i :4444' to find the PID, then use 'systemctl disable' to disable the service.

Why wrong: lsof finds the PID but systemctl disable only applies to systemd services.

Run 'systemctl status' to find the service name, then use 'systemctl stop' to stop it.

Why wrong: systemctl cannot show or manage non-systemd services.

set -e pre_backup_cmd backup_cmd

Why wrong: set -e exits on any error but does not allow custom logging, and it may exit prematurely without proper handling.

pre_backup_cmd && backup_cmd || echo 'Error' >&2

Why wrong: Using && and || has pitfalls; if backup_cmd fails, it also triggers the error message, which is not intended.

(pre_backup_cmd; if [ $? -ne 0 ]; then echo 'Error' >&2; exit 1; fi) && backup_cmd

Why wrong: The subshell prevents the exit from stopping the main script, and the error handling is flawed.

Run 'fsck /dev/sda1' from the GRUB command line

Why wrong: GRUB command line does not have fsck; fsck requires a full OS.

Use 'systemctl rescue' from the boot prompt

Why wrong: systemctl commands are not available at the boot prompt; they require a running system.

firewall-cmd --zone=public --add-service=https

Why wrong: This adds the rule but not permanently; it will be lost after reload.

firewall-cmd --service=https --add --zone=public --permanent

Why wrong: The syntax is incorrect; --add-service is the correct option.

firewall-cmd --add-port=443/tcp --zone=public --permanent

Why wrong: While this also works, the question specifically asks for HTTPS service, and using --add-service is the preferred method.

rescue.target

Why wrong: Rescue starts some services; emergency is more minimal.

multi-user.target

Why wrong: Multi-user starts networking and services, not ideal for recovery.

graphical.target

Why wrong: Graphical target starts the GUI, not minimal.

openssl genrsa -out key.pem 2048 && openssl req -new -key key.pem -out req.pem

Why wrong: This also works but is two commands, not one step. The question asks for one step.

openssl req -new -key key.pem -out req.pem

Why wrong: This assumes the private key already exists, does not create one.

openssl req -x509 -newkey rsa:2048 -keyout key.pem -out cert.pem -days 365

Why wrong: This creates a self-signed certificate, not a CSR.

ltrace

Why wrong: ltrace traces library calls, not system calls.

dmesg

Why wrong: dmesg shows kernel ring buffer messages, not per-process traces.

lsof

Why wrong: lsof lists open files, not system call traces.

$VAR

Why wrong: Incorrect. $VAR is used to expand the value of a variable, not to capture command output.

$((command))

Why wrong: Incorrect. $(( )) is used for arithmetic expansion, not command substitution.

`command`

Why wrong: Incorrect but historically used. Backticks `command` also perform command substitution, but the $(command) syntax is preferred and less error-prone.

sar -r -b

Why wrong: Shows memory and I/O, not CPU.

sar -n DEV

Why wrong: Shows network stats.

sar -u -s 00:00:00 -e 23:59:59

Why wrong: This shows current day's data, not historical.

mount -o remount,rw / && fsck /

Why wrong: fsck on a mounted filesystem can cause corruption; it must be unmounted.

xfs_repair /dev/sda1

Why wrong: xfs_repair is for XFS filesystems; not all systems use XFS.

journalctl -xb

Why wrong: journalctl shows logs but does not repair filesystems.

pam_pwquality

Why wrong: pam_pwquality enforces password complexity, not lockout.

pam_securetty

Why wrong: pam_securetty restricts root login to secure terminals.

pam_unix

Why wrong: pam_unix handles standard authentication, not lockout.

The file /var/www/html/index.html has incorrect SELinux context

Why wrong: Would show a different SELinux denial message.

The Apache service is running under the wrong user

Why wrong: Would cause different issues, not specifically this error.

The file /var/www/html/index.html is missing read permission for the Apache user

Why wrong: Would say 'permission denied' when reading the file, not 'search permissions'.

rwxrwxr-x (775)

Why wrong: That would be umask 002.

rwxrwxrwx (777)

Why wrong: That would be umask 000.

rw-rw-r-- (664)

Why wrong: That is typical for files, not directories.

Increase the PID limit in /proc/sys/kernel/pid_max.

Why wrong: The PID limit is not the issue; there are only a few processes.

Kill the parent process of the zombie (PID 1234).

Why wrong: Killing the parent would not clean the zombie; the zombie's parent is init after reparenting.

Terminate the zombie process with SIGKILL.

Why wrong: Zombies are already dead; they cannot be killed. The parent must reap them.

lsof

Why wrong: Lists open files, not a rootkit detector.

netstat

Why wrong: Network statistics tool.

clamav

Why wrong: Antivirus, not rootkit-specific.

chronyd -q

Why wrong: chronyd -q sets time then exits, but may not be intended for large offsets.

systemctl restart ntp

Why wrong: Restarts the service but does not force a step.

timedatectl set-ntp true

Why wrong: This enables NTP service but does not force immediate sync.

The firewall is blocking port 22

Why wrong: Firewall would not cause 'address in use' error.

The sshd configuration file has incorrect permissions

Why wrong: Would show permission denied, not address in use.

The sshd service is not installed

Why wrong: The service file exists, so it is installed.