The apt-get command  upgrade  will install the newest versions of all currently installed packages without removing any packages or installing new packages that are not already installed.  It will only upgrade packages that can be upgraded without changing the dependencies 1 . The syntax is:  apt-get upgrade .  For example,  apt-get upgrade nginx  will update the nginx package to the latest version available in the repositories, if there is one 2 . The other options are not correct because:

auto-update  is not a valid apt-get command.

dist-upgrade  will also install new packages or remove existing packages if that is required to resolve a package conflict 1 .  It is more aggressive than  upgrade  and may change the system in unexpected ways 3 .

install  will install new packages or upgrade existing packages to the specified version 1 .  It may also install or remove dependencies as needed 4 .

update  will only resynchronize the package index files from the sources, but it will not install or upgrade any packages 1 .  References :

apt-get(8) — apt — Debian buster — Debian Manpages

How to Update Nginx on Ubuntu 18.04 | Linuxize

What is “dist-upgrade” and why does it upgrade more than “upgrade”? - Ask Ubuntu

How to Install Specific Version of Package using apt-get - TecAdmin

 When using rpm --verify to check files created during the installation of RPM packages, the following information is taken into consideration:

Timestamps . RPM compares the modification time of the installed files with the original time stored in the RPM database.  If the file has been modified after installation, the timestamp will differ and RPM will report it with an M flag 1 .

MD5 checksums . RPM calculates the MD5 checksum of the installed files and compares it with the original checksum stored in the RPM database.  If the file has been altered in any way, the checksum will differ and RPM will report it with an 5 flag 1 .

File sizes . RPM compares the size of the installed files with the original size stored in the RPM database.  If the file has been truncated or appended, the size will differ and RPM will report it with an S flag 1 .

RPM does not take into consideration the following information:

Inodes . RPM does not check the inode number of the installed files, as it is not a reliable indicator of file identity.  The inode number can change if the file is moved, copied, or restored from a backup 2 .

GnuPG signatures . RPM does not verify the GnuPG signatures of the installed files, as they are not part of the RPM package format.  The GnuPG signatures are used to verify the authenticity and integrity of the RPM package files before installation, not after 3 .

 The RPM command that will output the name of the package which supplied the file /etc/exports is  rpm -qf /etc/exports .  This command will query the RPM database and find the package that owns or provides the file /etc/exports 1 . The output will show the package name, version, release, and architecture. For example:

The other options are incorrect for the following reasons:

rpm -F /etc/exports .  This command will try to freshen or upgrade the package that contains the file /etc/exports, if it is already installed 2 . This command will not output the package name, but rather install the latest version of the package from a specified source. For example:

rpm -Kl /etc/exports . This command is not valid, as RPM does not have a -Kl option.  The -K option is used to verify the signatures of the RPM package files, not the installed files 3 . The -l option is used to list the files in a package, not to query the package name. For example:

rpm -qp /etc/exports . This command will try to query the package information of the file /etc/exports, as if it was an RPM package file. This command will not output the package name, but rather an error message, as /etc/exports is not a valid RPM package file. For example:

rpm -qi /etc/exports . This command will try to query the information of the package /etc/exports, as if it was an installed package name. This command will not output the package name, but rather an error message, as /etc/exports is not a valid package name. For example:

The /etc/apt/sources.list file is the main configuration file for the Advanced Package Tool (apt), which is used to manage Debian installation package files. This file contains a list of repositories, or sources, from which apt can download and install packages. Each repository is specified by a line that has the following format:

type uri suite [component1] [component2] […]

Where:

type is the access method, such as http, ftp, file, etc.

uri is the Uniform Resource Identifier (URI) of the repository, such as http://deb.debian.org/debian

suite is the distribution code name or archive name, such as stable, testing, unstable, etc.

component is an optional section of the repository, such as main, contrib, non-free, etc.

For example, a typical sources.list file for Debian stable could look like this:

deb http://deb.debian.org/debian stable main contrib non-free deb-src http://deb.debian.org/debian stable main contrib non-free

deb http://deb.debian.org/debian-security/ stable/updates main contrib non-free deb-src http://deb.debian.org/debian-security/ stable/updates main contrib non-free

deb http://deb.debian.org/debian stable-updates main contrib non-free deb-src http://deb.debian.org/debian stable-updates main contrib non-free

The first two lines specify the main repository for Debian stable, with both binary (deb) and source (deb-src) packages. The next two lines specify the security updates repository for Debian stable, which contains important security fixes. The last two lines specify the stable-updates repository, which contains packages that have been updated after the release of Debian stable.

By editing the /etc/apt/sources.list file, one can select the network locations from which Debian installation package files are loaded. However, it is recommended to use a graphical or command-line tool, such as aptitude or synaptic, to manage the sources.list file, as they can handle the syntax and avoid errors.

 The command that lists all currently installed packages when using RPM package management is  rpm --query --all .  This command displays information about all the packages that are currently installed on the system, including their name, version, release, and architecture 1 .  The output can be customized by using various query options and format specifiers 2 .

The other commands are either invalid or related to YUM, not RPM.  yum --query --all is not a valid YUM command, as YUM does not have a --query option 3 .  yum --list --installed is a valid YUM command, but it lists the packages from the YUM repositories, not the RPM database 3 .  rpm --list --installed is not a valid RPM command, as RPM does not have a --list option 2 .

 When removing a package on a system using dpkg package management, the --purge option ensures that configuration files are removed as well. The --purge option is equivalent to the --remove option followed by the --purge-config-files option, which removes any configuration files that are marked as obsolete. The --remove option only removes the package files, but leaves the configuration files intact. The --clean option removes any .deb files from the local cache, but does not affect the installed packages. The --delete option is not a valid option for dpkg.  References:

1 , 102.4 Lesson 1

3 , 101-500 Exam - Free Questions and Answers - ITExams.com

man dpkg

The most likely reason for getting an error when creating a hard link to an ordinary file is that the source and the target are on different filesystems. A hard link is a directory entry that points to the same inode as the original file. An inode is a data structure that stores the metadata and location of a file on a filesystem. A hard link cannot span across different filesystems because each filesystem has its own inode table and numbering scheme. Therefore, a hard link can only refer to a file that exists on the same filesystem as the link.  This is mentioned in the article by How-To Geek 1  and the man page of ln 2 . The other options are not valid reasons for getting an error when creating a hard link. The source file being hidden, read-only, or a shell script does not affect the ability to create a hard link, as long as the user has the appropriate permissions. The source file being already a hard link also does not prevent creating another hard link to the same file, as long as the maximum number of links per inode is not exceeded.  This is explained in the article by Linuxize 3  and the man page of ln

The top-level system directory that is used for files and data that change regularly while the system is running and are to be kept between reboots is /var. The /var directory contains variable data that changes in size as the system runs. For instance, log files, mail directories, databases, and printing spools are stored in /var. These files and data are not temporary and need to be preserved across system reboots.  The /var directory is one of the few directories that are recommended to be on a separate partition, according to the Filesystem Hierarchy Standard (FHS) 1 . This is because the /var directory can grow unpredictably and fill up the / partition, which can cause system instability or failure. By having /var on a separate partition, we can limit the amount of disk space that can be used by variable data and prevent users from affecting the / partition. The /var directory is also a common target for malicious attacks, so having it on a separate partition can improve the security and isolation of the system.  References :

Filesystem Hierarchy Standard

 The dpkg-reconfigure command is used to reconfigure an already installed package. It asks configuration questions for the package, just as if the package were being installed for the first time. This can be useful if the user wants to change some settings or options for the package without reinstalling it. The dpkg-reconfigure command can also be used to fix a broken package configuration or to restore the default settings.  References :

dpkg-reconfigure(8) - Linux man page

Linux Professional Institute: Exam 101 Objectives

The statement that is correct for a command line ending with a & character is that the command is run in background of the current shell. The & character tells the shell to run the command in the background, which means that the shell does not wait for the command to finish and returns the prompt immediately. The command’s output is not redirected to /dev/null, unless explicitly specified. The result of the command does not define if the next command will be run, unless the commands are separated by a logical operator such as & & or ||. The command is not run as a direct child of the init process, unless the shell is the init process itself.  References:  [LPI Exam 101 Detailed Objectives], Topic 103: GNU and Unix Commands, Weight: 25, Objective 103.1: Work on the command line, Background Processes