100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 670
A Linux guest has carrier and a default route expectation, but ip addr reveals no address on the intended interface. Choose THREE measures that together correct the failure, demonstrate success and reduce recurrence.
- Allow approved TCP 53 traffic in addition to UDP 53 where the DNS deployment requires it.
- Apply the correct dynamic or static address to the proper interface using the authoritative manager.
- Test address assignment separately from physical carrier and routing.
- Check ip addr show dev interface and run an on-link test to confirm reachability.
- Check ip -6 addr and ping with the correct interface scope to an on-link neighbor.
- Manage DNS at its authoritative configuration layer instead of editing generated files.
Explanation
Correct Answers
B:Apply the correct dynamic or static address to the proper interface using the authoritative manager. Unlike a broad workaround, it targets the observed cause: Layer-two link state does not imply that an IPv4 or IPv6 address has been configured.
C:Test address assignment separately from physical carrier and routing. Sustained checks matter because Layer-two link state does not imply that an IPv4 or IPv6 address has been configured.
D:Check ip addr show dev interface and run an on-link test to confirm reachability. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: Layer-two link state does not imply that an IPv4 or IPv6 address has been configured.
Incorrect Answers
A:This option assumes DNS commonly uses UDP and also uses TCP for responses and operations requiring it. The reported symptoms instead call for: Apply the correct dynamic or static address to the proper interface using the authoritative manager.
E:The test for ipv6 link-local scope would be: Check ip -6 addr and ping with the correct interface scope to an on-link neighbor. The relevant acceptance check here is: Check ip addr show dev interface and run an on-link test to confirm reachability.
F:It would address persistent dns in managed connection rather than the present problem. The appropriate correction here is: Apply the correct dynamic or static address to the proper interface using the authoritative manager.
Question 671
A host reaches local devices but remote packets go to an obsolete gateway shown by ip route. Which explanation most directly accounts for the failure in this environment?
- NXDOMAIN indicates a negative name response, not by itself a broken physical network connection.
- Profile priority and autoconnect policy can select an unintended saved connection.
- The default route's next hop is wrong for the current network segment.
- The active profile's automatic method permits DHCP to supply network settings.
Explanation
Correct Answer
C:The default route's next hop is wrong for the current network segment. A good follow-up is to test this explanation through: Use ip route get destination and compare path selection before and after.
Incorrect Answers
A:NXDOMAIN indicates a negative name response, not by itself a broken physical network connection. belongs to a situation where NXDOMAIN indicates a negative name response, not by itself a broken physical network connection. Here the evidence supports a different requirement: The default route's next hop is wrong for the current network segment.
B:That choice responds to a multiple saved profiles for one device failure. In this incident, The default route's next hop is wrong for the current network segment.
D:The active profile's automatic method permits DHCP to supply network settings. belongs to a situation where The active profile's automatic method permits DHCP to supply network settings. Here the evidence supports a different requirement: The default route's next hop is wrong for the current network segment.
Question 672
A host reaches local devices but remote packets go to an obsolete gateway shown by ip route. What action should be planned as the next targeted correction?
- Identify the actual interface manager and use appropriate systemd-networkd configuration for this host.
- Correct the default route via the approved on-link gateway and persist the configuration.
- Configure the connection with the approved SSID and authentication settings using NetworkManager.
- Inspect /etc/nsswitch.conf hosts order and remove the stale local mapping if not required.
Explanation
Correct Answer
B:Correct the default route via the approved on-link gateway and persist the configuration. It addresses the root cause, while Audit default routes after VLAN and subnet migrations. reduces future recurrence.
Incorrect Answers
A:It would address systemd-networkd awareness rather than the present problem. The appropriate correction here is: Correct the default route via the approved on-link gateway and persist the configuration.
C:Configure the connection with the approved SSID and authentication settings using NetworkManager. could help with wi-fi network name and authentication; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use ip route get destination and compare path selection before and after.
D:The test for nss hosts lookup order would be: Compare getent hosts and dig for the name and identify the selected source. The relevant acceptance check here is: Use ip route get destination and compare path selection before and after.
Question 673
A host reaches local devices but remote packets go to an obsolete gateway shown by ip route. What diagnostic result would demonstrate the target behavior?
- Use nmcli device wifi list and inspect connection logs after an attempted association.
- Inspect service states and verify the interface configuration is persistent after reboot.
- Compare lookups for the short name and the explicit FQDN under the same resolver.
- Use ip route get destination and compare path selection before and after.
Explanation
Correct Answer
D:Use ip route get destination and compare path selection before and after. This check is tied to the expected behavior rather than mere process uptime.
Incorrect Answers
A:Use nmcli device wifi list and inspect connection logs after an attempted association. could help with wi-fi network name and authentication; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use ip route get destination and compare path selection before and after.
B:nmcli controls NetworkManager profiles and cannot manage an unrelated active network stack by itself. That describes a different fault. Here, The default route's next hop is wrong for the current network segment.
C:Compare lookups for the short name and the explicit FQDN under the same resolver. could help with search suffix causes misleading name; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use ip route get destination and compare path selection before and after.
Question 674
A host reaches local devices but remote packets go to an obsolete gateway shown by ip route. What longer-term control best supports this requirement?
- Test both IPv4 and IPv6 profile persistence in dual-stack provisioning checks.
- Audit default routes after VLAN and subnet migrations.
- Use layered diagnostics rather than interpreting one ICMP result as application health.
- Manage DNS at its authoritative configuration layer instead of editing generated files.
Explanation
Correct Answer
B:Audit default routes after VLAN and subnet migrations. Sustained checks matter because The default route's next hop is wrong for the current network segment.
Incorrect Answers
A:Test both IPv4 and IPv6 profile persistence in dual-stack provisioning checks. could help with ipv6 disabled in a persistent profile; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use ip route get destination and compare path selection before and after.
C:Use layered diagnostics rather than interpreting one ICMP result as application health. belongs to a situation where ICMP echo tests basic reachability where permitted and can be filtered independently of an application. Here the evidence supports a different requirement: Audit default routes after VLAN and subnet migrations.
D:Manage DNS at its authoritative configuration layer instead of editing generated files. belongs to a situation where A network manager may regenerate resolver configuration from active connection properties. Here the evidence supports a different requirement: Audit default routes after VLAN and subnet migrations.
Question 675
A host reaches local devices but remote packets go to an obsolete gateway shown by ip route. Choose TWO case-specific steps: one that fixes the issue and one that proves the result.
- Use ip route get destination and compare path selection before and after.
- Include cold-boot network activation in server provisioning QA.
- Correct the default route via the approved on-link gateway and persist the configuration.
- Set ipv4.method manual with the intended address and gateway for a truly static configuration.
- Use ss -ltn and an SSH client to verify the server's actual configured listener.
Explanation
Correct Answers
A:Use ip route get destination and compare path selection before and after. This check is tied to the expected behavior rather than mere process uptime.
C:Correct the default route via the approved on-link gateway and persist the configuration. It corrects the mechanism identified in the scenario: The default route's next hop is wrong for the current network segment.
Incorrect Answers
B:Include cold-boot network activation in server provisioning QA. belongs to a situation where The saved NetworkManager profile may not be set to autoconnect on device availability. Here the evidence supports a different requirement: Audit default routes after VLAN and subnet migrations.
D:The test for static ipv4 method versus dhcp would be: Use nmcli -f ipv4.method,ipv4.addresses connection show and observe address state after activation. The relevant acceptance check here is: Use ip route get destination and compare path selection before and after.
E:It would address ssh and mail protocol ports rather than the present problem. The appropriate correction here is: Correct the default route via the approved on-link gateway and persist the configuration.
Question 676
An IPv4 host has a connected route but packets to an on-link peer fail and ip neigh shows INCOMPLETE. Which failure condition fits the evidence without assuming an unrelated fault?
- ARP neighbor discovery is not resolving the peer's link-layer address, suggesting a local link or peer problem.
- Application lookup may use NSS with files before DNS, while dig queries DNS directly.
- The hostname command can alter runtime state without changing the static hostname policy.
- A configured or caching resolver may differ from authoritative or alternative resolver results.
Explanation
Correct Answer
A:ARP neighbor discovery is not resolving the peer's link-layer address, suggesting a local link or peer problem. This is the explanation that justifies the specific remedy: Check VLAN/port state and peer address rather than immediately adding a remote default route.
Incorrect Answers
B:The test for nss hosts lookup order would be: Compare getent hosts and dig for the name and identify the selected source. The relevant acceptance check here is: Repeat traffic while inspecting ip neigh and the link's ARP frames.
C:This option assumes The hostname command can alter runtime state without changing the static hostname policy. The reported symptoms instead call for: Check VLAN/port state and peer address rather than immediately adding a remote default route.
D:A configured or caching resolver may differ from authoritative or alternative resolver results. That describes a different fault. Here, ARP neighbor discovery is not resolving the peer's link-layer address, suggesting a local link or peer problem.
Question 677
An IPv4 host has a connected route but packets to an on-link peer fail and ip neigh shows INCOMPLETE. Which change most directly meets the stated requirement?
- Identify the actual interface manager and use appropriate systemd-networkd configuration for this host.
- Check VLAN/port state and peer address rather than immediately adding a remote default route.
- Choose TCP when transport-level reliability is required or implement those controls in the UDP application.
- Correct the resolver's search list or use the intended fully qualified name.
Explanation
Correct Answer
B:Check VLAN/port state and peer address rather than immediately adding a remote default route. Unlike a broad workaround, it targets the observed cause: ARP neighbor discovery is not resolving the peer's link-layer address, suggesting a local link or peer problem.
Incorrect Answers
A:It would address systemd-networkd awareness rather than the present problem. The appropriate correction here is: Check VLAN/port state and peer address rather than immediately adding a remote default route.
C:It would address tcp versus udp application fit rather than the present problem. The appropriate correction here is: Check VLAN/port state and peer address rather than immediately adding a remote default route.
D:That choice responds to a search suffix causes misleading name failure. In this incident, ARP neighbor discovery is not resolving the peer's link-layer address, suggesting a local link or peer problem.
Question 678
An IPv4 host has a connected route but packets to an on-link peer fail and ip neigh shows INCOMPLETE. Which observation should be used for acceptance testing?
- Reconnect and inspect effective resolver configuration and a known DNS query.
- Check query results and TTLs from each resolver before deciding whether caching or source data differs.
- Repeat traffic while inspecting ip neigh and the link's ARP frames.
- Reboot a test system and inspect active connections without manual intervention.
Explanation
Correct Answer
C:Repeat traffic while inspecting ip neigh and the link's ARP frames. This check is tied to the expected behavior rather than mere process uptime.
Incorrect Answers
A:The test for persistent dns in managed connection would be: Reconnect and inspect effective resolver configuration and a known DNS query. The relevant acceptance check here is: Repeat traffic while inspecting ip neigh and the link's ARP frames.
B:This option assumes A configured or caching resolver may differ from authoritative or alternative resolver results. The reported symptoms instead call for: Check VLAN/port state and peer address rather than immediately adding a remote default route.
D:The test for autoconnect disabled would be: Reboot a test system and inspect active connections without manual intervention. The relevant acceptance check here is: Repeat traffic while inspecting ip neigh and the link's ARP frames.
Question 679
An IPv4 host has a connected route but packets to an on-link peer fail and ip neigh shows INCOMPLETE. What longer-term control best supports this requirement?
- Avoid relying on ambiguous single-label names across administrative zones.
- Include L2 neighbor evidence when diagnosing local-network reachability.
- Manage DNS at its authoritative configuration layer instead of editing generated files.
- Avoid hand-written IPv4-only parsing in dual-stack automation.
Explanation
Correct Answer
B:Include L2 neighbor evidence when diagnosing local-network reachability. It makes the outcome of the targeted repair (Check VLAN/port state and peer address rather than immediately adding a remote default route.) repeatable.
Incorrect Answers
A:This belongs to search suffix causes misleading name, where Resolver search-domain configuration can qualify a short name differently than the operator expects. The current issue instead is: ARP neighbor discovery is not resolving the peer's link-layer address, suggesting a local link or peer problem.
C:Manage DNS at its authoritative configuration layer instead of editing generated files. could help with persistent dns in managed connection; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Repeat traffic while inspecting ip neigh and the link's ARP frames.
D:Avoid hand-written IPv4-only parsing in dual-stack automation. could help with ipv6 address length; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Repeat traffic while inspecting ip neigh and the link's ARP frames.
Question 680
An IPv4 host has a connected route but packets to an on-link peer fail and ip neigh shows INCOMPLETE. Which THREE actions form a suitable remediation, verification and prevention plan? Select THREE.
- Compare the candidate address against RFC1918 ranges, including 10/8 and 192.168/16.
- Allocate at least a /27 network, which ordinarily provides 30 usable host addresses.
- Repeat traffic while inspecting ip neigh and the link's ARP frames.
- Include L2 neighbor evidence when diagnosing local-network reachability.
- Check VLAN/port state and peer address rather than immediately adding a remote default route.
- Model protocol and port combinations rather than assuming one transport for all DNS behavior.
Explanation
Correct Answers
C:Repeat traffic while inspecting ip neigh and the link's ARP frames. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: ARP neighbor discovery is not resolving the peer's link-layer address, suggesting a local link or peer problem.
D:Include L2 neighbor evidence when diagnosing local-network reachability. Sustained checks matter because ARP neighbor discovery is not resolving the peer's link-layer address, suggesting a local link or peer problem.
E:Check VLAN/port state and peer address rather than immediately adding a remote default route. The change should be accepted only after this test: Repeat traffic while inspecting ip neigh and the link's ARP frames.
Incorrect Answers
A:That choice responds to a rfc1918 private ipv4 failure. In this incident, ARP neighbor discovery is not resolving the peer's link-layer address, suggesting a local link or peer problem.
B:Allocate at least a /27 network, which ordinarily provides 30 usable host addresses. belongs to a situation where A /28 has 16 total addresses and ordinarily only 14 usable host addresses, so it cannot fit 25 hosts. Here the evidence supports a different requirement: Check VLAN/port state and peer address rather than immediately adding a remote default route.
F:This belongs to dns usually udp but can use tcp, where DNS commonly uses UDP and also uses TCP for responses and operations requiring it. The current issue instead is: ARP neighbor discovery is not resolving the peer's link-layer address, suggesting a local link or peer problem.
LPI Level 1 (102-500) Practice Tests