Free Preparation Discussions
MENU
LPI 010-160 Exam Questions
- Topic 1: The Linux Community and a Career in Open Source: This section of the exam measures skills of an Aspiring Open Source Developer and covers the history and growth of Linux along with its major distributions, embedded uses like Raspberry Pi, and its role in cloud computing. It also requires familiarity with prominent open source applications across desktop, server, and development contexts, including package management tools. Additionally, it addresses open source philosophy and licensing principles, and evaluates basic ICT skills relevant to working within Linux environments.
- Topic 2: Finding Your Way on a Linux System: Aimed at the Junior Linux System Administrator, this domain evaluates competence using the Linux command line. Candidates must demonstrate an understanding of shell syntax, environment variables, and quoting conventions. They are expected to navigate help systems such as man and info pages, manipulate directories and files through absolute and relative paths, and perform basic file operations including creation, movement, and deletion.
- Topic 3: The Power of the Command Line: This section measures the abilities of a Linux Script Developer and focuses on archive management using tools like tar and gzip, as well as data searching and filtering via utilities such as grep and cut. It also assesses the capacity to transform repetitive commands into simple shell scripts, employing constructs such as shebang lines, loops, variables, and error handling to automate tasks.
- Topic 4: The Linux Operating System: Targeted at the IT Support Technician, this domain covers the selection of operating systems and their life cycles, differences between major OS types, and essential hardware components including storage and drivers. It further explores how data is stored and logged in a Linux system, and mandates competence in querying network configurations, understanding TCP/IP concepts, and verifying connectivity using basic networking tools.
- Topic 5: Security and File Permissions: This section evaluates the expertise of a Linux Security Administrator in user and group management, permission structures, and directory security. It addresses root and system user distinctions, account creation and modification processes, and manipulation of file ownership and permission settings. Knowledge of special directories, symbolic links, and the behaviour of sticky bits completes the required security skill set.
Free LPI 010-160 Exam Actual Questions
Note: Premium Questions for 010-160 were last updated On Sep. 21, 2026 (see below)
Which of the following examples shows the general structure of a for loop in a shell script?
The general structure of a for loop in a shell script is as follows12:
for variable in list do commands done
The variable is the name of a loop counter or iterator that takes on the values of the items in the list. The list can be a sequence of words, numbers, filenames, or the output of a command. The commands are the body of the loop that are executed for each value of the variable. The do and done keywords mark the beginning and the end of the loop body.
The option C. for file in *.txt do echo $i done follows this structure, with the variable being file, the list being *.txt (which matches all the files with the .txt extension in the current directory), and the command being echo $i (which prints the value of the variable i, which is presumably set somewhere else in the script).
The other options are incorrect because:
A . for *.txt as file => echo $file uses an invalid syntax for a for loop. The as keyword is not part of the shell script syntax, and the => symbol is not a valid operator. The correct way to write this loop would be:
for file in *.txt do echo $file done
B . for *.txt ( echo $i ) uses an invalid syntax for a for loop. The parentheses are not part of the shell script syntax, and the loop body is missing the do and done keywords. The correct way to write this loop would be:
for i in *.txt do echo $i done
D . for ls *.txt exec {} ; uses an invalid syntax for a for loop. The ls command is not a valid variable name, and the exec {} ; is not a valid command. This looks like a mix of a for loop and a find command. The correct way to write this loop would be:
for file in *.txt do exec $file done
E . foreach @{file} { echo $i } uses an invalid syntax for a for loop. The foreach keyword is not part of the shell script syntax, and the @{file} and { echo $i } are not valid expressions. This looks like a mix of a for loop and a Perl syntax. The correct way to write this loop would be:
for file in * do echo $file done
Looping Statements | Shell Script - GeeksforGeeks
How do I write a 'for' loop in Bash? - Stack Overflow
Which of the following commands creates the ZIP archive poems.zip containing all files in the current directory whose names end in .txt?
The zip command is used to create compressed archive files that can contain one or more files or directories. The zip command takes the name of the archive file as the first argument, followed by the names of the files or directories to be included in the archive. You can also use wildcards to match multiple files or directories with a common pattern. For example, the command zip poems.zip *.txt will create the ZIP archive poems.zip containing all files in the current directory whose names end in .txt. The other commands are either invalid or do not perform the desired operation. The command zip *.txt > poems.zip will try to create an archive for each file ending in .txt and redirect the output to poems.zip, which is not a valid archive file. The command zcat *.txt poems.zip will try to decompress and concatenate the contents of the files ending in .txt and poems.zip, which is not a valid ZIP file. The command zip cfz poems.zip *.txt will fail because the options c, f, and z are not valid for the zip command. The command cat *.txt | zip poems.zip will try to read the contents of the files ending in .txt from the standard input and create an archive named poems.zip, but this will not preserve the file names or attributes of the original files.Reference:
Linux Essentials - Linux Professional Institute (LPI), section 3.1.1
3.1 Archiving Files on the Command Line - Linux Professional Institute Certification Programs, slide
Which of the following commands will search for the file foo.txt under the directory /home?
The correct command to search for the file foo.txt under the directory /home is find /home --name foo.txt. This command uses the find command, which is used to search for files and directories that match certain criteria. The first argument, /home, specifies the starting point of the search. The second argument, -name, indicates that the search is based on the name of the file or directory. The third argument, foo.txt, is the name of the file to be searched for. The find command will recursively search all the subdirectories under /home and print the path of any file or directory that matches the name foo.txt.
The other commands are incorrect for various reasons:
A . search /home --file foo.txt is incorrect because there is no such command as search in Linux. The correct command for searching files and directories is find.
B . search /home foo.txt is incorrect because, as mentioned above, there is no search command in Linux. Also, this command does not use any option to specify the search criteria, such as -name, -type, -size, etc.
C . find /home -- file foo.txt is incorrect because the option -file is not valid. The correct option for specifying the type of file or directory is -type, followed by a letter that indicates the type, such as f for regular file, d for directory, l for symbolic link, etc. For example, find /home -type f -name foo.txt would search for a regular file named foo.txt under /home.
E . find /home foo.txt is incorrect because this command does not use any option to specify the search criteria, such as -name, -type, -size, etc. This command will search for any file or directory that has foo.txt as part of its name, not exactly as its name. For example, this command will also match a file named barfoo.txt or a directory named foo.txt.bak.
Running the command rm Downloads leads to the following error:
rm: cannot remove 'Downloads/': Is a directory
Which of the following commands can be used instead to remove Downloads, assuming Downloads is
empty? (Choose two correct answers.)
To remove a directory, you need to use a command that can delete directories, not just files. The rm command can only remove files by default, unless you use the -r option, which stands for recursive. This option tells rm to delete the directory and all of its contents, including subdirectories and files. The rmdir command can also remove directories, but only if they are empty. If the directory contains any files or subdirectories, rmdir will fail and display an error message. Therefore, the correct commands to remove Downloads, assuming it is empty, are rmdir Downloads and rm -r Downloads. The other commands are either invalid or do not work on directories.Reference:
Linux Essentials - Linux Professional Institute (LPI), section 2.3.1
LPI Linux Essentials Study Guide: Exam 010 v1.6, 3rd Edition, chapter 4, page 93.
What is true about links in a Linux file system?
A symbolic link, also known as a symlink or soft link, is a special type of file that points to another file or directory by its name. A symbolic link can point to a file or directory on the same or different file system, as long as the target is accessible. For example, you can create a symbolic link to a file on a USB drive or a network share, as long as the device is mounted or the connection is established. However, if the target of the symbolic link is moved, renamed, or deleted, the link becomes broken and does not work. To create a symbolic link, you can use the ln command with the -s or --symbolic option, followed by the target name and the link name. For example,ln -s /mnt/usb/file.txt link.txtcreates a symbolic link named link.txt that points to the file.txt on the USB drive mounted at /mnt/usb.
The other options are not true about links in a Linux file system. A symbolic link can point to a directory as well as a file. A hard link, which is a direct reference to the same data as another file, can only point to a file and not a directory. A hard link cannot span across different file systems, because it depends on the inode number, which is unique within a file system. When the target of the symbolic link is moved, the link is not automatically updated, but becomes broken. Any user can create hard links, as long as they have the permission to read and write the target file and the link directory.
Linux Essentials - Linux Professional Institute (LPI)
Ln Command in Linux (Create Symbolic Links) | Linuxize
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Brian Rodriguez
15 days agoJason Mitchell
29 days agoPaul Hall
2 months agoMichael Sanchez
2 months agoElizabeth Hernandez
3 months agoHarold Rodriguez
3 months agoRebecca Jackson
4 months agoBarbara Brown
4 months agoAmanda Robinson
5 months agoBrenda Garcia
5 months agoKevin Baker
5 months agoSandra Martinez
5 months agoStephen Sanchez
5 months agoChristopher Rodriguez
5 months agoPaul Flores
4 months agoJulio
6 months agoJacqueline
6 months agoHeidy
6 months agoMica
7 months agoMitzie
7 months agoClare
7 months agoKaitlyn
7 months agoFelice
7 months agoDarrin
8 months agoMarion
8 months agoFrank
8 months agoDenna
8 months agoKaycee
9 months agoDetra
9 months agoBettye
9 months agoFrancesco
9 months agoWillard
10 months agoLuis
10 months agoBenedict
10 months agoGabriele
10 months agoMalinda
11 months agoFrederica
11 months agoRashad
11 months agoMarta
11 months agoLorrine
12 months agoTawna
12 months agoRichelle
1 year agoTayna
1 year agoNobuko
1 year agoSkye
1 year agoFiliberto
1 year agoVince
1 year agoHeike
1 year agoDominque
1 year agoWillie
1 year agoEura
1 year agoMalcom
1 year agoJina
1 year agoDanilo
1 year agoMa
2 years agoWinifred
2 years agoBarney
2 years agoMyong
2 years agoLizbeth
2 years agoCarla
2 years agoRuth
2 years agoGeraldo
2 years agoJoye
2 years agoNickolas
2 years agoHeike
2 years agoStanton
2 years agoDalene
2 years agoStarr
2 years agoLoren
2 years agoSophia
2 years agoBernardo
2 years agoDelsie
2 years agoTasia
2 years agoKrissy
2 years agoRolland
2 years agoAdelina
2 years agoJanet
2 years agoLaila
2 years agoRodrigo
2 years agoAlyce
2 years agoGeorgene
2 years agoFranklyn
2 years agoCatarina
2 years agoMerilyn
2 years agoDesirae
2 years agoLore
2 years agoMaile
2 years agoVerdell
2 years ago