Free LPI 102-500 Actual Exam Questions - Question 2 Discussion

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.

Option C wouldn’t actually change the system timezone, just show the date in UTC. So it can't be right for setting the timezone permanently.

B, since linking the timezone file is standard and safe for most Linux systems.

B, because linking the correct timezone file is the usual manual method.

D imo, moves files around which is risky and unlikely the intended way. B seems safer since it just links to the correct timezone file without messing with system files directly.

It’s B for me too. The key is that /etc/localtime needs to point to the right timezone file, and creating a symlink to /usr/share/zoneinfo/UTC does exactly that. A and D either try writing or moving files in places that don’t control the timezone, and C just changes the output format temporarily without affecting the system clock. Even if some distros use timedatectl, this symlink method is the underlying mechanism most rely on.

Yeah, B seems solid since /etc/localtime is the standard place for timezone info. Options A and D mess with odd files, and C just changes date output temporarily. Definitely B here.

Isn't timedatectl the better way on systemd systems instead of just symlinking?

Makes sense to pick B since /etc/localtime is the usual symlink that tells the system what timezone to use. A looks off because just dumping "UTC" into /etc/timezone might not do anything unless the system reads that file and updates the localtime accordingly, which isn’t common. C just changes how date displays time temporarily. D tries moving a file from a path that probably doesn’t exist, so it’s a no-go. So yeah, B is the solid choice here.

I’d rule out C because date --timezone=UTC just changes the output format for that command, not the whole system’s timezone. Also, A tries to write "UTC" into /etc/timezone but that file usually contains a timezone name, not raw text like that, so it won’t properly update the system time settings. D’s path looks suspicious—there’s no /usr/timezone directory by default. So B stands out as the only option that correctly links the system timezone file.

B imo. The key thing is that system timezone is usually defined by the file /etc/localtime linking to the right zoneinfo file. Options A and D seem off because they either try to overwrite or move stuff in the wrong places. C only affects the display of date temporarily, doesn’t set system timezone permanently. So B matches what I’ve seen in Linux setups.

It’s B again for me. Just to add, options A and D mess with files or paths that don’t actually control the system timezone. Option C only changes the date command’s behavior temporarily but doesn’t update the system-wide setting. So linking the correct zoneinfo file is really the only solid way to set UTC properly.

It’s B because /etc/localtime has to point to the timezone file for the system to use it properly. The other options either use wrong commands or paths that don’t actually set the timezone.

B, since /etc/localtime needs to link to the right zoneinfo file.

B for sure, it’s the usual way to link the timezone file to localtime. The others seem off or wrong paths.