Free LPI 102-500 Actual Exam Questions

E, because read only assigns the first three numbers and then stops.

B tbh, I see why E seems right, but the ‘read a b c’ will actually assign a=1, b=2, and c=3 and then the loop echoes those three in reverse order once. The leftover numbers (4 5 6) don’t get processed in this setup because read reads one line at a time, and there’s only one line. So output is “result 3 2 1” just once, which matches E, not B. The command doesn’t print the whole set or reverse all six numbers, so options like B or D don’t make sense here.

C seems off since date --timezone only changes the current session time, not the system timezone permanently. So it's probably not C.

B, since it directly points to the UTC timezone file permanently.

Probably C. The commas are necessary to separate columns, and no parentheses are used in standard SELECT syntax. D is missing the comma, so it can’t be correct.

A/B are wrong because of parentheses usage, which isn’t valid here. Between C and D, D is missing the comma, so C’s the cleanest and most standard choice.

Makes sense to go with E since usermod is designed to modify user account settings, including group memberships. The trick is you have to specify all groups the user should stay in, leaving out the one you want removed. A and D aren’t standard commands for this, and C deals with passwords, so they’re out. B is more for changing group details, not user memberships. So, E fits best here.

Good points all around. I’d back E as well — usermod with the -G option actually sets the entire list of supplementary groups, so you have to list all the groups you want the user to remain in except the one you want to remove. So technically it doesn't just remove a single group but replaces the whole group membership set. None of the other options work for removing users from groups, so E is the only viable choice here.

Pretty sure it's B since user crontabs need to be separate and managed by the system, and /var/spool/cron fits that role. The other options don't usually store user-specific cron jobs. B

B imo, user crontabs are definitely not in home directories or shared files. They’re stored individually in /var/spool/cron so the system can manage them per user.

Maybe D works best since it covers every hour at 30 minutes past on Sunday (0). C only runs at midnight, so it’s not every hour. A and E have invalid weekday values, so they’re out.

B/D? B hits 30 past every hour but only on day 6, which is usually Saturday, so no. D covers all hours at 30 on day 0, which is Sunday in most setups, so that fits better.

I’d also say "select" fits best because count(*) is used within a select statement to get the total rows. No other SQL keyword would make sense before count(*).

"select" makes the most sense here, since count(*) is always used with select to fetch the result. No other keyword logically fits before count(*).

D vs B? I’m sticking with D because ~/.forward is the usual user-controlled file for redirecting mail in Sendmail. ~/.alias (B) is typically a system or global config thing, not something users edit themselves. Also, /etc/alias and /etc/mail/forwarders are system-wide and need admin rights. ~/.vacation is for auto-replies, not forwarding. So D fits the question about user-configurable mail redirection best.

D. Only ~/.forward lets users redirect their own mail without needing admin rights, unlike system files like /etc/alias or /etc/mail/forwarders that require higher privileges.

No doubt it’s D, 'x' is the classic sign for shadow storage. D

I’d rule out A and B since * and - usually mean locked or no password. C sounds off too, never seen 's' for shadow. So, is it really just D that matches common practice?

A makes sense because 'for' is the standard keyword for this pattern.

A, cause only 'for' fits iterating over files like that.

It’s A because if neither file exists, cron defaults to denying access to users by default, so no one can create crontabs unless those files are set up.

B. The absence of both files usually means no restrictions are applied, so all users can create their own crontabs by default.

A imo, lpd is more about the daemon managing print queues, not the command for sending files. The question says “sending files to the printer queues,” which hints at the command that actually submits the job, not the service running in the background. So lpr (D) fits that better as it’s the command-line tool provided by CUPS for printing. It’s a subtle difference but important here.

lpr is the one CUPS kept for legacy command-line printing, so D fits best.

The directory is definitely /usr/share/zoneinfo since that’s where all timezone files are stored. Linking /etc/localtime to any file inside that folder sets the system timezone correctly.

The question wants the directory without any country or region info, so it’s just the base folder that holds all the timezone data files. That’s definitely /usr/share/zoneinfo because the actual timezone files for different regions are stored inside subfolders there, but the parent directory is what you link from /etc/localtime. Linking directly to /usr/share/zoneinfo without specifying a region won’t set a proper timezone, but since the question excludes country info, that’s the correct directory to mention here.

D imo, the key is it only echoes $1 and $2, so anything after B is ignored. The missing () might be weird, but output definitely won’t include C, ruling out options with three arguments printed.

I’m curious if the missing () after myfunction affects how arguments are passed. If it does run, $1 and $2 should only be A and B, so output matches option A. Does anyone know if that syntax is valid in all Bash versions?

It’s A because it directs where to find system info like hosts, not just LDAP.

Option A, because it specifies system info sources, not just LDAP or service startup.