Free LPI 702-100 Actual Exam Questions

Not B, because df -h shows disk usage and includes network filesystems too. The mount command without options is better for just listing local mounted filesystems.

mount command without options actually lists all mounted filesystems, including local ones.

B imo, others either run too often or have wrong syntax.

B/D? B is definitely right for hourly, but D has a typo with that "o" instead of zero, so it can't be correct. The rest don’t match the hourly pattern properly.

C. The key here is "updates packages to newer versions," which means actually upgrading what's installed. pkg update just grabs the latest repo catalog but doesn’t touch installed packages. pkg upgrade is the one that applies newer versions to your system. The other options either check for vulnerabilities or don’t exist in this context. So, it’s really about the distinction between refreshing metadata and performing the upgrade itself.

A/D? Since pkg update just refreshes repo info and pkg audit only scans for vulnerabilities, neither installs new versions. It’s between those two if you think about updating data versus security checks.

It’s definitely not A or B since those don’t match typical default permissions. D is the raw default before umask, so that’s out. E is for directories, so C fits best for files after applying umask 022.

Guessing C since the question is about files, not directories.

Good point on D being off. Also, E is just for creating or updating timestamps, so it won’t tell us anything about the file contents. That leaves A as the only practical way to identify the data type. Definitely A.

A. Also, other options either just list metadata (like B) or rely on specific formats (like C). File is designed exactly for this purpose—checking the file content without assumptions.

Not B, it misses spaces inside brackets which Bourne shell needs.

D imo, because the classic Bourne shell requires spaces around the square brackets and proper use of test commands. Looking at the options, D seems to follow the right syntax with spaces and a valid test expression, unlike C which uses double brackets that aren’t supported. A and B either miss spaces or have syntax quirks that would cause errors in a strict Bourne shell environment. So, if this is about original Bourne shell syntax only, D is the safest bet.

It’s D again. The main thing is the correct order: device first, then mount point, then filesystem type. Options like A and E mess that up by swapping fields or using wrong syntax. B looks more like a mount command line rather than fstab format. C uses a totally odd format. So D fits the standard fstab layout perfectly with the right device, mount point, and filesystem type for a CD device.

It’s D as well. The fstab format is pretty strict: device first, then mount point, then filesystem type. The other options either mix up the order or use weird syntax that doesn’t match fstab standards. A and E flip device and mount point, B looks more like a mount command, not fstab. Plus, cd9660 is the right filesystem for a CD device, so D fits perfectly without extra confusion.

C. You can definitely set build flags and enable features only at compile time, which you just can’t mess with in a pre-built binary. That’s the main advantage here.

It’s C as well. Another way to see it: when you compile from source, you can enable or disable features that are hardcoded into the app, which you simply can’t do with a binary. D doesn’t hold up since binaries are fixed in what they include or exclude at compile time, so they don’t really offer more options than source builds—just runtime settings, which aren’t the same thing.

I agree that the slash (/) symbol is the one used for forward search in vi, but thinking about it from a different angle: since the question wants just the single character, and vi distinguishes forward vs backward search by using slash for forward and question mark for backward, eliminating the question mark makes sense here. Plus, colon (:) is for commands, so that doesn’t fit. So it’s definitely slash.

I’m with the others on this being the slash (/). The question just wants the single symbol, and slash is the classic way to start a forward search in vi. The question mark (?) is for backward search, so that’s easy to rule out. Plus and asterisk don’t really fit here since they’re more for pattern matching or repeats inside vi commands, not starting a search. So it’s definitely the slash symbol.

I trust /etc/printers too, it fits the classic BSD ipr setup better.

I think /etc/printers is the solid choice here. The ipr system on BSD traditionally uses that file to list available printers. The printers.conf file is more tied to CUPS or other newer printing systems, which isn’t what ipr uses. So if the question wants the file tied directly to ipr, /etc/printers fits best.

mkdir works in both Linux and Windows, so it’s the safest bet here.

I’d say mkdir makes the most sense here since it’s the universal command for creating directories on Linux and most Unix-like systems. The other options don’t really match up: touch creates files, ls lists files, and cd changes directories but doesn’t create them. Since the question just wants the bare command without any paths or flags, mkdir fits perfectly. Plus, it’s pretty much standard across different shells, so it’s the safest bet.

-v shows detailed OS version info, not just the kernel release.

I think -v makes sense since it shows the OS version string, not just the kernel release like -r. The question wants the running OS version, so -v is the clearer match here.

I’d say rcctl fits better for FreeBSD since it’s designed for boot service control specifically. NetBSD mostly uses rc.d scripts directly or rcorder, so rcctl might not be the answer for both.

I’m going with service too because it’s the common command that both FreeBSD and NetBSD support for managing services at boot. rcctl is definitely more FreeBSD-specific and isn’t available on NetBSD by default. Since the question asks for a single command for both, service fits best. It’s the standard wrapper for rc.d scripts on both systems, so it makes sense here.

That file sets interface parameters directly, so /etc/hostname.em0 makes complete sense.

I think it’s definitely /etc/hostname.em0 because OpenBSD uses those “hostname.interface” files to set up each network interface individually. Other files like dhclient.conf handle DHCP client options but aren’t the core config for that interface. So if the question is about the main network interface config file, /etc/hostname.em0 is the one they want.

I think the key part here is "set during system startup" and "values for MIBs." The /etc/snmp/snmpd.conf usually has the daemon config but doesn’t store MIB values that persist. The file under /var/lib/snmp/snmpd.conf.static fits better since it holds the saved MIB values that get loaded when the SNMP daemon starts. So the full path /var/lib/snmp/snmpd.conf.static makes sense as the answer because it's designed for storing those persistent values, not just runtime configs.

Could also rule out /etc/snmp/snmpd.conf because it mainly configures the daemon, not the MIB values saved across restarts. The static file under /var/lib/snmp sounds more fitting for values set during startup.