Pass LPI 102-500 Exam in First Attempt Guaranteed!
Get 100% Latest Exam Questions, Accurate & Verified Answers!
30 Days Free Updates, Instant Download!
LPI 102-500 Practice Test 68
Question 670
At fictional Redridge Insurance, the Linux network operations team is working while investigating an observed production-like support incident. The Linux scenario is: A host can ping peers on its directly connected subnet but cannot reach an approved remote subnet. The decisive evidence is: ip route displays only connected routes and no usable default or specific remote route. Which paired action and independent proof BEST satisfies the requirement?
Explanation
Correct Answer
A remote test subnet is reachable and local-subnet traffic remains on-link. Without that result, the finding ip route displays only connected routes and no usable default or specific remote route would remain unresolved.
Incorrect Answers
A test that scoped correction: Compare dig, getent and effective nsswitch sources; fix the actual NSS or resolver configuration. Independent acceptance: The application's standard name lookup and an appropriate DNS check both resolve the expected host would not demonstrate closure of this condition. The needed proof is a remote test subnet is reachable and local-subnet traffic remains on-link.
Scoped correction: Apply the approved CIDR prefix consistently and verify routing for nonlocal addresses. Independent acceptance: Hosts on the intended subnet communicate directly and external destinations use the gateway. That does not demonstrate the case-specific success condition: a remote test subnet is reachable and local-subnet traffic remains on-link. IP routing tables determine the path to remote addresses independently of DNS resolution.
Scoped correction: Configure DNS servers and search domains in the owning persistent network connection profile. Independent acceptance: After a DHCP renewal the intended resolvers appear in effective state and names resolve consistently. That result does not test the original problem, identified by ip route displays only connected routes and no usable default or specific remote route. Recovery must show that a remote test subnet is reachable and local-subnet traffic remains on-link.
Question 671
At fictional Harborview Library, the Linux network operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: A test host reports network unreachable to a neighbor because its address has an excessively narrow prefix. The diagnostic evidence is: ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. Which bounded step BEST resolves the described problem?
Explanation
Correct Answer
The case reveals ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. That matters because IP address prefix length determines whether a peer is on-link. The corrective step is to set the appropriate interface prefix and verify gateway and neighbor discovery behavior. Preserve this constraint during the change: Avoid treating a one-off ping fix as proof the persistent network profile is corrected.
Incorrect Answers
Another possible response is to restore the supported systemd-resolved stub integration and configure per-link DNS through the proper owner. The case evidence instead shows that ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. IP address prefix length determines whether a peer is on-link.
Permit the required approved DNS transport paths and validate both UDP and TCP resolution behavior. This does not address the reported incident: a test host reports network unreachable to a neighbor because its address has an excessively narrow prefix. Ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. The case-specific correction is to set the appropriate interface prefix and verify gateway and neighbor discovery behavior.
One alternative would be to set and verify the approved static hostname with the supported host configuration mechanism. The observed evidence instead shows that ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. The more relevant correction is to set the appropriate interface prefix and verify gateway and neighbor discovery behavior.
Question 672
At fictional Harborview Library, the Linux network operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: A test host reports network unreachable to a neighbor because its address has an excessively narrow prefix. Which observation MOST directly supports the underlying diagnosis before any changes are made?
Explanation
Correct Answer
Ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. It identifies the problem behind a test host reports network unreachable to a neighbor because its address has an excessively narrow prefix. IP address prefix length determines whether a peer is on-link.
Incorrect Answers
A competing Linux diagnostic finding for Harborview Library is: resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. It does not account for the observation ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route in the reported situation.
At Harborview Library, another diagnostic finding is: Diagnostics show UDP port 53 access is permitted while required large responses fall back to TCP and TCP 53 is blocked. This would indicate another failure; here ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. IP address prefix length determines whether a peer is on-link.
At Harborview Library, a different observation is: The runtime hostname differs from the configured static hostname reported by hostnamectl. It concerns another dependency. This incident is distinguished by ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. IP address prefix length determines whether a peer is on-link.
Question 673
At fictional Harborview Library, the Linux network operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: A test host reports network unreachable to a neighbor because its address has an excessively narrow prefix. The proposed intervention is: Set the appropriate interface prefix and verify gateway and neighbor discovery behavior. Which independent result BEST demonstrates a successful correction?
Explanation
Correct Answer
Success requires the authorized neighbor is reachable and the interface displays the correct connected route. That result tests the previously observed condition: ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. IP address prefix length determines whether a peer is on-link.
Incorrect Answers
At Harborview Library, another acceptance finding might be: An internal split-DNS name and an external name both resolve through approved resolvers. That would still leave the reported failure unproven. An acceptance test must show that the authorized neighbor is reachable and the interface displays the correct connected route.
At Harborview Library, a different acceptance result would be: A standard and a larger DNS response succeed through the intended IPv6 resolver. It may validate a separate setting, but not the required action: set the appropriate interface prefix and verify gateway and neighbor discovery behavior. The required observation is the authorized neighbor is reachable and the interface displays the correct connected route.
The independent acceptance evidence for Harborview Library is: After restart the host uses the intended name and /etc/hosts entries remain consistent with policy. The evidence relevant to this incident is ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. Confirm the corresponding recovery result: The authorized neighbor is reachable and the interface displays the correct connected route.
Question 674
At fictional Harborview Library, the Linux network operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: A test host reports network unreachable to a neighbor because its address has an excessively narrow prefix. The relevant evidence is: ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. Which Linux administration principle MOST accurately explains the correct response?
Explanation
Correct Answer
The governing distinction is that IP address prefix length determines whether a peer is on-link. Here, ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. Set the appropriate interface prefix and verify gateway and neighbor discovery behavior.
Incorrect Answers
A competing Linux principle for Harborview Library is: A local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server. The decisive observation, ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route, requires a different explanation: IP address prefix length determines whether a peer is on-link.
A different principle is: the relevant Linux system principle for Harborview Library is: DNS can use both UDP and TCP on port 53; IPv6 changes addressing but not that general requirement. The causal link actually supported by ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route is IP address prefix length determines whether a peer is on-link.
A competing Linux principle for Harborview Library is: Linux runtime hostname and durable hostname metadata are separate forms of configuration. However, it does not explain ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. The applicable principle is that IP address prefix length determines whether a peer is on-link.
Question 675
At fictional Harborview Library, the Linux network operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: A test host reports network unreachable to a neighbor because its address has an excessively narrow prefix. The decisive evidence is: ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. Which paired action and independent proof BEST satisfies the requirement?
Explanation
Correct Answer
Verify the change by checking that the authorized neighbor is reachable and the interface displays the correct connected route. The original clue was ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. The test is meaningful because IP address prefix length determines whether a peer is on-link.
Incorrect Answers
Even verifying scoped correction: Restore the supported systemd-resolved stub integration and configure per-link DNS through the proper owner. Independent acceptance: An internal split-DNS name and an external name both resolve through approved resolvers leaves the reported failure unproven. An acceptance test must show that the authorized neighbor is reachable and the interface displays the correct connected route.
The alternative outcome is scoped correction: Permit the required approved DNS transport paths and validate both UDP and TCP resolution behavior. Independent acceptance: A standard and a larger DNS response succeed through the intended IPv6 resolver. It may validate a separate setting, but not the required action: set the appropriate interface prefix and verify gateway and neighbor discovery behavior. The required observation is the authorized neighbor is reachable and the interface displays the correct connected route.
Scoped correction: Set and verify the approved static hostname with the supported host configuration mechanism. Independent acceptance: After restart the host uses the intended name and /etc/hosts entries remain consistent with policy. The evidence relevant to this incident is ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. Confirm the corresponding recovery result: The authorized neighbor is reachable and the interface displays the correct connected route.
Question 676
At fictional Oakridge Services, the Linux network operations team is working while investigating an observed production-like support incident. The Linux scenario is: A test host reports network unreachable to a neighbor because its address has an excessively narrow prefix. The diagnostic evidence is: ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. Which bounded step BEST resolves the described problem?
Explanation
Correct Answer
Ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. Instead of unrelated changes, set the appropriate interface prefix and verify gateway and neighbor discovery behavior. The expected result is the authorized neighbor is reachable and the interface displays the correct connected route. Preserve this constraint during the change: Avoid treating a one-off ping fix as proof the persistent network profile is corrected.
Incorrect Answers
Restore the supported systemd-resolved stub integration and configure per-link DNS through the proper owner. It could be useful for another problem, but it does not change ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. The response needs to set the appropriate interface prefix and verify gateway and neighbor discovery behavior.
An alternative action is permit the required approved DNS transport paths and validate both UDP and TCP resolution behavior. This incident instead involves ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. Confirm the scoped change through the authorized neighbor is reachable and the interface displays the correct connected route.
Set and verify the approved static hostname with the supported host configuration mechanism. That would not correct the reported ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. The supported response is to set the appropriate interface prefix and verify gateway and neighbor discovery behavior.
Question 677
At fictional Oakridge Services, the Linux network operations team is working while investigating an observed production-like support incident. The Linux scenario is: A test host reports network unreachable to a neighbor because its address has an excessively narrow prefix. Which observation MOST directly supports the underlying diagnosis before any changes are made?
Explanation
Correct Answer
Look for the recorded condition: Ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. That is decisive because IP address prefix length determines whether a peer is on-link. Correction should target set the appropriate interface prefix and verify gateway and neighbor discovery behavior.
Incorrect Answers
A competing Linux diagnostic finding for Oakridge Services is: resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. That finding does not isolate the reported issue: a test host reports network unreachable to a neighbor because its address has an excessively narrow prefix. The determining evidence is ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route.
At Oakridge Services, that alternative suggests: Diagnostics show UDP port 53 access is permitted while required large responses fall back to TCP and TCP 53 is blocked. The actual diagnostic record shows ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route instead. The difference matters because IP address prefix length determines whether a peer is on-link.
At Oakridge Services, another potential finding is: The runtime hostname differs from the configured static hostname reported by hostnamectl. That would not establish the cause here. Ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. The case-specific correction is to set the appropriate interface prefix and verify gateway and neighbor discovery behavior.
Question 678
At fictional Oakridge Services, the Linux network operations team is working while investigating an observed production-like support incident. The Linux scenario is: A test host reports network unreachable to a neighbor because its address has an excessively narrow prefix. The proposed intervention is: Set the appropriate interface prefix and verify gateway and neighbor discovery behavior. Which independent result BEST demonstrates a successful correction?
Explanation
Correct Answer
To close the incident, demonstrate that the authorized neighbor is reachable and the interface displays the correct connected route. That addresses ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route and reflects the rule that IP address prefix length determines whether a peer is on-link.
Incorrect Answers
A separate test at Oakridge Services could show: An internal split-DNS name and an external name both resolve through approved resolvers. That would not demonstrate closure of this condition. The needed proof is the authorized neighbor is reachable and the interface displays the correct connected route.
The independent acceptance evidence for Oakridge Services is: A standard and a larger DNS response succeed through the intended IPv6 resolver. That does not demonstrate the case-specific success condition: the authorized neighbor is reachable and the interface displays the correct connected route. IP address prefix length determines whether a peer is on-link.
The independent acceptance evidence for Oakridge Services is: After restart the host uses the intended name and /etc/hosts entries remain consistent with policy. That result does not test the original problem, identified by ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. Recovery must show that the authorized neighbor is reachable and the interface displays the correct connected route.
Question 679
At fictional Oakridge Services, the Linux network operations team is working while investigating an observed production-like support incident. The Linux scenario is: A test host reports network unreachable to a neighbor because its address has an excessively narrow prefix. The relevant evidence is: ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. Which Linux administration principle MOST accurately explains the correct response?
Explanation
Correct Answer
IP address prefix length determines whether a peer is on-link. That explains the observed condition: ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. The scoped response is to set the appropriate interface prefix and verify gateway and neighbor discovery behavior.
Incorrect Answers
At Oakridge Services, another Linux system principle is: A local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server. The present evidence is ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route, which instead follows from IP address prefix length determines whether a peer is on-link.
A competing Linux principle for Oakridge Services is: DNS can use both UDP and TCP on port 53; IPv6 changes addressing but not that general requirement. This describes another relationship, not the cause of a test host reports network unreachable to a neighbor because its address has an excessively narrow prefix. IP address prefix length determines whether a peer is on-link.
At Oakridge Services, a different Linux system principle is: Linux runtime hostname and durable hostname metadata are separate forms of configuration does not account for ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. This case is governed by IP address prefix length determines whether a peer is on-link.
Question 680
At fictional Oakridge Services, the Linux network operations team is working while investigating an observed production-like support incident. The Linux scenario is: A test host reports network unreachable to a neighbor because its address has an excessively narrow prefix. The decisive evidence is: ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. Which paired action and independent proof BEST satisfies the requirement?
Explanation
Correct Answer
The authorized neighbor is reachable and the interface displays the correct connected route. This measures whether the response corrected ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route rather than merely completing a configuration step.
Incorrect Answers
A test that scoped correction: Restore the supported systemd-resolved stub integration and configure per-link DNS through the proper owner. Independent acceptance: An internal split-DNS name and an external name both resolve through approved resolvers would not demonstrate closure of this condition. The needed proof is the authorized neighbor is reachable and the interface displays the correct connected route.
Scoped correction: Permit the required approved DNS transport paths and validate both UDP and TCP resolution behavior. Independent acceptance: A standard and a larger DNS response succeed through the intended IPv6 resolver. That does not demonstrate the case-specific success condition: the authorized neighbor is reachable and the interface displays the correct connected route. IP address prefix length determines whether a peer is on-link.
Scoped correction: Set and verify the approved static hostname with the supported host configuration mechanism. Independent acceptance: After restart the host uses the intended name and /etc/hosts entries remain consistent with policy. That result does not test the original problem, identified by ip address show shows /32 on a normal Ethernet subnet and the route table lacks a connected subnet route. Recovery must show that the authorized neighbor is reachable and the interface displays the correct connected route.
LPI Level 1 (102-500) Practice Tests
- LPI 102-500 Practice Test 66 - 10 Questions (Last Reviewed 08-Nov-2026)
- LPI 102-500 Practice Test 67 - 10 Questions (Last Reviewed 07-Nov-2026)
- LPI 102-500 Practice Test 68 - 10 Questions (Last Reviewed 06-Nov-2026)
- LPI 102-500 Practice Test 69 - 10 Questions (Last Reviewed 05-Nov-2026)
- LPI 102-500 Practice Test 70 - 10 Questions (Last Reviewed 04-Nov-2026)
