LPI 102-500 Practice Test 55
Question 540
On a production Linux workstation or server, a technician observes: An administrator removes an address with `ip addr` and expects it to remain removed after a network-manager restart. Which TWO complementary steps provide the best corrective action and its most direct diagnostic verification? Select TWO answers.
- Identify RFC1918 blocks precisely and plan appropriate routing or address translation for connectivity to public destinations.
- Inspect `hostnamectl status`, /etc/hostname, /etc/hosts and `getent hosts` output before and after reboot.
- Inspect `ip -br link`, `ip address show`, carrier state and manager logs before and after a controlled interface activation.
- Attempt DNS repairs for an interface that is administratively DOWN and assume temporary `ip` state cannot be overwritten by NetworkManager.
- Use `ip link` and `ip addr` to examine and adjust temporary interface state and repair the persistent manager configuration where required.
Explanation
Correct Answers
C:Most direct verification evidence: Inspect `ip -br link`, `ip address show`, carrier state and manager logs before and after a controlled interface activation. Linux principle: The iproute2 command changes and reports kernel interface state, while durable settings are managed by the host's networking service.
E:Recommended administrative action: Use `ip link` and `ip addr` to examine and adjust temporary interface state and repair the persistent manager configuration where required. Linux principle: The iproute2 command changes and reports kernel interface state, while durable settings are managed by the host's networking service.
Incorrect Answers
A:That option would identify RFC1918 blocks precisely and plan appropriate routing or address translation for connectivity to public destinations, but it addresses a different concern. The iproute2 command changes and reports kernel interface state, while durable settings are managed by the host's networking service.
B:This alternative addresses Hostnamectl and durable host identification, not the specific issue of Ip command address and link troubleshooting: Inspect `hostnamectl status`, /etc/hostname, /etc/hosts and `getent hosts` output before and after reboot. Linux principle: The iproute2 command changes and reports kernel interface state, while durable settings are managed by the host's networking service.
D:This shortcut is unsafe for the present Linux issue: Attempt DNS repairs for an interface that is administratively DOWN and assume temporary `ip` state cannot be overwritten by NetworkManager. The iproute2 command changes and reports kernel interface state, while durable settings are managed by the host's networking service.
Question 541
During an LPIC-1 practice lab, the operator encounters this condition: A host reaches peers on its subnet but cannot reach any remote network because its default route points to an obsolete gateway. Which administrative step is the MOST appropriate way to resolve this issue? Select ONE best answer.
- Assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover.
- Inspect `ip route` and selected `ip route get`, then set or repair the appropriate default route in the active manager or with `ip route` for a controlled temporary change.
- Set the intended persistent static hostname with `hostnamectl` or supported distribution settings and validate local host mapping separately.
- Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics.
Explanation
Correct Answer
B:Recommended administrative action: Inspect `ip route` and selected `ip route get`, then set or repair the appropriate default route in the active manager or with `ip route` for a controlled temporary change. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
Incorrect Answers
A:That option would assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover, but it addresses a different concern. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
C:That option would set the intended persistent static hostname with `hostnamectl` or supported distribution settings and validate local host mapping separately, but it addresses a different concern. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
D:This alternative addresses TCP versus UDP versus ICMP diagnostics, not the specific issue of Linux routing tables and default gateway selection: Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics. Linux principle: Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity. Appropriate response: Inspect `ip route` and selected `ip route get`, then set or repair the appropriate default route in the active manager or with `ip route` for a controlled temporary change. Root-cause evidence: Examine `ip route show`, `ip route get` for a remote address, next-hop reachability and persisted route configuration. Independent acceptance: Remote traffic takes the intended next hop while on-link paths remain correct and route behavior persists as configured.
Question 542
A helpdesk escalation describes this Linux behavior: A host reaches peers on its subnet but cannot reach any remote network because its default route points to an obsolete gateway. Which Linux behavior or technical principle BEST explains why the issue occurs? Select ONE best answer.
- Port numbers identify transport endpoints within TCP or UDP; the same numeric port can be used differently across protocols and policy must match actual service bindings.
- Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
- Assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover.
- Wireless association, authentication and IP configuration are distinct stages; an SSID's visibility does not establish authorized connectivity.
Explanation
Correct Answer
B:Relevant Linux operating principle: Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
Incorrect Answers
A:This alternative addresses Well-known TCP UDP port mapping, not the specific issue of Linux routing tables and default gateway selection: Port numbers identify transport endpoints within TCP or UDP; the same numeric port can be used differently across protocols and policy must match actual service bindings. Linux principle: Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity. Appropriate response: Inspect `ip route` and selected `ip route get`, then set or repair the appropriate default route in the active manager or with `ip route` for a controlled temporary change. Root-cause evidence: Examine `ip route show`, `ip route get` for a remote address, next-hop reachability and persisted route configuration. Independent acceptance: Remote traffic takes the intended next hop while on-link paths remain correct and route behavior persists as configured.
C:That option would assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover, but it addresses a different concern. Independent acceptance: Remote traffic takes the intended next hop while on-link paths remain correct and route behavior persists as configured.
D:This alternative addresses NetworkManager Wi-Fi authentication and saved profiles, not the specific issue of Linux routing tables and default gateway selection: Wireless association, authentication and IP configuration are distinct stages; an SSID's visibility does not establish authorized connectivity. Linux principle: Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity. Appropriate response: Inspect `ip route` and selected `ip route get`, then set or repair the appropriate default route in the active manager or with `ip route` for a controlled temporary change. Root-cause evidence: Examine `ip route show`, `ip route get` for a remote address, next-hop reachability and persisted route configuration. Independent acceptance: Remote traffic takes the intended next hop while on-link paths remain correct and route behavior persists as configured.
Question 543
An operations handoff identifies this problem: A host reaches peers on its subnet but cannot reach any remote network because its default route points to an obsolete gateway. Which evidence or command result MOST directly tests the suspected root cause? Select ONE best answer.
- Inspect `nmcli connection show`, device status, saved connection properties, live `ip addr` and route after reconnect or reboot.
- Assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover.
- Inspect available SSIDs, connection authentication settings, device state, connection activation logs and effective routes.
- Examine `ip route show`, `ip route get` for a remote address, next-hop reachability and persisted route configuration.
Explanation
Correct Answer
D:Most direct verification evidence: Examine `ip route show`, `ip route get` for a remote address, next-hop reachability and persisted route configuration. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
Incorrect Answers
A:That option would inspect `nmcli connection show`, device status, saved connection properties, live `ip addr` and route after reconnect or reboot, but it addresses a different concern. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
B:This shortcut is unsafe for the present Linux issue: Assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
C:That option would inspect available SSIDs, connection authentication settings, device state, connection activation logs and effective routes, but it addresses a different concern. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
Question 544
A team maintaining a Linux host reports: A host reaches peers on its subnet but cannot reach any remote network because its default route points to an obsolete gateway. Which observed outcome BEST confirms a successful and properly scoped correction? Select ONE best answer.
- The host reports the approved name consistently and local resolution returns the correct intended addresses.
- Remote traffic takes the intended next hop while on-link paths remain correct and route behavior persists as configured.
- The device associates to the approved wireless network, authenticates successfully and receives the expected network configuration.
- Assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover.
Explanation
Correct Answer
B:Observable acceptance criterion: Remote traffic takes the intended next hop while on-link paths remain correct and route behavior persists as configured. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
Incorrect Answers
A:This alternative addresses Hostnamectl and durable host identification, not the specific issue of Linux routing tables and default gateway selection: The host reports the approved name consistently and local resolution returns the correct intended addresses. Linux principle: Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity. Appropriate response: Inspect `ip route` and selected `ip route get`, then set or repair the appropriate default route in the active manager or with `ip route` for a controlled temporary change. Root-cause evidence: Examine `ip route show`, `ip route get` for a remote address, next-hop reachability and persisted route configuration. Independent acceptance: Remote traffic takes the intended next hop while on-link paths remain correct and route behavior persists as configured.
C:This alternative addresses NetworkManager Wi-Fi authentication and saved profiles, not the specific issue of Linux routing tables and default gateway selection: The device associates to the approved wireless network, authenticates successfully and receives the expected network configuration. Linux principle: Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity. Appropriate response: Inspect `ip route` and selected `ip route get`, then set or repair the appropriate default route in the active manager or with `ip route` for a controlled temporary change. Root-cause evidence: Examine `ip route show`, `ip route get` for a remote address, next-hop reachability and persisted route configuration. Independent acceptance: Remote traffic takes the intended next hop while on-link paths remain correct and route behavior persists as configured.
D:This shortcut is unsafe for the present Linux issue: Assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
Question 545
While verifying a Linux change request, an engineer finds: A host reaches peers on its subnet but cannot reach any remote network because its default route points to an obsolete gateway. Which misleading assumption MOST directly contributes to this failure and should be rejected? Select ONE best answer.
- Assume any file under /etc/systemd/network will control an interface regardless of which network manager actually owns the device.
- Assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover.
- Assume /26 means the first 26 hosts belong to one network and that all addresses with the same first three dotted-quad octets are local.
- Use only a transient `ip addr add` command and expect NetworkManager to persist it automatically after every reboot.
Explanation
Correct Answer
B:Reject this specific misconception: Assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover. It incorrectly assumes behavior that conflicts with the observed Linux conditions.
Incorrect Answers
A:That option would assume any file under /etc/systemd/network will control an interface regardless of which network manager actually owns the device, but it addresses a different concern. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
C:That option would assume /26 means the first 26 hosts belong to one network and that all addresses with the same first three dotted-quad octets are local, but it addresses a different concern. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
D:That option would use only a transient `ip addr add` command and expect NetworkManager to persist it automatically after every reboot, but it addresses a different concern. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
Question 546
A Linux administrator investigates the following system incident: Two active interfaces have competing default routes and traffic leaves through the wrong uplink despite valid local addresses. Which administrative step is the MOST appropriate way to resolve this issue? Select ONE best answer.
- Inspect `ip route` and selected `ip route get`, then set or repair the appropriate default route in the active manager or with `ip route` for a controlled temporary change.
- Assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover.
- Map required common services to their correct transport and port, including SSH 22/TCP, HTTP 80/TCP, HTTPS 443/TCP and DNS 53/UDP or TCP where used.
- Use `ip link` and `ip addr` to examine and adjust temporary interface state and repair the persistent manager configuration where required.
Explanation
Correct Answer
A:Recommended administrative action: Inspect `ip route` and selected `ip route get`, then set or repair the appropriate default route in the active manager or with `ip route` for a controlled temporary change. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
Incorrect Answers
B:This shortcut is unsafe for the present Linux issue: Assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
C:That option would map required common services to their correct transport and port, including SSH 22/TCP, HTTP 80/TCP, HTTPS 443/TCP and DNS 53/UDP or TCP where used, but it addresses a different concern. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
D:That option would use `ip link` and `ip addr` to examine and adjust temporary interface state and repair the persistent manager configuration where required, but it addresses a different concern. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
Question 547
On a production Linux workstation or server, a technician observes: Two active interfaces have competing default routes and traffic leaves through the wrong uplink despite valid local addresses. Which Linux behavior or technical principle BEST explains why the issue occurs? Select ONE best answer.
- Assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover.
- A transient hostname change is not necessarily persisted; hostname resolution and the configured system hostname are related but distinct functions.
- Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
- The iproute2 command changes and reports kernel interface state, while durable settings are managed by the host's networking service.
Explanation
Correct Answer
C:Relevant Linux operating principle: Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
Incorrect Answers
A:This shortcut is unsafe for the present Linux issue: Assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover. It cannot establish a safe correction. Linux principle: Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
B:This alternative addresses Hostnamectl and durable host identification, not the specific issue of Linux routing tables and default gateway selection: A transient hostname change is not necessarily persisted; hostname resolution and the configured system hostname are related but distinct functions. Linux principle: Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity. Appropriate response: Inspect `ip route` and selected `ip route get`, then set or repair the appropriate default route in the active manager or with `ip route` for a controlled temporary change. Root-cause evidence: Examine `ip route show`, `ip route get` for a remote address, next-hop reachability and persisted route configuration. Independent acceptance: Remote traffic takes the intended next hop while on-link paths remain correct and route behavior persists as configured.
D:This alternative addresses Ip command address and link troubleshooting, not the specific issue of Linux routing tables and default gateway selection: The iproute2 command changes and reports kernel interface state, while durable settings are managed by the host's networking service. Linux principle: Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity. Appropriate response: Inspect `ip route` and selected `ip route get`, then set or repair the appropriate default route in the active manager or with `ip route` for a controlled temporary change. Root-cause evidence: Examine `ip route show`, `ip route get` for a remote address, next-hop reachability and persisted route configuration. Independent acceptance: Remote traffic takes the intended next hop while on-link paths remain correct and route behavior persists as configured.
Question 548
During an LPIC-1 practice lab, the operator encounters this condition: Two active interfaces have competing default routes and traffic leaves through the wrong uplink despite valid local addresses. Which evidence or command result MOST directly tests the suspected root cause? Select ONE best answer.
- Examine `ip route show`, `ip route get` for a remote address, next-hop reachability and persisted route configuration.
- Assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover.
- Inspect `hostnamectl status`, /etc/hostname, /etc/hosts and `getent hosts` output before and after reboot.
- Inspect `systemctl` service state, NetworkManager device management, /etc/systemd/network and active connection profiles alongside `ip` state.
Explanation
Correct Answer
A:Most direct verification evidence: Examine `ip route show`, `ip route get` for a remote address, next-hop reachability and persisted route configuration. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
Incorrect Answers
B:This shortcut is unsafe for the present Linux issue: Assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover. It cannot establish a safe correction. Linux principle: Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity. Appropriate response: Inspect `ip route` and selected `ip route get`, then set or repair the appropriate default route in the active manager or with `ip route` for a controlled temporary change. Root-cause evidence: Examine `ip route show`, `ip route get` for a remote address, next-hop reachability and persisted route configuration. Independent acceptance: Remote traffic takes the intended next hop while on-link paths remain correct and route behavior persists as configured.
C:This alternative addresses Hostnamectl and durable host identification, not the specific issue of Linux routing tables and default gateway selection: Inspect `hostnamectl status`, /etc/hostname, /etc/hosts and `getent hosts` output before and after reboot.
D:That option would inspect `systemctl` service state, NetworkManager device management, /etc/systemd/network and active connection profiles alongside `ip` state, but it addresses a different concern. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
Question 549
A helpdesk escalation describes this Linux behavior: Two active interfaces have competing default routes and traffic leaves through the wrong uplink despite valid local addresses. Which observed outcome BEST confirms a successful and properly scoped correction? Select ONE best answer.
- The host reports the approved name consistently and local resolution returns the correct intended addresses.
- Assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover.
- Remote traffic takes the intended next hop while on-link paths remain correct and route behavior persists as configured.
- The intended link is administratively up with the expected address and persistent configuration remains stable after service restart.
Explanation
Correct Answer
C:Observable acceptance criterion: Remote traffic takes the intended next hop while on-link paths remain correct and route behavior persists as configured. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
Incorrect Answers
A:This alternative addresses Hostnamectl and durable host identification, not the specific issue of Linux routing tables and default gateway selection: The host reports the approved name consistently and local resolution returns the correct intended addresses. Linux principle: Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity. Appropriate response: Inspect `ip route` and selected `ip route get`, then set or repair the appropriate default route in the active manager or with `ip route` for a controlled temporary change. Root-cause evidence: Examine `ip route show`, `ip route get` for a remote address, next-hop reachability and persisted route configuration. Independent acceptance: Remote traffic takes the intended next hop while on-link paths remain correct and route behavior persists as configured.
B:This shortcut is unsafe for the present Linux issue: Assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
D:This alternative addresses Ip command address and link troubleshooting, not the specific issue of Linux routing tables and default gateway selection: The intended link is administratively up with the expected address and persistent configuration remains stable after service restart. Linux principle: Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity. Appropriate response: Inspect `ip route` and selected `ip route get`, then set or repair the appropriate default route in the active manager or with `ip route` for a controlled temporary change. Root-cause evidence: Examine `ip route show`, `ip route get` for a remote address, next-hop reachability and persisted route configuration. Independent acceptance: Remote traffic takes the intended next hop while on-link paths remain correct and route behavior persists as configured.
Question 550
An operations handoff identifies this problem: Two active interfaces have competing default routes and traffic leaves through the wrong uplink despite valid local addresses. Which TWO complementary steps provide the best corrective action and its most direct diagnostic verification? Select TWO answers.
- Examine `ip route show`, `ip route get` for a remote address, next-hop reachability and persisted route configuration.
- Assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover.
- Inspect `ip route` and selected `ip route get`, then set or repair the appropriate default route in the active manager or with `ip route` for a controlled temporary change.
- Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics.
- Compare `getent hosts name`, /etc/nsswitch.conf hosts line, /etc/hosts entry and DNS-only `dig` output.
Explanation
Correct Answers
A:Most direct verification evidence: Examine `ip route show`, `ip route get` for a remote address, next-hop reachability and persisted route configuration. Linux principle: Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
C:Recommended administrative action: Inspect `ip route` and selected `ip route get`, then set or repair the appropriate default route in the active manager or with `ip route` for a controlled temporary change. Linux principle: Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
Incorrect Answers
B:This shortcut is unsafe for the present Linux issue: Assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover. Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity.
D:This alternative addresses TCP versus UDP versus ICMP diagnostics, not the specific issue of Linux routing tables and default gateway selection: Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics. Linux principle: Routing chooses destination paths from installed route prefixes and metrics; a correct local interface address alone does not establish off-link connectivity. Appropriate response: Inspect `ip route` and selected `ip route get`, then set or repair the appropriate default route in the active manager or with `ip route` for a controlled temporary change. Root-cause evidence: Examine `ip route show`, `ip route get` for a remote address, next-hop reachability and persisted route configuration. Independent acceptance: Remote traffic takes the intended next hop while on-link paths remain correct and route behavior persists as configured.
E:This alternative addresses Local hosts resolution versus DNS settings, not the specific issue of Linux routing tables and default gateway selection: Compare `getent hosts name`, /etc/nsswitch.conf hosts line, /etc/hosts entry and DNS-only `dig` output.
