LPI 102-500 Bundle

The stated concern is possible elsewhere, but the facts here specifically imply A runtime-only IPv6 address can disappear unexpectedly.

That danger is associated more closely with An engineer must distinguish a globally routable IPv4 address from RFC1918 private space. Here the primary exposure is A runtime-only IPv6 address can disappear unexpectedly.

This option serves the scenario “A technician edits /etc/resolv.conf directly but NetworkManager replaces it on reconnect”. The main exposure is Manual changes to generated resolver files can be lost unexpectedly. The present scenario is distinguished by “A runtime-only IPv6 address can disappear unexpectedly”.

Although that change may be valid elsewhere, it responds to A GUI tool works under a user's desktop but fails when launched from a root shell without DISPLAY, not to this system state. The relevant fix is Set DISPLAY to the proper remote display and provide working X11 authentication.

That option does not correct the stated dependency. In this case, X11 clients use DISPLAY to choose an X server and need authorization to connect; implement Set DISPLAY to the proper remote display and provide working X11 authentication and check The test client renders on the specified remote display without broad access relaxation.

This command or configuration addresses a different case: A workstation team wants a lightweight desktop and confuses the desktop environment with its display manager. Here, X11 clients use DISPLAY to choose an X server and need authorization to connect, so the targeted action is Set DISPLAY to the proper remote display and provide working X11 authentication.

This option serves the scenario “An administrator needs to adjust a user's primary group while retaining supplementary team groups”. Expect id shows the expected primary GID and the previously authorized supplementary groups. The present scenario is distinguished by “The group appears exactly once with the approved GID and no collision”.

This alternative addresses the separate case “A server in Karachi reports UTC on local console but should display local Pakistan time without changing UTC storage”. Expect timedatectl and date show the intended offset and a consistent instant. The deciding requirement here is “The group appears exactly once with the approved GID and no collision”.

This would test another scenario: Two departments agree to rename a Unix group without changing its existing GID. Here the acceptance evidence is The group appears exactly once with the approved GID and no collision.

The stated concern is possible elsewhere, but the facts here specifically imply Leaving automatic DHCP enabled can override manually intended values.

It is not the most direct failure mode. The relevant mechanism is NetworkManager uses the connection addressing method to choose DHCP or static configuration, which risks Leaving automatic DHCP enabled can override manually intended values.

The stated concern is possible elsewhere, but the facts here specifically imply Leaving automatic DHCP enabled can override manually intended values.

It is not the most direct failure mode. The relevant mechanism is The nologin file can prevent ordinary nonroot logins depending on the login service, which risks Unplanned global login denial can lock out operators during an incident.

That danger is associated more closely with A network daemon is not required but systemd starts it through socket activation after service disable. Here the primary exposure is Unplanned global login denial can lock out operators during an incident.

That danger is associated more closely with An old host uses xinetd to launch a service that is no longer allowed. Here the primary exposure is Unplanned global login denial can lock out operators during an incident.

This option serves the scenario “A workstation prints to a central server but the technician assumes local device drivers alone determine the destination”. The conclusive result is The print configuration points to the approved server and a test reaches its queue. This question instead requires “A forced test rotation creates the next archive and keeps the service logging”.

That observation may validate A process sends syslog messages with local0 facility but they never appear in the expected dedicated file, but it does not establish that A forced test rotation creates the next archive and keeps the service logging for the current case.

The option would apply to “A daemon sends messages to syslog but urgent alerts are not forwarded to the collector”. Verify that A logger-generated test event reaches the expected central collector. The present scenario is distinguished by “A forced test rotation creates the next archive and keeps the service logging”.

This command or configuration addresses a different case: A server is reinstalled and clients receive a changed SSH host-key warning. Here, SSH host-key pinning is independent of DNS address assignment and detects unexpected key changes, so the targeted action is Verify the replacement host identity and update only the corresponding known_hosts record safely.

This command or configuration addresses a different case: A historical LPIC-1 exercise uses TCP wrappers to allow one client and deny another. Here, SSH host-key pinning is independent of DNS address assignment and detects unexpected key changes, so the targeted action is Verify the replacement host identity and update only the corresponding known_hosts record safely.

Although that change may be valid elsewhere, it responds to A compliance reviewer needs to prove that a GPG-signed release manifest was not altered, not to this system state. The relevant fix is Verify the replacement host identity and update only the corresponding known_hosts record safely.

This alternative addresses the separate case “A mail relay must be permitted through a firewall and an operator confuses SMTP with IMAP”. The governing principle is SMTP transports mail while IMAP and POP provide mailbox retrieval functions. For the stated problem, “TCP adds sequencing and retransmission whereas UDP has no built-in delivery guarantee” addresses the central condition.

The alternative can apply elsewhere, but TCP adds sequencing and retransmission whereas UDP has no built-in delivery guarantee is the governing fact here; test by checking A controlled protocol test illustrates the intended connection and datagram behavior.

This option serves the scenario “A firewall rule permits port 53 only over TCP and small DNS queries work intermittently”. The governing principle is DNS commonly uses UDP for queries and TCP for larger responses and zone transfers. This question instead requires “TCP adds sequencing and retransmission whereas UDP has no built-in delivery guarantee”.

Although that change may be valid elsewhere, it responds to A server needs a fixed default gateway for a persistent NetworkManager Ethernet profile, not to this system state. The relevant fix is Inspect routing metrics and correct the preferred default route based on policy.

This option serves the scenario “A host cannot reach a DNS server because its IPv4 interface has an incorrect subnet mask”. The appropriate operation is Compare ip addr and ip route data with the intended subnet design. The present scenario is distinguished by “Inspect routing metrics and correct the preferred default route based on policy”.

Although that change may be valid elsewhere, it responds to An IPv6-only server uses ping for an IPv4 literal and mistakenly reports IPv6 routing is broken, not to this system state. The relevant fix is Inspect routing metrics and correct the preferred default route based on policy.

Although that change may be valid elsewhere, it responds to A service's housekeeping must start five minutes after boot and then repeat every hour using systemd, not to this system state. The relevant fix is Use a valid crontab expression with the intended minute, hour and weekday fields.

This alternative addresses the separate case “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. For the stated problem, “Use a valid crontab expression with the intended minute, hour and weekday fields” addresses the central condition.

The alternative fits A project account should be allowed to run cron while arbitrary guest accounts are forbidden. The reported issue instead calls for Use a valid crontab expression with the intended minute, hour and weekday fields, as Cron's five scheduling fields select the times at which recurring jobs execute.

It is less specific than SSH private keys must remain secret to preserve authentication assurance, which directly explains the scenario and supports Protect the private key with restrictive permissions and relocate it to authorized storage.

This alternative addresses the separate case “A workstation user types an SSH private-key passphrase repeatedly for several short sessions”. Here, ssh-agent caches unlocked key operations without requiring raw private-key copying to applications. The deciding requirement here is “SSH private keys must remain secret to preserve authentication assurance”.

The related but distinct situation is “A user must authenticate to an SSH host without typing a password for an approved automation task”. The decisive distinction is SSH public-key authentication uses a private client key and authorized server-side public key. For the stated problem, “SSH private keys must remain secret to preserve authentication assurance” addresses the central condition.