Why is /etc/shadow not world readable if the passwords are stored in an encrypted fashion?
Correct Answer: D
Question 172
On a system running the KDE Display Manager, when is the /etc/kde4/kdm/Xreset script automatically executed?
Correct Answer: E
Question 173
Which command, available with all MTAs, is used to list the contents of the MTA's mail queue? (Specify ONLY the command without any path or parameters.)
Correct Answer:
mailq, /usr/bin/mailq, sendmail -bp, /usr/sbin/sendmail -bp, /usr/lib/sendmail -bp, sendmail, /usr/sbin/sendmail, /usr/lib/sendmail Explanation: The command that is used to list the contents of the MTA's mail queue is mailq12. This command is available with all MTAs, such as sendmail, postfix, exim, etc12. The mailq command prints the mail queue, which is the list of messages that are waiting tobe sent12. The output of the mailq command shows the queue ID, size, time, sender, and recipient of each message12. The mailq command can also take various options to modify the output, such as -v for verbose mode, -Ac for mail submission queue, -qL for lost items, and -qQ for quarantined items3. References: 1: mailq Command in Linux with Examples - GeeksforGeeks 2: mailq Command Examples in Linux - The Geek Diary 3: linux - How to see entire sendmail queue? - Server Fault
Question 174
In case neither cron.allow nor cron.deny exist in /etc/, which of the following is true?
Correct Answer: B
The /etc/cron.allow and /etc/cron.deny files are used to control access to the crontab command and cron jobs for individual users. If neither of these files exists, then depending on site-dependent configuration parameters, only the superuser (root user) will be allowed to use this command, or all users will be able to use this command1. The default behavior of most Linux distributions is to allow all users to use the crontab command and have user specific crontabs if neither /etc/cron.allow nor /etc/cron.deny exists23. Therefore, option B is the correct answer. The other options are not true because: * Option A is false because it contradicts the default behavior of most Linux distributions. * Option C is false because the cron daemon will not refuse to start or report missing files in the system's logfile if neither /etc/cron.allow nor /etc/cron.deny exists. The cron daemon will start normally and use the default configuration parameters1. * Option D is false because the system administrator does not need to approve user specific crontabs explicitly. The user can create, edit, display, or remove their own crontab files without any intervention from the system administrator1. References: * How cron.allow and cron.deny can be used to limit access to crontab for a particular user | The Geek Search * crontab(1) - cron - Debian bullseye - Debian Manpages * Controlling Access to crontab (System Administration Guide: Basic Administration) - Oracle * /etc/cron.allow - Linux Bash Shell Scripting Tutorial Wiki - nixCraft
