702-100 LPI Linux Professional Institute BSD Specialist Free Practice Exam Questions (2025 Updated)

The correct configuration line for sending all messages from the auth facility to a remote syslog server is auth.* @logger.example.org. In syslog configuration, the auth.* specifies the facility and priority, where auth is the facility for security/authorization messages, and * represents all priorities. The @ symbol is used to indicate that the messages are to be sent to a remote server, followed by the hostname of the remote syslog server. References:

FreeBSD Handbook - Logging

Linux Professional Institute BSD Specialist Exam Objectives

A symbolic link, or symlink, is a special type of file that points to another file or directory on the file system1. When creating a symbolic link with the ln command, the syntax is as follows:

ln -s target link

where target is the file or directory to link to, and link is the name of the symbolic link2. If the link name already exists, the ln command will fail and display an error message indicating that the target already exists3. This is because the ln command does not overwrite existing files or directories by default4. Therefore, the only way to create a symbolic link with the same name as an existing file or directory is to manually remove the existing target first, and then run the ln command again. Alternatively, the ln command can be used with the -f (force) option, which will remove the existing target and create the symbolic link in one step4. However, this option is not mentioned in the question, so the correct answer is A.

References: 1: How to Create Symbolic Links in Linux [Complete Guide] - Linux Handbook 2: Ln Command in Linux (Create Symbolic Links) | Linuxize 3: How to Create and Use Symbolic Links (aka Symlinks) on Linux - How-To Geek 4: Symbolic Links in Unix/Linux - Stack Abuse

The -e option of the crontab command opens the current user’s crontab in an editor. The editor used is determined by the environment variables VISUAL or EDITOR. If neither of these variables is set, the default editor is vi. The user can edit the crontab file to add, modify, or delete cron jobs, which are scheduled commands or scripts that run at a specified time or interval. The crontab file has the following format:

minute hour day-of-month month day-of-week command

Each field can be a number, a range, a list, or an asterisk (*), which means all possible values. The command can be any valid shell command or script. For example, the following crontab entry runs the backup.sh script every day at 2:30 AM:

30 2 * * * /home/user/backup.sh

To save and install the crontab file, the user needs to exit the editor. The crontab command will check the syntax of the file and report any errors. If the file is valid, it will be installed and the cron daemon will execute the cron jobs according to the schedule. References:

crontab(1) - Linux manual page

FreeBSD Handbook: 11.6. Scheduling Tasks

The excerpt C is a valid if condition in the Bourne shell because it uses the correct syntax and operators for the test command. The syntax of the if statement in the Bourne shell is:

if test-commands; then consequent-commands; [elif more-test-commands; then more-consequents;] [else alternate-consequents;] fi

The test-commands are any commands that return a status of 0 (true) or non-zero (false). The test command is a common way to perform various tests on files, strings, and numbers. The test command has the following format:

test expression

The expression consists of one or more primaries, which are unary or binary operators that evaluate to true or false. The primaries can be combined with the following operators:

! expression: Logical NOT expression -a expression: Logical AND expression -o expression: Logical OR ( expression ): Parentheses for grouping

The excerpt C uses the test command with the following expression:

“$var” = “test”

This expression tests if the value of the variable $var is equal to the string “test”. The = operator is a string comparison operator that returns true if the strings are equal. The double quotes around the variable and the string are used to prevent word splitting and globbing by the shell. The spaces around the operator are also required by the test command.

The excerpt C also uses the correct syntax for the then and fi keywords, which mark the beginning and the end of the if statement. The then keyword must be on the same line as the test command, or on a new line after a semicolon. The fi keyword must be on a new line.

The other excerpts are invalid for various reasons:

The excerpt A uses the && operator instead of the -a operator for logical AND. The && operator is a shell operator that executes the second command only if the first command succeeds. The test command does not recognize the && operator as a valid argument. The excerpt A also uses the != operator instead of the -ne operator for numeric comparison. The != operator is a string comparison operator that returns true if the strings are not equal. The -ne operator is a numeric comparison operator that returns true if the numbers are not equal.

The excerpt B uses the [ [ construct instead of the test command. The [ [ construct is a shell keyword that performs conditional expressions similar to the test command, but with some extensions and differences. The [ [ construct is not part of the POSIX standard and is not supported by all shells. The Bourne shell does not support the [ [ construct, and will treat it as a command name. The excerpt B also uses the wrong syntax for the then keyword, which must be on a new line or after a semicolon.

The excerpt D uses the wrong syntax for the test command, which requires a space after the opening bracket and before the closing bracket. The excerpt D also uses the wrong syntax for the fi keyword, which must be on a new line.

The command grep "non [-] disclosure" legalfile matches the lines in the file that contain the pattern non [-] disclosure, where the brackets indicate a character class that matches either a space or a dash. Therefore, the lines that contain non-disclosure or non - disclosure are matched by the command, while the line that contains disclosure only is not matched. The file has two lines that contain non-disclosure, so the correct answer is E. non-disclosure and non-disclosure Only. References:

grep - IBM

Character Classes and Bracket Expressions - GNU

The command that generates the output showing kernel module IDs, reference counts, addresses, sizes, and names iskldstatin FreeBSD. This command is used to display thestatus of loaded kernel modules, including those loaded dynamically. The output format shown in the question is characteristic ofkldstat, where it lists the kernel modules currently loaded into the system's memory along with their respective details.

References:

FreeBSD Handbook or Manual Pages (man pages), specifically the section on kernel modules and thekldstatcommand.

Linux Professional Institute BSD Specialist resources, which cover FreeBSD commands and utilities, including those for managing kernel modules.

The last command displays a list of the last logged in users on a BSD system. The output consists of several columns that show the user name, the terminal name, the login date and time, and the logout date and time or the current status. The option C is the only line that matches the format of the last command output. It shows that the user root logged in on the terminal ttyv0 on Saturday, May 18, 2023 at 13:35 and is still logged in. The other options are either invalid lines or belong to othercommands or sources. For example, option A is the output of the uptime command, option B is a line from the /var/log/auth.log file, option D is a line from the ps command, and option E is the output of the uname -a command. References:

[last] - FreeBSD last(1) Manual Page

[How to use the last command in Linux] - Linuxize

The pgrep command is used to find processes by various criteria, such as user name, group name, process ID, command name, etc. The -u option specifies the user name or user ID to match. Therefore, the command pgrep -u bob will show all processes owned by the user bob. The output will be a list of process IDs, one per line. To show more information about the processes, such as command name, arguments, state, etc., the -l, -a, and -f options can be used. For example, the command pgrep -l -u bob will show the process ID and the command name for each process owned by bob. References:

pgrep - FreeBSD, the manual page for the pgrep command on FreeBSD.

How to use pgrep and pkill commands in Linux - Linuxize, a tutorial on how to use the pgrep and pkill commands in Linux.

Compiling an application from source code allows for customization of the binary to a system’s particular needs, including optimization for specific hardware and enabling or disabling certain features. Pre-compiled binaries are quick and easy to install but they don’t allow for such customization.

References:

Understand the difference between a pre-compiled binary and compiling from source

The command cp SI 52 in the Bourne shell script copies the file named by the value of SI to the file named 52. The SI is a positional parameter that represents the first argument passed to the script when it is executed. Positional parameters are numbered from 1 to 9, and can be accessed by using the dollar sign $ followed by the number. For example, $1 is the first positional parameter, $2 is the second, and so on. Therefore, the SI in the script is equivalent to $1, and it represents the first argument passed to the script. The correct answer is D. A positional parameter. References:

[Positional Parameters - FreeBSD]

[Shell Scripting Tutorial - Positional Parameters]

The /etc/newsyslog.conf file is the configuration file for the newsyslog command, which is used to rotate log files on BSD systems. The newsyslog command is typically run by cron at regular intervals to check if any log files need to be rotated based on the criteria specified in the /etc/newsyslog.conf file. The file contains a series of entries, one per line, that define the log file name, the owner and group, the mode, the count, the size, the when, the flags, and the pidfile for each log file. For example, the following entry in the /etc/newsyslog.conf file:

/var/log/messages root:wheel 644 7 * @T00 Z /var/run/syslog.pid

means that the /var/log/messages file is owned by root and belongs to the wheel group, has the mode 644, is rotated 7 times, has no size limit, is rotated at midnight every day, is compressed after rotation, and the process ID of syslogd is read from /var/run/syslog.pid and sent a signal to reopen the log file.

The other options are either invalid files or belong to other purposes. For example, /etc/logs.conf is not a valid file, /etc/rc.logd is a startup script for the log daemon, /etc/rc.d/syslogd is a startup script for the syslog daemon, and /etc/syslog.conf is the configuration file for the syslog daemon.

References:

[newsyslog.conf] - FreeBSD newsyslog.conf(5) Manual Page

[newsyslog] - FreeBSD newsyslog(8) Manual Page

[Log File Rotation] - FreeBSD Handbook

The inetd.conf file is the configuration file that needs to be edited before the TFTP service will start on a BSD system. The inetd daemon handles the TFTP service and other network services, and its configuration file contains settings that determine howthese services are managed. To enable the TFTP service, the corresponding entry in inetd.conf must be uncommented and properly configured. References:

FreeBSD Handbook - inetd

Linux Professional Institute BSD Specialist Exam Objectives

The wq! command is used to save a file and quit the vi editor, even if the file is read-only. The w command means write, the q command means quit, and the ! command means force. By combining these commands, the vi editor will override the file permissions and save the changes to the file, then exit the editor. The other options are either invalid syntax or do not force the write operation. For example, wq will save and quit only if the file is writable, ql will quit without saving, and fw! will force write but not quit. References:

[vi] - FreeBSD vi(1) Manual Page

[wq!] - How to save a file in vi / vim editor in Linux / Unix

The /etc/nsswitch.conf file defines the order of the name resolution methods used on a NetBSD system. It specifies the sources and their priority for various databases, such as hosts, services, protocols, etc. The sources can be files, DNS, NIS, or other services. For example, the following line in /etc/nsswitch.conf indicates that the hosts database should be looked up first in the /etc/hosts file, then in the DNS server, and finally in the NIS server:

hosts: files dns nis

References:

nsswitch.conf(5) - NetBSD Manual Pages

Chapter 23. The NetBSD Network Configuration Files

The cron job syntax consists of five fields that specify the time and date of execution, followed by the command or script to run. The fields are: minute, hour, day of month, month, and day of week. Each field can have a specific value, a range, a list, a wildcard (), or a step value. The wildcard () means any possible value for that field. The option B sets the minute field to 0 and the hour field to *, which means the script will run at the 0th minute of every hour, regardless of the day, month, or weekday. This is equivalent to once per hour. The other options are either invalid syntax or do not match the desired frequency. For example, option A sets all fields to *, which means the script will run every minute of every hour of every day, month, and weekday. Option C sets the minute field to * and the hour field to 0, which means the script will run every minute of the 0th hour, or once per day at midnight. Option D has a typo (o instead of *) and option E sets the day of month field to o, which is not a valid value. References:

crontab - FreeBSD crontab(5) Manual Page1

Crontab Explained in Linux [With Examples] - Linux Handbook2

The command pkg_add is used to install binary packages on OpenBSD systems. It is a utility for installing and upgrading software packages from binary files. When using pkg_add, the system will fetch and install the specified package, along with any dependencies it may have123.

References:

OpenBSD manual pages - packages(7)

nixCraft - OpenBSD install or add binary software package using pkg_add

The nice command is used to run a command with a modified scheduling priority, which affects how much CPU time the command receives. The priority can be specified by the -n option, which takes an integer value between -20 and 19, where lower values indicate higher priority. By default, the nice value is incremented by 10, which means the command runs with lower priority than normal. Only the superuser can specify a negative increment, which means the command runs with higher priority than normal. For example, the command nice -n 5 date runs the date command with a priority of 5, while the command nice -n -10 ls runs the ls command with a priority of -10, but only if the user is the superuser. The nice command is useful for running CPU-intensive commands that do not need to finish quickly, or for running commands that need more CPU time than normal. References:

nice - FreeBSD, the manual page for the nice command on FreeBSD.

HowTo: Use ps, kill, nice, and killall To Manage processes in FreeBSD and OS X Unix Operating System - nixCraft, a tutorial on how to use the nice command and other process management commands on FreeBSD and OS X.