LPI 102-500 Bundle

This command or configuration addresses a different case: A fresh server boots with an unapproved web service that nobody uses. Here, Socket activation can launch a service even if its service unit is otherwise inactive, so the targeted action is Disable the unnecessary systemd socket unit as well as the associated service where appropriate.

This command or configuration addresses a different case: A host still exposes Telnet but policy allows only encrypted remote administration. Here, Socket activation can launch a service even if its service unit is otherwise inactive, so the targeted action is Disable the unnecessary systemd socket unit as well as the associated service where appropriate.

Although that change may be valid elsewhere, it responds to A process consumes too much address space and a shell session needs a temporary limit, not to this system state. The relevant fix is Disable the unnecessary systemd socket unit as well as the associated service where appropriate.

It fails to address the actual requirement, A host's hostname is present in /etc/hosts but its external DNS lookup returns an NXDOMAIN. The needed change is Distinguish local hosts-file resolution from authoritative public DNS records; verify getent finds the local mapping while a direct remote DNS query still reports NXDOMAIN.

The alternative fits A program resolves a name differently than dig because local NSS mappings override DNS. The reported issue instead calls for Distinguish local hosts-file resolution from authoritative public DNS records, as A hosts-file entry affects local NSS resolution and does not create a DNS zone record.

This option serves the scenario “In an LPIC-1 102-500 administration task, A system using systemd-resolved shows generated /etc/resolv.conf and an administrator edits it persistently”. The safest fitting response is Configure the upstream DNS through the responsible resolver or network manager. This question instead requires “Distinguish local hosts-file resolution from authoritative public DNS records”.

The related but distinct situation is “A maintenance script unexpectedly executes a local program named ls before the system utility”. The appropriate operation is Remove unsafe current-directory entries from PATH and use trusted command locations. For the stated problem, “Use an explicit executable path or script logic rather than relying on interactive aliases” addresses the central condition.

Although that change may be valid elsewhere, it responds to A script launched by sudo expects an administrator's custom shell alias to be available, not to this system state. The relevant fix is Use an explicit executable path or script logic rather than relying on interactive aliases.

This command or configuration addresses a different case: A scripted conditional needs to distinguish an empty variable from a nonempty path safely. Here, Cron's noninteractive shell does not necessarily load the user's alias definitions, so the targeted action is Use an explicit executable path or script logic rather than relying on interactive aliases.

The related but distinct situation is “In an LPIC-1 102-500 administration task, An old host uses xinetd to launch a service that is no longer allowed”. The appropriate operation is Disable the relevant xinetd service entry and reload the controlling daemon. The deciding requirement here is “Disable the legacy Telnet service or socket and enforce approved SSH access”.

This option serves the scenario “A network daemon is not required but systemd starts it through socket activation after service disable”. The safest fitting response is Disable the unnecessary systemd socket unit as well as the associated service where appropriate. This question instead requires “Disable the legacy Telnet service or socket and enforce approved SSH access”.

This alternative addresses the separate case “A hardening scan finds an unfamiliar TCP listener on a production Linux host”. The safest fitting response is Correlate ss or netstat listener data with process ownership and approved service inventory. For the stated problem, “Disable the legacy Telnet service or socket and enforce approved SSH access” addresses the central condition.

Although that change may be valid elsewhere, it responds to A server logs show a large time offset but ntpq reports no selected peer, not to this system state. The relevant fix is Check the rsyslog facility selector and its action path for local0 messages.

It fails to address the actual requirement, A process sends syslog messages with local0 facility but they never appear in the expected dedicated file. The needed change is Check the rsyslog facility selector and its action path for local0 messages; verify A logger -p local0.info test appears in the dedicated file.

It fails to address the actual requirement, A process sends syslog messages with local0 facility but they never appear in the expected dedicated file. The needed change is Check the rsyslog facility selector and its action path for local0 messages; verify A logger -p local0.info test appears in the dedicated file.

This would be the main explanation for A custom application's logs grow indefinitely because no rotation policy exists. It does not account for A mail alias is added to /etc/aliases but messages still go to the old address.

This would be the main explanation for A node lacks a full mail transport service but a monitoring task assumes local mail delivery. It does not account for A mail alias is added to /etc/aliases but messages still go to the old address.

This option serves the scenario “A Linux server must deliver mail addressed to root to an on-call administrator”. This behavior is explained by Local mail aliases redirect a recipient without modifying the sender's mail command. This question instead requires “Alias source changes may require regeneration of the lookup database”.

The related but distinct situation is “A Linux host keeps accurate software time but its hardware RTC is configured to a different local timezone”. The governing principle is Keeping the RTC in UTC avoids daylight-saving and timezone ambiguity on Linux hosts. For the stated problem, “The hardware clock and the running system clock are separate clock representations” addresses the central condition.

This option serves the scenario “A service needs the current timestamp as ISO text for an audit record”. This behavior is explained by The date utility formats system time and can render an unambiguous offset-bearing timestamp. The present scenario is distinguished by “The hardware clock and the running system clock are separate clock representations”.

The proposed principle does not identify the crucial dependency in this case: The hardware clock and the running system clock are separate clock representations.

The related but distinct situation is “A process consumes too much address space and a shell session needs a temporary limit”. The best evidence is A controlled child process observes the configured limit. The deciding requirement here is “The affected user is prompted to set a new valid password at the next login”.

This alternative addresses the separate case “An SSH client rejects a host after a DNS migration because the stored known_hosts entry no longer matches”. Verify that A verified new fingerprint is recorded and the intended SSH connection completes. For the stated problem, “The affected user is prompted to set a new valid password at the next login” addresses the central condition.

The proposed check does not prove the intended behavior. A directly relevant test must show The affected user is prompted to set a new valid password at the next login.

This alternative addresses the separate case “A user sets LC_ALL for a one-off task and then wonders why LC_NUMERIC no longer controls decimals”. The main exposure is Global override can silently defeat individual localization choices. The deciding requirement here is “Unspecified collation rules can break reproducible hashes or batch comparisons”.

The option would apply to “An automated task must run at system startup even if no user logs into a shell”. Leaving the issue can cause Putting the job only in .bashrc can start it unpredictably or never run. This question instead requires “Unspecified collation rules can break reproducible hashes or batch comparisons”.

The case is most directly exposed to Unspecified collation rules can break reproducible hashes or batch comparisons; the alternative describes a different operational risk.

Although that change may be valid elsewhere, it responds to A mail relay must be permitted through a firewall and an operator confuses SMTP with IMAP, not to this system state. The relevant fix is Use ss for sockets and iproute2 for interface and route inspection.

That option does not correct the stated dependency. In this case, Modern Linux commonly uses ss and ip instead of legacy net-tools utilities; implement Use ss for sockets and iproute2 for interface and route inspection and check The same listener and route facts are available through supported modern commands.

The alternative fits An IPv6-only server uses ping for an IPv4 literal and mistakenly reports IPv6 routing is broken. The reported issue instead calls for Use ss for sockets and iproute2 for interface and route inspection, as Modern Linux commonly uses ss and ip instead of legacy net-tools utilities.

The option would apply to “A resolver searches external DNS before local /etc/hosts and ignores a deliberate test alias”. The decisive distinction is NSS controls whether files or DNS are consulted first for hostnames. This question instead requires “Hop-tracing tools estimate path behavior using TTL or hop-limit expiration”.

That statement explains another situation: A network engineer uses netstat on a minimal modern Linux host and discovers it is not installed. The current observation instead depends on Hop-tracing tools estimate path behavior using TTL or hop-limit expiration.

This would be the main explanation for A host shows an Ethernet link but no IP connectivity to its local subnet peers. It does not account for A user reports packet loss only toward one remote hop and wants to locate the failing segment.