LPI 102-500 Bundle

The option would apply to “A host uses a /26 mask but a technician assumes every subnet has 254 usable addresses”. The conclusive result is A subnet calculator and assigned usable range agree on 62 host addresses. This question instead requires “Production configuration uses an assigned valid IPv6 prefix rather than documentation space”.

The related but distinct situation is “An IPv6-only server uses ping for an IPv4 literal and mistakenly reports IPv6 routing is broken”. Expect An IPv6 target responds over the expected IPv6 interface and gateway. For the stated problem, “Production configuration uses an assigned valid IPv6 prefix rather than documentation space” addresses the central condition.

A passing result on that unrelated check cannot certify the present correction; require Production configuration uses an assigned valid IPv6 prefix rather than documentation space.

That statement explains another situation: An administrator needs to adjust a user's primary group while retaining supplementary team groups. The current observation instead depends on Password aging policy is maintained separately from the plaintext password itself.

This option serves the scenario “A support team needs to inspect one user's groups but /etc/group alone seems to omit the primary group”. This behavior is explained by The primary GID is stored in the passwd record and can be resolved through group databases. This question instead requires “Password aging policy is maintained separately from the plaintext password itself”.

This alternative addresses the separate case “A scheduled maintenance command writes to stdout but no file is created and the team assumes nothing ran”. The decisive distinction is Cron's command output routing differs from interactive terminal output. For the stated problem, “Password aging policy is maintained separately from the plaintext password itself” addresses the central condition.

This option serves the scenario “A support team needs to inspect one user's groups but /etc/group alone seems to omit the primary group”. The appropriate operation is Use id or getent with the relevant user and account databases. The present scenario is distinguished by “Query the configured NSS databases with getent passwd username”.

This command or configuration addresses a different case: A deployment parser depends on English month names while a server's locale uses translated names. Here, Name service switch resolution can include accounts not stored in local passwd files, so the targeted action is Query the configured NSS databases with getent passwd username.

That option does not correct the stated dependency. In this case, Name service switch resolution can include accounts not stored in local passwd files; implement Query the configured NSS databases with getent passwd username and check getent returns the expected directory account while local files remain unchanged.

The option would apply to “A deployment parser depends on English month names while a server's locale uses translated names”. Here, Locale settings can change date output and text formatting in command-line tools. The present scenario is distinguished by “Locale numeric category can change decimal punctuation and parsing expectations”.

The related but distinct situation is “A shell script's sorted output differs between English and German systems”. The governing principle is Locale collation rules can change ordering of otherwise identical text input. The deciding requirement here is “Locale numeric category can change decimal punctuation and parsing expectations”.

The proposed principle does not identify the crucial dependency in this case: Locale numeric category can change decimal punctuation and parsing expectations.

The alternative fits A scheduled maintenance command writes to stdout but no file is created and the team assumes nothing ran. The reported issue instead calls for Review running processes and preserved file ownership before a controlled userdel operation, as Removing a passwd entry does not automatically reconcile all processes and numeric UID ownership.

That option does not correct the stated dependency. In this case, Removing a passwd entry does not automatically reconcile all processes and numeric UID ownership; implement Review running processes and preserved file ownership before a controlled userdel operation and check The deprovisioning record addresses the user's processes and preserved files safely.

It fails to address the actual requirement, A user account is deleted but its running processes and file ownership remain on shared storage. The needed change is Review running processes and preserved file ownership before a controlled userdel operation; verify The deprovisioning record addresses the user's processes and preserved files safely.

It fails to address the actual requirement, A system has two NetworkManager profiles on one NIC and activates the wrong address after restart. The needed change is Choose the intended profile and set suitable autoconnect priority or activation policy; verify The correct profile is active after reboot with the expected address and route.

This option serves the scenario “In an LPIC-1 102-500 administration task, A test host uses 255.255.255.0 but another host in the same VLAN uses 255.255.0.0”. The appropriate operation is Normalize the intended IPv4 prefixes and verify routing and broadcast behavior. This question instead requires “Choose the intended profile and set suitable autoconnect priority or activation policy”.

It fails to address the actual requirement, A system has two NetworkManager profiles on one NIC and activates the wrong address after restart. The needed change is Choose the intended profile and set suitable autoconnect priority or activation policy; verify The correct profile is active after reboot with the expected address and route.

That statement explains another situation: An operator needs to identify which process owns an unexpected listening socket. The current observation instead depends on Runtime hostnames and persistent system identity can be configured separately.

This alternative addresses the separate case “A new static IPv4 connection created with nmcli disappears after reboot because it was not saved correctly”. The decisive distinction is Runtime interface changes do not automatically define a persistent connection configuration. The deciding requirement here is “Runtime hostnames and persistent system identity can be configured separately”.

The option would apply to “A technician edits /etc/resolv.conf directly but NetworkManager replaces it on reconnect”. The decisive distinction is Network-management services can regenerate resolv.conf from persistent connection settings. This question instead requires “Runtime hostnames and persistent system identity can be configured separately”.

That outcome fits another condition, A terminated contractor should no longer log in while the home directory is retained for legal review, rather than the current one.

The option would apply to “A developer edits a systemd timer file but the system continues following its earlier schedule”. Leaving the issue can cause Editing a unit without reloading can leave the old schedule active. The present scenario is distinguished by “Deleting and recreating the group with a different ID can orphan shared permissions”.

The case is most directly exposed to Deleting and recreating the group with a different ID can orphan shared permissions; the alternative describes a different operational risk.

The option would apply to “A server must be assigned a persistent IPv6 address but its only configuration is an ip -6 addr add command”. The decisive distinction is The ip utility changes the running kernel state, not necessarily boot-time persistence. This question instead requires “Incorrect prefix length changes what the kernel considers directly connected”.

The related but distinct situation is “A Linux host can ping its gateway but cannot reach the Internet because no default route exists”. The governing principle is Traffic for destinations outside connected prefixes requires a selected route. For the stated problem, “Incorrect prefix length changes what the kernel considers directly connected” addresses the central condition.

The alternative can apply elsewhere, but Incorrect prefix length changes what the kernel considers directly connected is the governing fact here; test by checking The corrected mask makes the DNS server reachable through the proper path.

Although that change may be valid elsewhere, it responds to An hourly job is moved from a user crontab into /etc/crontab and fails to execute, not to this system state. The relevant fix is Use crontab -l -u account where authorized instead of scanning another user's home.

That option does not correct the stated dependency. In this case, User crontab entries are managed by cron utilities rather than stored in ordinary profile files; implement Use crontab -l -u account where authorized instead of scanning another user's home and check The listing reports the target account's scheduled entries without modifying them.

The option would apply to “A support team needs to inspect one user's groups but /etc/group alone seems to omit the primary group”. The appropriate operation is Use id or getent with the relevant user and account databases. The present scenario is distinguished by “Use crontab -l -u account where authorized instead of scanning another user's home”.

This option serves the scenario “A department requires an existing user to join the audit group without losing other supplementary groups”. The main exposure is Using usermod -G without append can silently remove existing group access. The present scenario is distinguished by “Duplicate or unexpected GIDs may unintentionally share group-based file access”.

It is not the most direct failure mode. The relevant mechanism is Group management utilities maintain consistent names and numeric group identities, which risks Duplicate or unexpected GIDs may unintentionally share group-based file access.

It is not the most direct failure mode. The relevant mechanism is Group management utilities maintain consistent names and numeric group identities, which risks Duplicate or unexpected GIDs may unintentionally share group-based file access.