Free 1Z0-106 Practice Test

The provided udev rule KERNEL=="hdb", DRIVER=="ide-disk", SYMLINK+="sparedisk" is processed based on a set of conditions and an action. The comma separating the key-value pairs acts as a logical AND operator. Therefore, the rule will only trigger if a device event occurs where the kernel-assigned name is "hdb" and the device is using the "ide-disk" driver. The SYMLINK+="sparedisk" directive instructs udev to create a symbolic link named /dev/sparedisk that points to the actual device node, which is /dev/hdb. This does not rename the original device node; it only provides an additional, persistent name.

A. The += operator adds a value to a list for the current device; the term "overwriting" is imprecise for how udev manages the /dev namespace.
B. The SYMLINK key creates a symbolic link, it does not rename the device. The NAME key is used for renaming the device node itself.
E. The comma separating match keys in a udev rule implies a logical AND, not an OR. Both conditions must be true for the rule to be applied.

1. udev(7) man page: "A rule is a set of one or more key-value pairs. If all keys match their values, the rule is applied... KERNEL==: Match the kernel name for the device... DRIVER==: Match the driver name for the device... SYMLINK=: The name of a symbolic link to be created for the device node." This confirms that all conditions must match (AND logic) and that SYMLINK creates a link, not a rename. (Source: man udev.rules(7) on Oracle Linux 7/8).

2. Oracle Linux 7 Documentation, Administrator's Guide, Chapter 26. Managing Devices with udev, Section 26.2. Udev Rules: "All conditions in a rule must be met for the rule to be applied... The SYMLINK key is used to create a symbolic link to the device node." This official vendor documentation confirms the AND logic of the rule and the function of the SYMLINK key.

3. Red Hat Enterprise Linux 7, Storage Administration Guide, Chapter 5. Managing Storage Devices with udev: "A udev rule is composed of one or more key-value pairs separated by a comma... SYMLINK: create a symbolic link to the device node." As Oracle Linux is derived from RHEL, this source is authoritative and corroborates that the comma implies an AND condition and that SYMLINK creates a link, leaving the original kernel name (/dev/hdb) intact.

The standard procedure for removing a physical volume (PV) from a volume group (VG) requires two key considerations. First, the VG's metadata must be updated to reflect the removal of the PV. This is accomplished using the vgreduce command, making it a mandatory step before the PV is considered fully removed from the LVM configuration (A). Second, a primary feature of LVM is its support for online administration. It is possible to migrate all data extents off a specific PV using pvmove and then use vgreduce to remove it from the VG, all while the VG and its logical volumes remain active and mounted. This capability is crucial for maintenance tasks like replacing disks without downtime (E).

B. The vgexport command is used to prepare an inactive VG for removal or migration to another system; it cannot be run on an active VG with mounted file systems.
C. This is incorrect. LVM is designed to allow for the online removal of a PV from an active VG, typically by first migrating its data with pvmove.
D. The ability to remove a PV depends on whether it contains any allocated extents, not on the active/inactive status of logical volumes that may reside on other PVs.

1. Oracle® Linux 7: Administrator's Guide, Section 10.3.5. "Removing Physical Volumes from a Volume Group". The documentation outlines the procedure using pvmove followed by vgreduce, and the examples do not require deactivating the volume group, confirming that the operation can be done on an active VG.

2. Red Hat Enterprise Linux 8: Configuring and managing logical volumes, Section 4.4.8. "Removing physical volumes from a volume group". This official documentation states, "If there are logical volumes on the physical volume, you must move the data from the physical volume before you can remove it. You can use the pvmove command to move the data from the physical volume while your system is running." This explicitly confirms that a PV can be removed from an active VG.

3. LVM HOWTO, Section 5.6. "Removing disks from a volume group". This foundational guide details the process: "1. Use pvmove to move the allocated extents off the PV(s). 2. Use vgreduce to remove the PV(s) from the VG. 3. Use pvremove to remove the LVM metadata from the PV(s)." The context of pvmove is for online data migration, reinforcing that the VG can be active.

The dmesg -T (or --ctime) command is used to print kernel ring buffer messages with human-readable timestamps. This option converts the kernel's internal timestamp, which is typically the number of seconds since boot, into a standard wall-clock time format (e.g., [Tue May 21 10:30:00 2024]). This functionality is crucial for administrators who need to correlate kernel events with other system logs or real-world time, especially during troubleshooting and system analysis.

A. dmesg -t (--notime) suppresses the printing of timestamps, which is the opposite of the desired outcome.
B. dmesg -x (--decode) decodes facility and level (priority) numbers into human-readable prefixes, but it does not affect the timestamp format.
D. dmesg -W (--follow) waits for new messages to be added to the kernel ring buffer and prints them as they appear, similar to tail -f.

1. Oracle Linux 8 Documentation, dmesg(1) Manual Page: "-T, --ctime Print human-readable timestamps. The timestamp could be inaccurate! The time source used for the logs is not updated after system SUSPEND/RESUME."

2. The Linux man-pages project, dmesg(1): "-T, --ctime Print human-readable timestamps. Be aware that the timestamp could be inaccurate! The time source used for the logs is not updated after system SUSPEND/RESUME." This source also confirms the functions of -t, -x, and -W as described above.

The anacron utility is designed for systems that are not running continuously, such as laptops or desktops. Its configuration file, /etc/anacrontab, specifies job frequency in days, meaning the highest frequency a job can run is once per day. The primary purpose of anacron is to ensure that periodic system jobs (e.g., daily, weekly, monthly scripts typically managed by cron) are executed even if the system was powered off at their scheduled time. It checks timestamps to see if a job was missed and runs it if necessary after the system boots.

A. cron's minimum scheduling granularity is one minute, but jobs can be scheduled for any longer interval (e.g., hourly, daily), not only once a minute.
B. This is incorrect. User-specific crontabs are located in /var/spool/cron, and the main system-wide crontab is /etc/crontab.
C. The crond daemon reads jobs from /etc/crontab, the /etc/cron.d/ directory, and the user-specific spool directory (/var/spool/cron).

1. Oracle Linux 8 Documentation, Managing Core System Configuration, Chapter 10. Automating System Tasks. The documentation states, "The anacron utility is similar to crond but is intended for systems that are not running continuously." It also describes the /etc/anacrontab format as period-in-days delay-in-minutes job-identifier command, confirming the minimum period is one day.

2. anacron(8) Linux manual page. "Anacron can be used to execute commands periodically, with a frequency specified in days... For each job, Anacron checks whether this job has been executed in the last n days, where n is the period specified for that job. If not, Anacron runs the job's shell command..." This confirms options D and E.

3. crontab(5) Linux manual page. This page details the file format for cron jobs, showing the time fields are "minute, hour, day of month, month, day of week," which establishes the one-minute minimum granularity but does not restrict jobs to only that frequency, making option A incorrect. It also specifies the locations for crontab files, refuting options B and C.

The dnf info command is used to display detailed information about a package. The output provided in the question, which includes fields like Name, Version, Release, Size, Source, Repository, and a full Description, is the standard format for this command. DNF is capable of resolving a file path, such as /usr/bin/gzip, to the package that owns it (gzip) and then displaying the detailed information for that specific package. The "Installed Packages" heading confirms that information for a package on the local system is being displayed.

A. dnf list /usr/bin/gzip: This command lists packages in a brief, tabular format (typically one line per package), not the detailed, multi-line block shown.
B. dnf provides /usr/bin/gzip: This command identifies which package owns a file, but its output is a concise listing of the package name and summary, not the full details.
D. dnf search /usr/bin/gzip: This command searches package metadata for a keyword and returns a list of matching packages with their summaries, not detailed information for one specific package.

1. Oracle® Linux 8: Managing Software on Oracle Linux

Section 2.3.5 Displaying Package Information.

This official Oracle documentation states

"To display more detailed information about a package

use the dnf info command." The example output provided in the documentation for dnf info precisely matches the structure and fields shown in the question.

2. dnf(8) Linux manual page

COMMANDS section.

The man page for the dnf utility describes the info command as follows: "Display details about a package or a group of packages." This aligns with the detailed output provided. In contrast

it describes list as listing packages

provides as finding the package for a file

and search as searching metadata for keywords

all of which produce different output formats.

The /proc filesystem is a virtual filesystem that provides a direct interface to kernel data structures. It contains numerous files that report on the system's state, including /proc/cpuinfo for detailed processor information and /proc/meminfo for memory usage statistics. Similarly, the /sys filesystem (sysfs) exports information from the kernel's device model to user space in a structured way. It also contains detailed information about core hardware, with CPU topology and control files located under /sys/devices/system/cpu/ and memory block information under /sys/devices/system/memory/. Both filesystems serve as sources for CPU and memory information, though they present it differently.

B. sys contains a list of running processes. Incorrect. The /proc filesystem contains directories corresponding to each running process ID (PID), not /sys.
D. proc contains a list of network drivers. Incorrect. The /sys filesystem provides a structured view of devices and their associated drivers, for example, under /sys/class/net/.
E. sys contains a list of mounted devices. Incorrect. The list of mounted filesystems is found in /proc/mounts. /sys shows all detected devices, regardless of their mount status.

1. Oracle® Linux 7 Documentation: Administrator's Guide, Chapter 27, "Working with the /proc File System". Section 27.2, "Important /proc Files and Directories," explicitly lists /proc/cpuinfo and /proc/meminfo as key files for retrieving system hardware information.

2. The Linux Kernel Documentation: The sysfs Filesystem. The official kernel documentation describes the layout of sysfs, detailing the /sys/devices/system/ hierarchy which contains the cpu and memory subdirectories for managing and viewing information about those subsystems. (Available at kernel.org/doc/html/latest/filesystems/sysfs.html).

3. proc(5) Linux Manual Page: The man page states, "The proc filesystem is a pseudo-filesystem which provides an interface to kernel data structures... It contains... information about the system, such as /proc/cpuinfo and /proc/meminfo."

4. Red Hat Enterprise Linux 7 Documentation: Kernel Administration Guide, Chapter 5, "The sysfs filesystem". This guide explains that sysfs provides information about devices and drivers, and specifically mentions that CPU topology is exposed under /sys/devices/system/cpu/ and memory blocks under /sys/devices/system/memory/.

The /etc/sysconfig directory in Oracle Linux 8 contains static configuration files and scripts that control the behavior of system services and utilities. When a software package that provides a system service (e.g., chronyd, sshd, network-scripts) is installed, it often places a corresponding configuration file in this directory. For example, installing the chronyd package creates /etc/sysconfig/chronyd. Therefore, the contents of the /etc/sysconfig directory are directly dependent on which packages are installed on the system, allowing administrators to customize service parameters.

A. Device and driver information is dynamically exposed through the /sys and /proc virtual filesystems, not stored in /etc/sysconfig.
B. Information about running processes is located in the /proc virtual filesystem, with each process having a subdirectory named by its process ID.
D. System hardware information is made available by the kernel through virtual filesystems like /proc (e.g., /proc/cpuinfo) and /sys.

1. Oracle Linux 8 Documentation: In the "Managing Core System Configuration" guide

the description of the /etc directory states it contains system configuration files. The /etc/sysconfig subdirectory is a convention in RHEL-based distributions like Oracle Linux for holding configuration files for services installed by packages. For instance

the networking service configuration is detailed in /etc/sysconfig/network-scripts/

which is provided by the network-scripts package.

Source: Oracle® Linux 8: Managing Core System Configuration

Chapter 1

"About System Configuration Files".

2. systemd Documentation (man pages): The systemd.exec(5) man page

which is part of the official Oracle Linux 8 system documentation

describes the EnvironmentFile= directive used in service unit files. This directive often points to a file in /etc/sysconfig to load service-specific configuration variables. This establishes a direct link between a service (installed by a package) and its configuration file in /etc/sysconfig.

Source: man systemd.exec

Section "EnvironmentFile="

Oracle Linux 8.

3. Red Hat Enterprise Linux 8 Documentation: As Oracle Linux is derived from RHEL

its documentation is highly relevant. The "Configuring and managing networking" guide explicitly details the role of files within /etc/sysconfig/network-scripts. The presence and content of these files depend on the network-scripts package being installed and the network interfaces configured.

Source: Red Hat Enterprise Linux 8 Documentation

"Configuring and managing networking

" Section 2.3

"Configuring an Ethernet connection using ifcfg files".

The journalctl command is used to query and display logs from the systemd journal. B: The -p or --priority option filters messages by a specified priority level and all levels that are more severe. Specifying -p err (priority 3) will display messages logged at the err, crit (2), alert (1), and emerg (0) levels. While the wording "only error log level" is imprecise, it is interpreted in this context as filtering based on the error level, which is correct. D: The -k or --dmesg flag is a shortcut to show only kernel messages. This option implicitly applies the -b flag, which restricts the output to messages from the current boot only. E: The -p option accepts numerical priority values. info corresponds to priority 6. Therefore, journalctl -p 6 will display all messages with a priority of 6 (info) or a more severe priority (0-5).

A. The command will not fail. The -b flag shows logs from the current boot, which are stored in memory (/run/log/journal) and are available even if persistence to /var/log/journal is not configured.
C. This command shows messages in the notice and warning priority range from all available journals. It does not limit the output to only the last boot, as the -b flag was not specified.

1. systemd Project

journalctl Manual Page:

For options B and E: "-p

--priority= Filter output by message priorities. ... If a single priority is specified

all messages with this or a more important priority are shown. ... The priorities are the usual syslog priorities as documented in syslog(3)

i.e. "emerg" (0)

"alert" (1)

"crit" (2)

"err" (3)

"warning" (4)

"notice" (5)

"info" (6)

"debug" (7)."

For option D: "-k

--dmesg Show only kernel messages. This implies -b and adds the match TRANSPORT=kernel."

For options A and C: "-b [[ID][±offset]]

--boot=[[ID][±offset]] Show messages from a specific boot. ... The argument may be empty

in which case logs for the current boot will be shown."

Source: freedesktop.org

journalctl(1) man page.

2. Oracle® Linux 8 Documentation

Managing Core System Configuration:

Section 12.3.2. Filtering Log Output: "To view only kernel messages

use the -k or --dmesg option. By default

this command displays kernel messages from the current boot." This supports option D.

Section 12.3.2. Filtering Log Output: "To filter output by message priority

use the -p or --priority option. You can use either the name or the corresponding number for the priority level... For example

to view only messages with a priority of error or higher

type: sudo journalctl -p err -b" This supports the functionality described in options B and E.

Source: Oracle Linux 8 Documentation

Chapter 12. Managing Log Files With journald.

The AutoFS service automatically mounts a filesystem upon access and is designed to unmount it after a period of inactivity (the idle timeout). In the described scenario, the first session changes its current working directory (CWD) into the AutoFS-managed directory, which triggers the mount. Because the shell process in the first session maintains its CWD within this mounted filesystem, the filesystem is considered "in use" or "busy". The automount daemon will not unmount a busy filesystem, even after the idle timeout expires. The filesystem will only be unmounted after it is no longer busy and the subsequent idle timeout period passes. The "busy" state is released when the process (the shell) either changes its CWD to a location outside the mount point or terminates (e.g., by logging out).

A. AutoFS is specifically designed to unmount idle filesystems to conserve resources; they do not persist for the entire system uptime unless constantly in use.
C. The filesystem cannot be unmounted when the timer expires because the shell's CWD in the first session keeps the resource busy.
D. Actions in a second, unrelated session and directory (/etc) have no impact on the mount status of the filesystem used by the first session.

1. Oracle Linux 8 Documentation

Managing Storage Devices

Chapter 20. Automounting File Systems with AutoFS: The documentation explains the timeout mechanism. While it doesn't explicitly detail the "busy" state in the introductory sections

the underlying umount behavior it relies on prevents unmounting a filesystem that is in use (e.g.

by a process's CWD). The core principle is that unmounting only occurs on idle filesystems.

Reference: Oracle® Linux 8: Managing Storage Devices

Section 20.1

"About AutoFS".

2. autofs(5) Linux man page: This primary source document describes the behavior of the automounter. A key operational principle is that busy filesystems are not unmounted.

Quote: "The automounter will not unmount a filesystem that is in use." A shell's CWD within a mount point defines it as "in use".

3. University of Washington

CSE 451

Introduction to Operating Systems Courseware: Academic materials on Linux/UNIX filesystems corroborate this behavior.

Reference: Lecture notes on Network File Systems often describe AutoFS behavior

stating: "Autofs will not unmount a filesystem if any process has it as its current working directory

or has any open file in it." This directly supports why the filesystem remains mounted in the scenario.

An rsyslog rule defines how to process a specific log message and consists of two fundamental components. The first is a filter (also known as a selector), which specifies the conditions a message must meet to be selected, such as its facility (e.g., kern, mail) and priority level (e.g., info, err). The second component is the action, which defines what to do with the selected message, such as writing it to a specific file, sending it to a remote server, or discarding it. This filter-action structure forms the basis of all rules in the rsyslog.conf file.

C. parser: A parser is a component that interprets the structure and content of a log message, but it is not a direct part of the rule's filter/action syntax.
D. module: Modules extend rsyslog functionality (e.g., for input or output). While an action may utilize a module, the module itself is not a primary component of the rule's syntax.
E. security policy: A security policy is a high-level set of rules and procedures. It is not a syntactic component used to construct an individual rsyslog rule.

1. Oracle Linux 8 Documentation: Managing Core System Configuration, Chapter 22. Viewing and Managing Log Files, Section 22.3.1. Understanding the rsyslog.conf file format. The documentation states, "Each rule consists of two fields: a selector field and an action field... The selector field, also called a filter, specifies a message source and a priority level."

2. rsyslogd Official Documentation: The documentation for rsyslog.conf format specifies the basic rule structure. "Every rule line consists of two parts: a selector and an action... The selector, now also called filter, specifies which messages to select for the action." (Reference: rsyslog.com, Documentation, Configuration, rsyslog.conf).

3. Linux man pages: The rsyslog.conf(5) man page, available on Oracle Linux systems, describes the rule format. Under the "RULES" section, it details that lines are composed of a "Filter Part" and an "Action Part".