100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 720
A multi-address host reaches a remote service only when the source address is specified manually. Choose THREE measures that together correct the failure, demonstrate success and reduce recurrence.
- Inspect ip route get with source and interface context, then adjust source policy or route configuration safely.
- Provision Wi-Fi security profiles securely rather than embedding plaintext passwords in scripts.
- Assign the intended interface to the correct profile and review autoconnect priority for competing profiles.
- Check nmcli connection IPv6 method, ip -6 addr and ip -6 route after a clean reconnect.
- Record intended source identities for multi-homed application traffic.
- Capture the actual packet source and compare it with the service's allowlist.
Explanation
Correct Answers
A:Inspect ip route get with source and interface context, then adjust source policy or route configuration safely. This is appropriate because Source address selection and policy routing can choose an unintended outbound identity.
E:Record intended source identities for multi-homed application traffic. It makes the outcome of the targeted repair (Inspect ip route get with source and interface context, then adjust source policy or route configuration safely.) repeatable.
F:Capture the actual packet source and compare it with the service's allowlist. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: Source address selection and policy routing can choose an unintended outbound identity.
Incorrect Answers
B:The test for wi-fi network name and authentication would be: Use nmcli device wifi list and inspect connection logs after an attempted association. The relevant acceptance check here is: Capture the actual packet source and compare it with the service's allowlist.
C:It would address multiple saved profiles for one device rather than the present problem. The appropriate correction here is: Inspect ip route get with source and interface context, then adjust source policy or route configuration safely.
D:Check nmcli connection IPv6 method, ip -6 addr and ip -6 route after a clean reconnect. could help with ipv6 disabled in a persistent profile; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Capture the actual packet source and compare it with the service's allowlist.
Question 721
A host's application resolves a name to /etc/hosts while dig reports a different DNS address. Which failure condition fits the evidence without assuming an unrelated fault?
- An IPv4 default route does not substitute for IPv6 routing information.
- The hostname command can alter runtime state without changing the static hostname policy.
- Application lookup may use NSS with files before DNS, while dig queries DNS directly.
- nmcli controls NetworkManager profiles and cannot manage an unrelated active network stack by itself.
Explanation
Correct Answer
C:Application lookup may use NSS with files before DNS, while dig queries DNS directly. The observation is consistent with this mechanism; a targeted repair would be: Inspect /etc/nsswitch.conf hosts order and remove the stale local mapping if not required.
Incorrect Answers
A:This belongs to ipv6 route omission, where An IPv4 default route does not substitute for IPv6 routing information. The current issue instead is: Application lookup may use NSS with files before DNS, while dig queries DNS directly.
B:The hostname command can alter runtime state without changing the static hostname policy. belongs to a situation where The hostname command can alter runtime state without changing the static hostname policy. Here the evidence supports a different requirement: Application lookup may use NSS with files before DNS, while dig queries DNS directly.
D:It would address systemd-networkd awareness rather than the present problem. The appropriate correction here is: Inspect /etc/nsswitch.conf hosts order and remove the stale local mapping if not required.
Question 722
A host's application resolves a name to /etc/hosts while dig reports a different DNS address. Which change most directly meets the stated requirement?
- Set the static hostname using hostnamectl or the distribution's supported persistent configuration.
- Inspect /etc/nsswitch.conf hosts order and remove the stale local mapping if not required.
- Activate or reapply the modified connection using an approved nmcli operation with safe remote-access planning.
- Use ip link set dev interface up after confirming the intended port and policy.
Explanation
Correct Answer
B:Inspect /etc/nsswitch.conf hosts order and remove the stale local mapping if not required. It addresses the root cause, while Track local hostname overrides that supersede DNS in incident playbooks. reduces future recurrence.
Incorrect Answers
A:This option assumes The hostname command can alter runtime state without changing the static hostname policy. The reported symptoms instead call for: Inspect /etc/nsswitch.conf hosts order and remove the stale local mapping if not required.
C:Activate or reapply the modified connection using an approved nmcli operation with safe remote-access planning. could help with bring up modified networkmanager profile; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Compare getent hosts and dig for the name and identify the selected source.
D:An administratively down interface cannot pass ordinary traffic until brought up. That describes a different fault. Here, Application lookup may use NSS with files before DNS, while dig queries DNS directly.
Question 723
A host's application resolves a name to /etc/hosts while dig reports a different DNS address. What focused test would distinguish a real correction from a cosmetic change?
- Inspect service states and verify the interface configuration is persistent after reboot.
- Compare getent hosts and dig for the name and identify the selected source.
- Compare a local listener test with network captures and remote TCP connection behavior.
- Use nmcli device wifi list and inspect connection logs after an attempted association.
Explanation
Correct Answer
B:Compare getent hosts and dig for the name and identify the selected source. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
Incorrect Answers
A: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 getent hosts and dig for the name and identify the selected source.
C:That choice responds to a timeout versus refusal failure. In this incident, Application lookup may use NSS with files before DNS, while dig queries DNS directly.
D:SSID selection alone is insufficient when the wireless security and credentials do not match the access point. That describes a different fault. Here, Application lookup may use NSS with files before DNS, while dig queries DNS directly.
Question 724
A host's application resolves a name to /etc/hosts while dig reports a different DNS address. What should the team standardize to prevent similar incidents?
- Test address assignment separately from physical carrier and routing.
- Maintain an authoritative private-address plan and avoid blanket assumptions from the first octet.
- Track local hostname overrides that supersede DNS in incident playbooks.
- Select transport protocols from delivery guarantees and latency needs, not port numbers alone.
Explanation
Correct Answer
C:Track local hostname overrides that supersede DNS in incident playbooks. It preserves the corrective behavior established through: Inspect /etc/nsswitch.conf hosts order and remove the stale local mapping if not required.
Incorrect Answers
A:Test address assignment separately from physical carrier and routing. belongs to a situation where Layer-two link state does not imply that an IPv4 or IPv6 address has been configured. Here the evidence supports a different requirement: Track local hostname overrides that supersede DNS in incident playbooks.
B:That choice responds to a rfc1918 private ipv4 failure. In this incident, Application lookup may use NSS with files before DNS, while dig queries DNS directly.
D:Select transport protocols from delivery guarantees and latency needs, not port numbers alone. belongs to a situation where UDP datagrams do not inherently provide TCP's reliable stream, retransmission and ordering guarantees. Here the evidence supports a different requirement: Track local hostname overrides that supersede DNS in incident playbooks.
Question 725
A host's application resolves a name to /etc/hosts while dig reports a different DNS address. Select TWO justified actions that address this particular problem and confirm closure.
- Compare getent hosts and dig for the name and identify the selected source.
- Reboot a test system and inspect active connections without manual intervention.
- Inspect /etc/nsswitch.conf hosts order and remove the stale local mapping if not required.
- Avoid hand-written IPv4-only parsing in dual-stack automation.
- Change the connection profile to an approved IPv6 auto method and reactivate it under a controlled rollback plan.
Explanation
Correct Answers
A:Compare getent hosts and dig for the name and identify the selected source. The test is evidence-based because the underlying failure was: Application lookup may use NSS with files before DNS, while dig queries DNS directly.
C:Inspect /etc/nsswitch.conf hosts order and remove the stale local mapping if not required. Unlike a broad workaround, it targets the observed cause: Application lookup may use NSS with files before DNS, while dig queries DNS directly.
Incorrect Answers
B:That choice responds to a autoconnect disabled failure. In this incident, Application lookup may use NSS with files before DNS, while dig queries DNS directly.
D:The test for ipv6 address length would be: Parse a compressed IPv6 address and check it round-trips without truncation. The relevant acceptance check here is: Compare getent hosts and dig for the name and identify the selected source.
E:The saved NetworkManager profile has IPv6 disabled, so router advertisements cannot supply the intended host configuration. That describes a different fault. Here, Application lookup may use NSS with files before DNS, while dig queries DNS directly.
Question 726
A host's IP connectivity is healthy but every public hostname lookup fails; /etc/resolv.conf points to a retired resolver. Which diagnosis is supported by the observations?
- The saved NetworkManager profile has IPv6 disabled, so router advertisements cannot supply the intended host configuration.
- The client resolver is sending queries to an unavailable configured DNS server.
- Standard SSH service is TCP 22; SMTP mail transfer commonly uses TCP 25.
- SSID selection alone is insufficient when the wireless security and credentials do not match the access point.
Explanation
Correct Answer
B:The client resolver is sending queries to an unavailable configured DNS server. A good follow-up is to test this explanation through: Use dig against the configured server and an alternate known-good server to isolate the issue.
Incorrect Answers
A:This belongs to ipv6 disabled in a persistent profile, where The saved NetworkManager profile has IPv6 disabled, so router advertisements cannot supply the intended host configuration. The current issue instead is: The client resolver is sending queries to an unavailable configured DNS server.
C:This option assumes Standard SSH service is TCP 22; SMTP mail transfer commonly uses TCP 25. The reported symptoms instead call for: Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits.
D:This option assumes SSID selection alone is insufficient when the wireless security and credentials do not match the access point. The reported symptoms instead call for: Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits.
Question 727
A host's IP connectivity is healthy but every public hostname lookup fails; /etc/resolv.conf points to a retired resolver. What should the administrator do to correct this behavior?
- Apply the correct dynamic or static address to the proper interface using the authoritative manager.
- Investigate cable, optics, NIC, duplex and receive queue behavior based on the actual counter pattern.
- Inspect and adjust the relevant route metrics or NetworkManager profile priorities.
- Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits.
Explanation
Correct Answer
D:Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits. It addresses the root cause, while Monitor DNS resolver availability and configuration provenance. reduces future recurrence.
Incorrect Answers
A:Apply the correct dynamic or static address to the proper interface using the authoritative manager. belongs to a situation where Layer-two link state does not imply that an IPv4 or IPv6 address has been configured. Here the evidence supports a different requirement: Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits.
B:Physical/link or buffering issues are indicated by interface statistics, not necessarily a DNS fault. That describes a different fault. Here, The client resolver is sending queries to an unavailable configured DNS server.
C:Inspect and adjust the relevant route metrics or NetworkManager profile priorities. could help with unexpected route metric; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use dig against the configured server and an alternate known-good server to isolate the issue.
Question 728
A host's IP connectivity is healthy but every public hostname lookup fails; /etc/resolv.conf points to a retired resolver. Which observation should be used for acceptance testing?
- Use ip -6 route get and ping -6 to a known reachable IPv6 endpoint.
- Check ip addr show dev interface and run an on-link test to confirm reachability.
- Use dig against the configured server and an alternate known-good server to isolate the issue.
- Use ip route get for a target and verify the selected outgoing interface.
Explanation
Correct Answer
C:Use dig against the configured server and an alternate known-good server to isolate the issue. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
Incorrect Answers
A:That choice responds to a ipv6 route omission failure. In this incident, The client resolver is sending queries to an unavailable configured DNS server.
B:Check ip addr show dev interface and run an on-link test to confirm reachability. belongs to a situation where Layer-two link state does not imply that an IPv4 or IPv6 address has been configured. Here the evidence supports a different requirement: Use dig against the configured server and an alternate known-good server to isolate the issue.
D:It would address unexpected route metric rather than the present problem. The appropriate correction here is: Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits.
Question 729
A host's IP connectivity is healthy but every public hostname lookup fails; /etc/resolv.conf points to a retired resolver. Which ongoing control would best reduce the chance of the issue returning?
- Monitor DNS resolver availability and configuration provenance.
- Manage DNS at its authoritative configuration layer instead of editing generated files.
- Audit DHCP versus static intent for each deployment role.
- Maintain an authoritative private-address plan and avoid blanket assumptions from the first octet.
Explanation
Correct Answer
A:Monitor DNS resolver availability and configuration provenance. The underlying risk is The client resolver is sending queries to an unavailable configured DNS server.
Incorrect Answers
B: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: Use dig against the configured server and an alternate known-good server to isolate the issue.
C:This belongs to static ipv4 method versus dhcp, where The active profile's automatic method permits DHCP to supply network settings. The current issue instead is: The client resolver is sending queries to an unavailable configured DNS server.
D:It would address rfc1918 private ipv4 rather than the present problem. The appropriate correction here is: Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits.
Question 730
A host's IP connectivity is healthy but every public hostname lookup fails; /etc/resolv.conf points to a retired resolver. Select THREE measures that follow directly from the root cause and lifecycle risk.
- Drop and reorder packets in a test and observe how the application handles missing data.
- Monitor DNS resolver availability and configuration provenance.
- Change the connection profile to an approved IPv6 auto method and reactivate it under a controlled rollback plan.
- Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits.
- Use dig against the configured server and an alternate known-good server to isolate the issue.
- Test both IPv4 and IPv6 profile persistence in dual-stack provisioning checks.
Explanation
Correct Answers
B:Monitor DNS resolver availability and configuration provenance. It preserves the corrective behavior established through: Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits.
D:Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits. This is appropriate because The client resolver is sending queries to an unavailable configured DNS server.
E:Use dig against the configured server and an alternate known-good server to isolate the issue. The test is evidence-based because the underlying failure was: The client resolver is sending queries to an unavailable configured DNS server.
Incorrect Answers
A:This option assumes UDP datagrams do not inherently provide TCP's reliable stream, retransmission and ordering guarantees. The reported symptoms instead call for: Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits.
C:It would address ipv6 disabled in a persistent profile rather than the present problem. The appropriate correction here is: Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits.
F:That choice responds to a ipv6 disabled in a persistent profile failure. In this incident, The client resolver is sending queries to an unavailable configured DNS server.
LPI Level 1 (102-500) Practice Tests