100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 550
A host at 192.0.2.63/26 is assumed to be an ordinary unicast endpoint in the first /26 network. Select THREE measures that follow directly from the root cause and lifecycle risk.
- Review IPv4 and IPv6 routing as independent protocol planes.
- Check first and last subnet addresses before IP assignment.
- Use ip route get for a target and verify the selected outgoing interface.
- Assign an address between .1 and .62 for a host in that specific /26 network.
- Use ip link set dev interface up after confirming the intended port and policy.
- Compute the network and broadcast addresses using the mask and confirm the host configuration.
Explanation
Correct Answers
B:Check first and last subnet addresses before IP assignment. It makes the outcome of the targeted repair (Assign an address between .1 and .62 for a host in that specific /26 network.) repeatable.
D:Assign an address between .1 and .62 for a host in that specific /26 network. The change should be accepted only after this test: Compute the network and broadcast addresses using the mask and confirm the host configuration.
F:Compute the network and broadcast addresses using the mask and confirm the host configuration. This measures the specific result of applying: Assign an address between .1 and .62 for a host in that specific /26 network.
Incorrect Answers
A:This option assumes An IPv4 default route does not substitute for IPv6 routing information. The reported symptoms instead call for: Assign an address between .1 and .62 for a host in that specific /26 network.
C:That choice responds to a unexpected route metric failure. In this incident, For 192.0.2.0/26, address .63 is the broadcast address, not a usable host address.
E:An administratively down interface cannot pass ordinary traffic until brought up. That describes a different fault. Here, For 192.0.2.0/26, address .63 is the broadcast address, not a usable host address.
Question 551
A workstation is configured with 172.32.5.9 and a colleague assumes every 172.x address is RFC1918 private space. Which diagnosis is supported by the observations?
- The resolver's search list affects qualification of unqualified hostnames.
- Application lookup may use NSS with files before DNS, while dig queries DNS directly.
- A timeout can indicate drops or path loss; a received refusal indicates an endpoint actively rejected the connection.
- Only 172.16.0.0 through 172.31.255.255 belongs to the 172.16/12 private range.
Explanation
Correct Answer
D:Only 172.16.0.0 through 172.31.255.255 belongs to the 172.16/12 private range. A good follow-up is to test this explanation through: Compare the candidate address against RFC1918 ranges, including 10/8 and 192.168/16.
Incorrect Answers
A:The resolver's search list affects qualification of unqualified hostnames. That describes a different fault. Here, Only 172.16.0.0 through 172.31.255.255 belongs to the 172.16/12 private range.
B:This option assumes Application lookup may use NSS with files before DNS, while dig queries DNS directly. The reported symptoms instead call for: Use a valid internal private range or plan routing for a properly assigned public address.
C:It would address timeout versus refusal rather than the present problem. The appropriate correction here is: Use a valid internal private range or plan routing for a properly assigned public address.
Question 552
A workstation is configured with 172.32.5.9 and a colleague assumes every 172.x address is RFC1918 private space. What should the administrator do to correct this behavior?
- Use a valid internal private range or plan routing for a properly assigned public address.
- Identify the actual interface manager and use appropriate systemd-networkd configuration for this host.
- Change the connection profile to an approved IPv6 auto method and reactivate it under a controlled rollback plan.
- Review the saved profile's interface name and MAC match and update it for the authorized adapter.
Explanation
Correct Answer
A:Use a valid internal private range or plan routing for a properly assigned public address. It corrects the mechanism identified in the scenario: Only 172.16.0.0 through 172.31.255.255 belongs to the 172.16/12 private range.
Incorrect Answers
B:The test for systemd-networkd awareness would be: Inspect service states and verify the interface configuration is persistent after reboot. The relevant acceptance check here is: Compare the candidate address against RFC1918 ranges, including 10/8 and 192.168/16.
C:The test for ipv6 disabled in a persistent profile would be: Check nmcli connection IPv6 method, ip -6 addr and ip -6 route after a clean reconnect. The relevant acceptance check here is: Compare the candidate address against RFC1918 ranges, including 10/8 and 192.168/16.
D:That choice responds to a wired mac and device association failure. In this incident, Only 172.16.0.0 through 172.31.255.255 belongs to the 172.16/12 private range.
Question 553
A workstation is configured with 172.32.5.9 and a colleague assumes every 172.x address is RFC1918 private space. What diagnostic result would demonstrate the target behavior?
- Compare the candidate address against RFC1918 ranges, including 10/8 and 192.168/16.
- Compare short-name and fully qualified getent lookups after reconnect.
- Use resolvectl query and compare with a direct upstream query to trace the chain.
- Query the authoritative/approved DNS source for the exact FQDN and inspect the returned status.
Explanation
Correct Answer
A:Compare the candidate address against RFC1918 ranges, including 10/8 and 192.168/16. This check is tied to the expected behavior rather than mere process uptime.
Incorrect Answers
B:The resolver's search list affects qualification of unqualified hostnames. That describes a different fault. Here, Only 172.16.0.0 through 172.31.255.255 belongs to the 172.16/12 private range.
C:Use resolvectl query and compare with a direct upstream query to trace the chain. could help with systemd-resolved stub target; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Compare the candidate address against RFC1918 ranges, including 10/8 and 192.168/16.
D:NXDOMAIN indicates a negative name response, not by itself a broken physical network connection. That describes a different fault. Here, Only 172.16.0.0 through 172.31.255.255 belongs to the 172.16/12 private range.
Question 554
A workstation is configured with 172.32.5.9 and a colleague assumes every 172.x address is RFC1918 private space. Which repeatable check would reduce recurrence?
- Maintain stable host identities through declarative provisioning.
- Maintain an authoritative private-address plan and avoid blanket assumptions from the first octet.
- Audit DHCP versus static intent for each deployment role.
- Monitor DNS resolver availability and configuration provenance.
Explanation
Correct Answer
B:Maintain an authoritative private-address plan and avoid blanket assumptions from the first octet. It prevents repetition of the condition: Only 172.16.0.0 through 172.31.255.255 belongs to the 172.16/12 private range.
Incorrect Answers
A:That choice responds to a host name managed by hostnamectl failure. In this incident, Only 172.16.0.0 through 172.31.255.255 belongs to the 172.16/12 private range.
C:This option assumes The active profile's automatic method permits DHCP to supply network settings. The reported symptoms instead call for: Use a valid internal private range or plan routing for a properly assigned public address.
D:It would address resolver nameserver failure rather than the present problem. The appropriate correction here is: Use a valid internal private range or plan routing for a properly assigned public address.
Question 555
A workstation is configured with 172.32.5.9 and a colleague assumes every 172.x address is RFC1918 private space. Which TWO options provide a coherent remediation-and-test response to this incident?
- Compare the candidate address against RFC1918 ranges, including 10/8 and 192.168/16.
- Use a valid internal private range or plan routing for a properly assigned public address.
- Check query results and TTLs from each resolver before deciding whether caching or source data differs.
- Choose one authoritative network-management stack per interface.
- Configure the connection with the approved SSID and authentication settings using NetworkManager.
Explanation
Correct Answers
A:Compare the candidate address against RFC1918 ranges, including 10/8 and 192.168/16. It verifies that the targeted action (Use a valid internal private range or plan routing for a properly assigned public address.) achieved its intended outcome.
B:Use a valid internal private range or plan routing for a properly assigned public address. It addresses the root cause, while Maintain an authoritative private-address plan and avoid blanket assumptions from the first octet. reduces future recurrence.
Incorrect Answers
C:The test for explicit dns server comparison would be: Check query results and TTLs from each resolver before deciding whether caching or source data differs. The relevant acceptance check here is: Compare the candidate address against RFC1918 ranges, including 10/8 and 192.168/16.
D:That choice responds to a systemd-networkd awareness failure. In this incident, Only 172.16.0.0 through 172.31.255.255 belongs to the 172.16/12 private range.
E:This belongs to wi-fi network name and authentication, where SSID selection alone is insufficient when the wireless security and credentials do not match the access point. The current issue instead is: Only 172.16.0.0 through 172.31.255.255 belongs to the 172.16/12 private range.
Question 556
Two interfaces on different routed segments use fe80:: addresses and an operator tries to reach a remote link-local target through a router. Which diagnosis is supported by the observations?
- Source address selection and policy routing can choose an unintended outbound identity.
- The resolver's search list affects qualification of unqualified hostnames.
- IPv6 link-local addresses are scoped to one link and are not routed across ordinary network boundaries.
- NXDOMAIN indicates a negative name response, not by itself a broken physical network connection.
Explanation
Correct Answer
C:IPv6 link-local addresses are scoped to one link and are not routed across ordinary network boundaries. The observation is consistent with this mechanism; a targeted repair would be: Use an appropriate routable IPv6 destination or specify the correct on-link interface zone for local access.
Incorrect Answers
A:This belongs to wrong source address selection, where Source address selection and policy routing can choose an unintended outbound identity. The current issue instead is: IPv6 link-local addresses are scoped to one link and are not routed across ordinary network boundaries.
B:The resolver's search list affects qualification of unqualified hostnames. belongs to a situation where The resolver's search list affects qualification of unqualified hostnames. Here the evidence supports a different requirement: IPv6 link-local addresses are scoped to one link and are not routed across ordinary network boundaries.
D:The test for dns record absent versus network down would be: Query the authoritative/approved DNS source for the exact FQDN and inspect the returned status. The relevant acceptance check here is: Check ip -6 addr and ping with the correct interface scope to an on-link neighbor.
Question 557
Two interfaces on different routed segments use fe80:: addresses and an operator tries to reach a remote link-local target through a router. Which remedial step follows from the observed mechanism?
- Use an appropriate routable IPv6 destination or specify the correct on-link interface zone for local access.
- Inspect /etc/nsswitch.conf hosts order and remove the stale local mapping if not required.
- Check routing, filtering and packet reachability before concluding the service is absent.
- Set DNS servers and search domains in the appropriate NetworkManager connection profile or resolver manager.
Explanation
Correct Answer
A:Use an appropriate routable IPv6 destination or specify the correct on-link interface zone for local access. It is the direct response; verify the result by: Check ip -6 addr and ping with the correct interface scope to an on-link neighbor.
Incorrect Answers
B:It would address nss hosts lookup order rather than the present problem. The appropriate correction here is: Use an appropriate routable IPv6 destination or specify the correct on-link interface zone for local access.
C:A timeout can indicate drops or path loss; a received refusal indicates an endpoint actively rejected the connection. That describes a different fault. Here, IPv6 link-local addresses are scoped to one link and are not routed across ordinary network boundaries.
D:Set DNS servers and search domains in the appropriate NetworkManager connection profile or resolver manager. belongs to a situation where A network manager may regenerate resolver configuration from active connection properties. Here the evidence supports a different requirement: Use an appropriate routable IPv6 destination or specify the correct on-link interface zone for local access.
Question 558
Two interfaces on different routed segments use fe80:: addresses and an operator tries to reach a remote link-local target through a router. How should the administrator verify the required behavior?
- Use ss -ltnp and a local TCP connection test before testing remotely.
- Use ip route get for a target and verify the selected outgoing interface.
- Compare a local listener test with network captures and remote TCP connection behavior.
- Check ip -6 addr and ping with the correct interface scope to an on-link neighbor.
Explanation
Correct Answer
D:Check ip -6 addr and ping with the correct interface scope to an on-link neighbor. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
Incorrect Answers
A:The test for listener missing on local port would be: Use ss -ltnp and a local TCP connection test before testing remotely. The relevant acceptance check here is: Check ip -6 addr and ping with the correct interface scope to an on-link neighbor.
B:Use ip route get for a target and verify the selected outgoing interface. could help with unexpected route metric; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Check ip -6 addr and ping with the correct interface scope to an on-link neighbor.
C:The test for timeout versus refusal would be: Compare a local listener test with network captures and remote TCP connection behavior. The relevant acceptance check here is: Check ip -6 addr and ping with the correct interface scope to an on-link neighbor.
Question 559
Two interfaces on different routed segments use fe80:: addresses and an operator tries to reach a remote link-local target through a router. Which ongoing control would best reduce the chance of the issue returning?
- Include protocol-specific checks for important service dependencies.
- Record interface scope and address type when debugging IPv6 endpoints.
- Record intended source identities for multi-homed application traffic.
- Test address assignment separately from physical carrier and routing.
Explanation
Correct Answer
B:Record interface scope and address type when debugging IPv6 endpoints. It prevents repetition of the condition: IPv6 link-local addresses are scoped to one link and are not routed across ordinary network boundaries.
Incorrect Answers
A:It would address network port test without application protocol rather than the present problem. The appropriate correction here is: Use an appropriate routable IPv6 destination or specify the correct on-link interface zone for local access.
C:It would address wrong source address selection rather than the present problem. The appropriate correction here is: Use an appropriate routable IPv6 destination or specify the correct on-link interface zone for local access.
D:This belongs to missing address on live interface, where Layer-two link state does not imply that an IPv4 or IPv6 address has been configured. The current issue instead is: IPv6 link-local addresses are scoped to one link and are not routed across ordinary network boundaries.
Question 560
Two interfaces on different routed segments use fe80:: addresses and an operator tries to reach a remote link-local target through a router. Which THREE actions form a suitable remediation, verification and prevention plan? Select THREE.
- Check ip -6 addr and ping with the correct interface scope to an on-link neighbor.
- Test address assignment separately from physical carrier and routing.
- Set DNS servers and search domains in the appropriate NetworkManager connection profile or resolver manager.
- Use an appropriate routable IPv6 destination or specify the correct on-link interface zone for local access.
- Compare counter deltas under load and after replacing a suspected link component.
- Record interface scope and address type when debugging IPv6 endpoints.
Explanation
Correct Answers
A:Check ip -6 addr and ping with the correct interface scope to an on-link neighbor. It verifies that the targeted action (Use an appropriate routable IPv6 destination or specify the correct on-link interface zone for local access.) achieved its intended outcome.
D:Use an appropriate routable IPv6 destination or specify the correct on-link interface zone for local access. It is the direct response; verify the result by: Check ip -6 addr and ping with the correct interface scope to an on-link neighbor.
F:Record interface scope and address type when debugging IPv6 endpoints. Sustained checks matter because IPv6 link-local addresses are scoped to one link and are not routed across ordinary network boundaries.
Incorrect Answers
B:It would address missing address on live interface rather than the present problem. The appropriate correction here is: Use an appropriate routable IPv6 destination or specify the correct on-link interface zone for local access.
C:This belongs to persistent dns in managed connection, where A network manager may regenerate resolver configuration from active connection properties. The current issue instead is: IPv6 link-local addresses are scoped to one link and are not routed across ordinary network boundaries.
E:Compare counter deltas under load and after replacing a suspected link component. belongs to a situation where Physical/link or buffering issues are indicated by interface statistics, not necessarily a DNS fault. Here the evidence supports a different requirement: Check ip -6 addr and ping with the correct interface scope to an on-link neighbor.
LPI Level 1 (102-500) Practice Tests