Free LPIC-1 Exam 102, Part 2 of 2, version 5.0 Practice Questions

The command userdel --force --remove bob is used to delete the user account named bob and all its associated files. The --force option forces the removal of the user account, even if the user is still logged in. The --remove option forces userdel to remove the user’s home directory and mail spool, even if another user uses the same home directory or if the mail spool is not owned by the specified user12. Therefore, options A and B are true regarding this command.

The other options are not true because:

Option C is false because the locate database is not updated by the userdel command. The locate database is updated by the updatedb command, which is usually run by cron as a scheduled job3.

Option D is false because the userdel command does not remove all files owned by bob from all mounted filesystems. The userdel command only removes the user’s home directory and mail spool, and it does not search for and delete the user files located in other file systems. You have to search for and delete the files manually1.

Option E is false because the userdel command does not delete the group with the same name as the user, unless the USERGROUPS_ENAB parameter is set to yes in the /etc/login.defs file and the group has no other members14.

References:

How to Delete/Remove Users in Linux (userdel Command) | Linuxize

userdel(8) — Linux manual page

updatedb(8) — Linux manual page

Understanding the /etc/login.defs File | Linuxize

The /etc/at.deny file specifies the user accounts that can NOT submit jobs via at or batch. The format of the file is a list of usernames, one on each line. Whitespace is not permitted. The superuser may always use at. If the file /etc/at.allow exists, only usernames mentioned in it are allowed to use at. If /etc/at.allow does not exist, /etc/at.deny is checked12. The at and batch commands use the files /usr/lib/cron/at.allow and /usr/lib/cron/at.deny to restrict usage on some systems3. References:

at.allow(5) - Linux man page

at.deny(5) [linux man page] - The UNIX and Linux Forums

The at.allow and at.deny files - IBM

The groupadd command creates a new group using the options specified on the command line and the default values from the /etc/login.defs file. It adds an entry for the new group to the /etc/group and /etc/gshadow files. Only the root user or a user with sudo privileges can create new groups using this command. The general syntax for the groupadd command is as follows:

groupadd [OPTIONS] GROUPNAME

Some of the common options for the groupadd command are:

-g, --gid GID: Specify the numeric group ID for the new group. If not given, the system will assign the next available GID from the range of group IDs specified in the login.defs file.

-r, --system: Create a system group with a GID chosen from the range of system group IDs specified in the login.defs file. System groups are usually used for some special system operation purposes, like creating backups or doing system maintenance.

-f, --force: Suppress the error message if the group already exists and exit successfully. This option is useful for scripts that need to ensure the existence of a group.

-K, --key KEY=VALUE: Override the default values from the /etc/login.defs file. The valid keys are GROUP_MIN_ID, GROUP_MAX_ID, SYS_GROUP_MIN_ID, SYS_GROUP_MAX_ID, and GID_INCREMENT.

References:  https://www.makeuseof.com/linux-file-ownership-groups-guide/

https://linuxize.com/post/how-to-create-groups-in-linux/

https://linuxhandbook.com/groupadd-command/

 The Bash shell can be configured by various files that affect its behavior, such as setting environment variables, aliases, functions, options, and prompts. Some of these files are global, meaning they apply to all users of the system, and some are local, meaning they apply to individual users. The global files are usually located in the /etc directory, while the local files are usually located in the user’s home directory, which is denoted by the tilde (~) symbol1.

The local files that affect the Bash shell are:

~/.bash_profile: This file is executed when a user logs in to the system. It is used to set up the user’s environment, such as the PATH, the default editor, the umask, and other variables. It can also run commands that are needed only once per login session, such as ssh-agent or fortune. This file can also source other files, such as ~/.bashrc, to inherit their settings12.

~/.bashrc: This file is executed when a user starts a new interactive shell, such as opening a terminal window or running a script with the shebang #!/bin/bash. It is used to set up the user’s shell preferences, such as aliases, functions, options, and prompts. It can also source other files, such as /etc/bashrc, to inherit their settings12.

~/.bash_logout: This file is executed when a user logs out of the system. It is used to perform any cleanup tasks, such as clearing the screen, deleting temporary files, or printing a farewell message1.

The other files listed in the question are not valid Bash configuration files and do not affect the behavior of the shell. Therefore, the correct answer is

B.  

E.  

References: 1: Bash Shell Configuration Files - Land of Linux 2: Bash Startup Files - GNU Project