• Home
• Linux Foundation Exams
• LFCS - Linux Foundation Certified System Administrator

LFCS Linux Foundation Practice Test Questions and Exam Dumps 

Question 1

What of the following can be done by the command ifconfig? (Choose TWO correct answers.)

A. Set a network interface active or inactive.
B. Specify the kernel module to be used with a network interface.
C. Allow regular users to change the network configuration of a network interface.
D. Change the netmask used on a network interface.
E. Specify which network services are available on a network interface.

Answer: A, D

Explanation:

The ifconfig command is a traditional Unix/Linux utility used to configure, manage, and query network interface parameters. Although it has largely been replaced by the ip command in modern distributions, it is still widely understood and used in many systems. Two of the correct functionalities of ifconfig are:

Setting a network interface active or inactive:
This is done using the up and down options. For example:

ifconfig eth0 up

ifconfig eth0 down

These commands respectively activate and deactivate the network interface eth0. This is a basic administrative function that allows system administrators to control network availability. Setting an interface active (or up) enables it to transmit and receive data, while setting it inactive (or down) disables it.

Changing the netmask used on a network interface:
The netmask parameter can be specified to define the subnet mask used for the interface. This determines which portion of an IP address identifies the network and which part identifies the host. For example:

ifconfig eth0 netmask 255.255.255.0

This sets the subnet mask for the eth0 interface. This configuration is crucial for proper IP address management and routing within a subnet.

Now, let’s examine why the other options are incorrect:

B. Specify the kernel module to be used with a network interface:
This task is beyond the scope of ifconfig. Kernel module management is typically done using tools like modprobe, insmod, or system configurations under /etc/modprobe.d/. ifconfig does not interact with kernel modules directly; it only configures interfaces that are already available.

C. Allow regular users to change the network configuration of a network interface:
Network configuration changes via ifconfig require administrative privileges. Ordinary users cannot bring interfaces up or down or change IP settings unless granted specific permissions through mechanisms like sudo. Therefore, ifconfig itself does not inherently provide the ability for regular users to perform these tasks.

E. Specify which network services are available on a network interface:
The ifconfig command deals strictly with network interface configuration, not with service-level management. Determining which services (such as HTTP, SSH, or FTP) are available or active on a network interface is typically handled through firewalls (e.g., iptables, nftables) or service configuration files, not via ifconfig.

In conclusion, ifconfig is capable of setting a network interface's operational status and modifying basic configuration parameters like the netmask. These are both essential for basic network management, making A and D the correct answers.

Question 2

Which of the following commands can be used to locate programs and their corresponding man pages and configuration files?

A. dirname
B. which
C. basename
D. query
E. whereis

Answer: E

Explanation:

The correct command that can locate a program along with its corresponding man pages and configuration files is whereis.

Let’s break down why this is the correct answer and examine each of the options:

E. whereis – Correct Answer

The whereis command is specifically designed to search for the binary, source, and manual sections of a program. For example:

whereis ssh

Might output:

ssh: /usr/bin/ssh /etc/ssh /usr/share/man/man1/ssh.1.gz

This shows:

• The binary location: /usr/bin/ssh

• The configuration directory: /etc/ssh

• The manual page: /usr/share/man/man1/ssh.1.gz

This comprehensive output makes whereis a very useful tool for administrators and users trying to locate all related components of a command or application.

A. dirname – Incorrect

The dirname command is used to extract the directory path from a given pathname. It does not locate any files or provide information about binaries or man pages. Example:

dirname /usr/bin/ssh

Would output:

/usr/bin

It only isolates the directory part of a path—it doesn’t locate programs.

B. which – Partially useful, but Incorrect

The which command is often used to identify the location of an executable binary in the user's path. For example:

which ssh

Might return:

/usr/bin/ssh

However, it only locates the binary and does not show man pages or configuration files. So, while useful, it does not meet the full requirements of the question.

C. basename – Incorrect

Like dirname, the basename command extracts the filename from a given path. For example:

basename /usr/bin/ssh

Returns:

ssh

It does not perform any search or location task and has no awareness of where a file is stored or its related man pages.

D. query – Incorrect

query is not a standard Linux command for this purpose. While some package managers (like rpm or dpkg) include commands like rpm -q or dpkg-query, query by itself is not recognized as a utility for locating binaries or man pages on a typical Linux system.

The only command among the options that can locate binaries, man pages, and often configuration files is whereis. Therefore, E is the correct answer. It is particularly useful for system administrators who need a quick overview of where all components related to a program are located.

Question 3

Which of the following options for the kernel's command line changes the systemd boot target to rescue.target instead of the default target?

A. systemd.target=rescue.target
B. systemd.runlevel=rescue.target
C. systemd.service=rescue.target
D. systemd.default=rescue.target
E. systemd.unit=rescue.target

Answer: E

Explanation:

In Linux systems using systemd as the init system, the kernel command line can be used to specify which systemd target to boot into. A target in systemd is a unit that groups together units to achieve a certain state, similar to runlevels in traditional SysVinit systems.Ubuntu Manpages+1LinuxConfig+1ArchWiki+1Ubuntu Manpages+1

To boot into rescue.target, which is a special target unit that provides a minimal environment for system recovery, the correct kernel command line parameter is:LinuxConfig+8freedesktop.org+8Ubuntu Manpages+8

systemd.unit=rescue.target

This parameter tells systemd to start the system in rescue mode, which is akin to single-user mode, providing a minimal environment with essential services for system maintenance. Additionally, for compatibility with SysVinit, the number 1 can be used as an alias:freedesktop.org+6LinuxConfig+6freedesktop.org+6Ubuntu Manpages+3freedesktop.org+3freedesktop.org+3

systemd.unit=1

This is equivalent to specifying systemd.unit=rescue.target.LinuxConfig+4freedesktop.org+4freedesktop.org+4

Let's examine why the other options are incorrect:

• A. systemd.target=rescue.target: This is not a valid kernel command line parameter. The correct parameter is systemd.unit=rescue.target.

• B. systemd.runlevel=rescue.target: While runlevel is a concept from SysVinit, systemd does not use this parameter. The appropriate systemd parameter is systemd.unit.ArchWiki

• C. systemd.service=rescue.target: This is not a valid kernel command line parameter. The systemd.service parameter is used to specify a service to start, not a target.

• D. systemd.default=rescue.target: The systemd.default parameter is not used to specify the boot target. The correct parameter is systemd.unit.

In summary, to change the systemd boot target to rescue.target, the correct kernel command line parameter is systemd.unit=rescue.target.

Question 4

What is the output of the following command?
echo "Hello World" | tr -d aieou

A. Hello World
B. eoo
C. Hll Wrld
D. eoo Hll Wrld

Answer: C

Explanation:

The command provided uses the tr (translate) command, which is used to perform character-based transformations or deletions in a stream of text.

Let’s break down the command:

echo "Hello World" | tr -d aieou

• echo "Hello World": This command outputs the string "Hello World".

• |: This is the pipe operator, which passes the output of the echo command as input to the tr command.

• tr -d aieou: The tr command with the -d option deletes characters from the input stream. The characters specified (in this case, a, i, e, o, u) are deleted from the input text.

Step-by-step transformation:

The string "Hello World" is passed to tr -d aieou. The command will delete all instances of the vowels a, i, e, o, and u.

• The original string is "Hello World".

• After removing the vowels (a, i, e, o, u), the string becomes:
  "Hll Wrld"

Thus, the final output after the transformation is "Hll Wrld".

The correct output is C. Hll Wrld.

Question 5

Which command can be used to display the inode number of a given file?

A. inode
B. ls
C. ln
D. cp

Answer: B

Explanation:

To understand the correct command for displaying the inode number of a given file, it’s essential to first know what an inode is. An inode is a data structure used by many file systems to store information about a file, except its name and its actual data. It contains metadata about the file, such as its size, owner, permissions, and location of the actual data blocks. The inode number is a unique identifier for a file within the file system.

The options provided relate to commands that are commonly used for file operations in Unix-like operating systems, so let’s analyze each:

• A. inode
  This is not a valid command in Unix or Linux. There is no standalone command named "inode" for displaying the inode number of a file.

• B. ls
  This is the correct answer. The ls command is typically used to list directory contents, but with the -i option, it can also display the inode number of a file. The syntax would be:
  ls -i filename
  This will show the inode number along with the file name. For example, running ls -i myfile.txt might output something like 12345678 myfile.txt, where 12345678 is the inode number of the file.

• C. ln
  The ln command is used to create links between files, not to display inode numbers. You can use ln to create hard links, which are references to the same inode, but it does not display inode numbers.

• D. cp
  The cp command is used to copy files or directories. It does not display inode numbers. It’s used for duplicating files or directories to different locations in the file system.

In summary, the command ls -i is specifically designed to display the inode number of a file, which makes B the correct answer.

Question 6

Which command will change the quota for a specific user?

A. edquota
B. repquota
C. quota -e
D. quota

Answer: A

Explanation:

In Unix-like operating systems, disk quotas are a way of limiting the amount of disk space a user or group can consume. The system administrator can set and manage these quotas to prevent users from using excessive disk space. To change a user’s quota, you need to use the appropriate command designed for modifying or adjusting these limits.

Let's break down each option:

• A. edquota
  The edquota command is specifically designed to edit and change the disk quota for users or groups. When run with the username as an argument, it opens an editor (usually vi or another text editor) that allows administrators to modify the quota settings for the specified user. Through this tool, administrators can change the soft and hard limits on disk space and the number of inodes allocated to the user. Therefore, A is the correct choice for changing a user’s quota.

• B. repquota
  The repquota command is used to report the disk usage and quota information for file systems that have quotas enabled. It displays information about how much disk space and how many inodes are being used by users and groups. However, it does not allow you to modify or change any quotas. It is simply for reporting, not for modifying settings, so B is not the correct answer.

• C. quota -e
  The quota -e command is used to show the disk quota usage in a more human-readable format, typically by displaying the usage in terms of block sizes and number of files. It does not modify quotas. It’s mainly a way to view current usage rather than alter quotas. Therefore, C is not the correct choice for changing a user's quota.

• D. quota
  The quota command is used to display the current disk usage and quota limits for a user. It shows how much disk space a user has used and how much they can still use within the assigned limits. While quota allows users to see their quota, it does not allow administrators to change the quota. Therefore, D is not the correct choice for modifying a user’s quota.

In summary, A. edquota is the correct command to change the quota for a specific user, as it provides the functionality to edit user quotas directly.

Question 7

When using rpm --verify to check files created during the installation of RPM packages, which of the following information is taken into consideration? (Choose THREE correct answers.)

A. Timestamps
B. MD5 checksums
C. Inodes
D. File sizes
E. GnuPG signatures

Correct Answers: B, C, D

Explanation:

The rpm --verify command is used to check the integrity of files that were installed via RPM packages. When the verification process runs, it compares the current state of the installed files with the information that was stored during the installation. The verification process uses several attributes of the files to ensure that they have not been tampered with or corrupted. Let's look at the different factors that come into play.

• A. Timestamps: During installation, the system records the timestamp of when each file is installed or modified. This timestamp is compared during verification to ensure that files haven't been altered after the installation. If the timestamp is different from the expected one, it indicates that the file may have been modified, corrupted, or tampered with. Therefore, timestamps are indeed a part of the verification process.

• B. MD5 checksums: The MD5 checksum is a unique identifier that is calculated for each file during installation. This checksum is used to verify the file's integrity by comparing the stored checksum with the current checksum of the file. If they don't match, it suggests that the file has been altered. The MD5 checksum is critical for verifying that files remain unaltered and is included in the verification process. Thus, MD5 checksums are involved in the verification process.

• C. Inodes: An inode is a data structure on the file system that stores information about a file or directory, such as its owner, permissions, and the location of the data blocks. When rpm --verify runs, it does check the inode information to ensure that the file is still pointing to the correct data on the disk. If the inode information changes, it could indicate that the file has been altered in some way, so inodes are also included in the verification check.

• D. File sizes: File sizes are another attribute that the RPM package manager uses during verification. The file size is checked against the value stored during the installation to ensure that the file hasn't grown or shrunk unexpectedly. A change in file size could indicate that data has been added or removed, which is a clear sign of alteration. Thus, file sizes are part of the verification process.

• E. GnuPG signatures: While GnuPG signatures are used during the installation of an RPM package to verify the authenticity of the package (to ensure it was signed by a trusted source), they are not directly involved in the post-installation verification process when running rpm --verify. The rpm --verify command does not check GnuPG signatures as part of its file integrity check. Therefore, GnuPG signatures are not taken into consideration during the verification step.

To summarize, when using the rpm --verify command, the system checks attributes like timestamps, MD5 checksums, inodes, and file sizes to ensure that files have not been altered or corrupted after installation. However, GnuPG signatures, which are primarily used for package authenticity during installation, are not part of the verification process.

Question 8

Which of the following SQL queries counts the number of occurrences for each value of the field order_type in the table orders?

A. SELECT order_type,COUNT() FROM orders WHERE order_type=order_type;
B. SELECT order_type,COUNT() FROM orders GROUP BY order_type;
C. COUNT(SELECT order_type FROM orders);
D. SELECT COUNT(*) FROM orders ORDER BY order_type;
E. SELECT AUTO_COUNT FROM orders COUNT order_type;

Correct Answer: B

Explanation:

When you want to count the occurrences of each value in a specific field of a database table, you typically use the COUNT() function in SQL, which is used to count rows in a result set. The key point is how to properly group the data by the field you want to analyze, and how to use the GROUP BY clause correctly.

Let's break down each option to see which query will correctly count the occurrences of each value in the order_type field from the orders table:

• A. SELECT order_type,COUNT(*) FROM orders WHERE order_type=order_type;
  This query includes a WHERE clause with the condition order_type=order_type, which is essentially always true and doesn't filter the rows in any meaningful way. It does not group the data, so it will only return a single count of all rows, not the count for each order_type. Therefore, this query is incorrect for the intended task.

• B. SELECT order_type,COUNT(*) FROM orders GROUP BY order_type;
  This query correctly uses the COUNT() function to count the occurrences of each order_type and groups the results by order_type. The GROUP BY clause is essential because it organizes the rows into groups based on the order_type, and then the COUNT(*) function counts the number of rows in each group. This is the correct query to count the occurrences of each value of order_type. Therefore, this is the correct answer.

• C. COUNT(SELECT order_type FROM orders);
  This is syntactically incorrect. You cannot use COUNT() with a subquery in this manner. The COUNT() function is designed to operate on a column or a result set, but not directly on a subquery without proper syntax. This query will result in an error.

• D. SELECT COUNT(*) FROM orders ORDER BY order_type;
  This query counts the total number of rows in the orders table, but it does not count occurrences of each value of order_type. Additionally, the ORDER BY clause is unnecessary in this context, as you are not grouping or filtering the rows. Therefore, this query does not achieve the intended result.

• E. SELECT AUTO_COUNT FROM orders COUNT order_type;
  This query is syntactically incorrect and does not follow proper SQL conventions. There is no AUTO_COUNT function or column, and the syntax of this query is invalid. It will result in an error.

To summarize, B is the correct query because it uses the GROUP BY clause to group the rows by order_type and counts the number of occurrences of each value in that field. This is the correct and standard way to count the occurrences for each value in a column in SQL.

Question 9

Which of the following keywords can be used in the file /etc/resolv.conf? (Choose TWO correct answers.)

A. substitute
B. nameserver
C. search
D. lookup
E. method

Correct Answers: B, C

Explanation:

The /etc/resolv.conf file is used in Unix-like systems (such as Linux) to configure DNS (Domain Name System) resolver settings. This file contains important information for resolving domain names into IP addresses and defines how the system will interact with DNS servers.

Let's explore the different options to understand which keywords are valid for use in the /etc/resolv.conf file:

• A. substitute: The keyword substitute is not a valid option in /etc/resolv.conf. This file doesn't include any setting or keyword named substitute. It is not used to configure substitution rules or anything related to it. Thus, this is not a valid keyword.

• B. nameserver: The nameserver keyword is a valid entry in /etc/resolv.conf. It specifies the IP address of a DNS server that the system should use for name resolution. You can list multiple nameserver entries if you want to specify backup DNS servers. For example, nameserver 8.8.8.8 would set Google's DNS server as the resolver. Therefore, this is a correct keyword.

• C. search: The search keyword is also valid in /etc/resolv.conf. It is used to specify a search domain, which is appended to domain names that are queried. For example, if the search domain is set to example.com, and you try to resolve host, it will first attempt to resolve host.example.com. This is commonly used in environments where short names are often used. Thus, this is another correct keyword.

• D. lookup: The lookup keyword is not used in /etc/resolv.conf. It does not exist in the list of valid keywords for this configuration file. Typically, DNS resolution is done based on the nameserver and search entries, and the lookup keyword is not required. Therefore, this is not a valid keyword.

• E. method: Similarly, the method keyword is not valid in /etc/resolv.conf. This file does not have a method keyword for DNS configuration. It focuses on specifying DNS servers and search domains. Hence, this is not a valid keyword.

To summarize, the valid keywords for configuring DNS settings in the /etc/resolv.conf file include nameserver to define DNS servers and search to specify search domains. Other keywords, such as substitute, lookup, and method, are not valid options in this configuration file.