100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 690
A TCP connection attempt hangs until timeout, but a colleague diagnoses it as definite evidence that no process is listening. Which THREE case-specific steps cover immediate repair, test evidence and sustained control?
- Check routing, filtering and packet reachability before concluding the service is absent.
- Document search domains explicitly to avoid ambiguous short-name resolution.
- Compare getent hosts and dig for the name and identify the selected source.
- Set the static hostname using hostnamectl or the distribution's supported persistent configuration.
- Document timeout and refusal as distinct evidence types in runbooks.
- Compare a local listener test with network captures and remote TCP connection behavior.
Explanation
Correct Answers
A:Check routing, filtering and packet reachability before concluding the service is absent. It corrects the mechanism identified in the scenario: A timeout can indicate drops or path loss; a received refusal indicates an endpoint actively rejected the connection.
E:Document timeout and refusal as distinct evidence types in runbooks. Sustained checks matter because A timeout can indicate drops or path loss; a received refusal indicates an endpoint actively rejected the connection.
F:Compare a local listener test with network captures and remote TCP connection behavior. It verifies that the targeted action (Check routing, filtering and packet reachability before concluding the service is absent.) achieved its intended outcome.
Incorrect Answers
B:Document search domains explicitly to avoid ambiguous short-name resolution. belongs to a situation where The resolver's search list affects qualification of unqualified hostnames. Here the evidence supports a different requirement: Document timeout and refusal as distinct evidence types in runbooks.
C:It would address nss hosts lookup order rather than the present problem. The appropriate correction here is: Check routing, filtering and packet reachability before concluding the service is absent.
D:The test for host name managed by hostnamectl would be: Reboot and compare hostnamectl status with hostname output. The relevant acceptance check here is: Compare a local listener test with network captures and remote TCP connection behavior.
Question 691
A laptop has Ethernet and Wi-Fi default routes, but traffic leaves over the slower Wi-Fi link. Which mechanism best explains the difference between expectation and result?
- A network manager may regenerate resolver configuration from active connection properties.
- The hostname command can alter runtime state without changing the static hostname policy.
- Routing preference can depend on metrics when multiple eligible routes share a destination prefix.
- The client resolver is sending queries to an unavailable configured DNS server.
Explanation
Correct Answer
C:Routing preference can depend on metrics when multiple eligible routes share a destination prefix. The observation is consistent with this mechanism; a targeted repair would be: Inspect and adjust the relevant route metrics or NetworkManager profile priorities.
Incorrect Answers
A:That choice responds to a persistent dns in managed connection failure. In this incident, Routing preference can depend on metrics when multiple eligible routes share a destination prefix.
B:That choice responds to a host name managed by hostnamectl failure. In this incident, Routing preference can depend on metrics when multiple eligible routes share a destination prefix.
D:The client resolver is sending queries to an unavailable configured DNS server. could help with resolver nameserver failure; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use ip route get for a target and verify the selected outgoing interface.
Question 692
A laptop has Ethernet and Wi-Fi default routes, but traffic leaves over the slower Wi-Fi link. Which configuration approach is appropriate for this requirement?
- Allocate at least a /27 network, which ordinarily provides 30 usable host addresses.
- Inspect and adjust the relevant route metrics or NetworkManager profile priorities.
- Enable connection.autoconnect for the correct profile and interface under policy.
- Permit policy-approved HTTPS egress on the correct transport and destination ranges.
Explanation
Correct Answer
B:Inspect and adjust the relevant route metrics or NetworkManager profile priorities. This is appropriate because Routing preference can depend on metrics when multiple eligible routes share a destination prefix.
Incorrect Answers
A:That choice responds to a ipv4 /27 address plan failure. In this incident, Routing preference can depend on metrics when multiple eligible routes share a destination prefix.
C:The test for autoconnect disabled would be: Reboot a test system and inspect active connections without manual intervention. The relevant acceptance check here is: Use ip route get for a target and verify the selected outgoing interface.
D:Permit policy-approved HTTPS egress on the correct transport and destination ranges. could help with tls application port; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use ip route get for a target and verify the selected outgoing interface.
Question 693
A laptop has Ethernet and Wi-Fi default routes, but traffic leaves over the slower Wi-Fi link. How should the administrator verify the required behavior?
- Compare the candidate address against RFC1918 ranges, including 10/8 and 192.168/16.
- List connection profiles and check which UUID becomes active after reboot.
- Use ip route get for a target and verify the selected outgoing interface.
- Use resolvectl query and compare with a direct upstream query to trace the chain.
Explanation
Correct Answer
C:Use ip route get for a target and verify the selected outgoing interface. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
Incorrect Answers
A:Compare the candidate address against RFC1918 ranges, including 10/8 and 192.168/16. could help with rfc1918 private ipv4; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use ip route get for a target and verify the selected outgoing interface.
B:It would address multiple saved profiles for one device rather than the present problem. The appropriate correction here is: Inspect and adjust the relevant route metrics or NetworkManager profile priorities.
D:That choice responds to a systemd-resolved stub target failure. In this incident, Routing preference can depend on metrics when multiple eligible routes share a destination prefix.
Question 694
A laptop has Ethernet and Wi-Fi default routes, but traffic leaves over the slower Wi-Fi link. What should the team standardize to prevent similar incidents?
- Specify multi-homed route preferences and test after interface reconnects.
- Document local stub and upstream resolver layers separately.
- Monitor DNS resolver availability and configuration provenance.
- Verify gateways and route persistence when provisioning interfaces.
Explanation
Correct Answer
A:Specify multi-homed route preferences and test after interface reconnects. It preserves the corrective behavior established through: Inspect and adjust the relevant route metrics or NetworkManager profile priorities.
Incorrect Answers
B:Document local stub and upstream resolver layers separately. belongs to a situation where 127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers. Here the evidence supports a different requirement: Specify multi-homed route preferences and test after interface reconnects.
C:This belongs to resolver nameserver failure, where The client resolver is sending queries to an unavailable configured DNS server. The current issue instead is: Routing preference can depend on metrics when multiple eligible routes share a destination prefix.
D:That choice responds to a default route necessary for off-subnet traffic failure. In this incident, Routing preference can depend on metrics when multiple eligible routes share a destination prefix.
Question 695
A laptop has Ethernet and Wi-Fi default routes, but traffic leaves over the slower Wi-Fi link. Choose TWO case-specific steps: one that fixes the issue and one that proves the result.
- Parse a compressed IPv6 address and check it round-trips without truncation.
- Record persistent network policy in managed connection profiles, not interactive commands.
- Inspect and adjust the relevant route metrics or NetworkManager profile priorities.
- Use ip route get for a target and verify the selected outgoing interface.
- Change the connection profile to an approved IPv6 auto method and reactivate it under a controlled rollback plan.
Explanation
Correct Answers
C:Inspect and adjust the relevant route metrics or NetworkManager profile priorities. It corrects the mechanism identified in the scenario: Routing preference can depend on metrics when multiple eligible routes share a destination prefix.
D:Use ip route get for a target and verify the selected outgoing interface. This measures the specific result of applying: Inspect and adjust the relevant route metrics or NetworkManager profile priorities.
Incorrect Answers
A:This belongs to ipv6 address length, where IPv6 addresses are 128 bits and use colon-separated hexadecimal presentation with compression rules. The current issue instead is: Routing preference can depend on metrics when multiple eligible routes share a destination prefix.
B:This belongs to persistent static address with networkmanager, where iproute2 changes live interface state; the connection profile governs persistent NetworkManager configuration. The current issue instead is: Routing preference can depend on metrics when multiple eligible routes share a destination prefix.
E:Change the connection profile to an approved IPv6 auto method and reactivate it under a controlled rollback plan. 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 for a target and verify the selected outgoing interface.
Question 696
An application reaches its local gateway but fails only for a remote subnet beyond several routers. Which explanation most directly accounts for the failure in this environment?
- IPv6 addresses are 128 bits and use colon-separated hexadecimal presentation with compression rules.
- The failure is likely beyond the local interface and should be localized by path probes.
- The resolver's search list affects qualification of unqualified hostnames.
- The saved NetworkManager profile may not be set to autoconnect on device availability.
Explanation
Correct Answer
B:The failure is likely beyond the local interface and should be localized by path probes. The observation is consistent with this mechanism; a targeted repair would be: Use traceroute or tracepath and corroborate with routing/firewall evidence for the relevant hops.
Incorrect Answers
A:IPv6 addresses are 128 bits and use colon-separated hexadecimal presentation with compression rules. could help with ipv6 address length; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Compare a working destination and failing destination path without treating each nonreply as a hard failure.
C:It would address separate dns search domains rather than the present problem. The appropriate correction here is: Use traceroute or tracepath and corroborate with routing/firewall evidence for the relevant hops.
D:That choice responds to a autoconnect disabled failure. In this incident, The failure is likely beyond the local interface and should be localized by path probes.
Question 697
An application reaches its local gateway but fails only for a remote subnet beyond several routers. Which configuration approach is appropriate for this requirement?
- Query the suspect server explicitly with dig @server name and compare with an approved reference.
- Use traceroute or tracepath and corroborate with routing/firewall evidence for the relevant hops.
- Allow narrowly scoped polling traffic on UDP 161 to the approved agent.
- Choose TCP when transport-level reliability is required or implement those controls in the UDP application.
Explanation
Correct Answer
B:Use traceroute or tracepath and corroborate with routing/firewall evidence for the relevant hops. The change should be accepted only after this test: Compare a working destination and failing destination path without treating each nonreply as a hard failure.
Incorrect Answers
A:That choice responds to a explicit dns server comparison failure. In this incident, The failure is likely beyond the local interface and should be localized by path probes.
C:SNMP polling commonly targets UDP 161, whereas SNMP traps commonly use UDP 162. That describes a different fault. Here, The failure is likely beyond the local interface and should be localized by path probes.
D:Choose TCP when transport-level reliability is required or implement those controls in the UDP application. 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: Use traceroute or tracepath and corroborate with routing/firewall evidence for the relevant hops.
Question 698
An application reaches its local gateway but fails only for a remote subnet beyond several routers. Which observation should be used for acceptance testing?
- Reapply the profile or reboot and confirm ip addr and nmcli connection show the intended values.
- Compare a working destination and failing destination path without treating each nonreply as a hard failure.
- Compare the candidate address against RFC1918 ranges, including 10/8 and 192.168/16.
- Compare nmcli device status with profile match fields and confirm activation.
Explanation
Correct Answer
B:Compare a working destination and failing destination path without treating each nonreply as a hard failure. This check is tied to the expected behavior rather than mere process uptime.
Incorrect Answers
A:This belongs to persistent static address with networkmanager, where iproute2 changes live interface state; the connection profile governs persistent NetworkManager configuration. The current issue instead is: The failure is likely beyond the local interface and should be localized by path probes.
C:The test for rfc1918 private ipv4 would be: Compare the candidate address against RFC1918 ranges, including 10/8 and 192.168/16. The relevant acceptance check here is: Compare a working destination and failing destination path without treating each nonreply as a hard failure.
D:That choice responds to a wired mac and device association failure. In this incident, The failure is likely beyond the local interface and should be localized by path probes.
Question 699
An application reaches its local gateway but fails only for a remote subnet beyond several routers. Which practice is most useful after the immediate repair succeeds?
- Document local stub and upstream resolver layers separately.
- Manage DNS at its authoritative configuration layer instead of editing generated files.
- Check first and last subnet addresses before IP assignment.
- Use multiple path and endpoint tests because routers may rate-limit probe replies.
Explanation
Correct Answer
D:Use multiple path and endpoint tests because routers may rate-limit probe replies. This control detects or prevents the same mechanism before another incident.
Incorrect Answers
A:It would address systemd-resolved stub target rather than the present problem. The appropriate correction here is: Use traceroute or tracepath and corroborate with routing/firewall evidence for the relevant hops.
B: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: Compare a working destination and failing destination path without treating each nonreply as a hard failure.
C:That choice responds to a ipv4 network boundary failure. In this incident, The failure is likely beyond the local interface and should be localized by path probes.
Question 700
An application reaches its local gateway but fails only for a remote subnet beyond several routers. Choose THREE measures that together correct the failure, demonstrate success and reduce recurrence.
- Reconnect and inspect effective resolver configuration and a known DNS query.
- Use traceroute or tracepath and corroborate with routing/firewall evidence for the relevant hops.
- Use multiple path and endpoint tests because routers may rate-limit probe replies.
- Compare a working destination and failing destination path without treating each nonreply as a hard failure.
- Set the static hostname using hostnamectl or the distribution's supported persistent configuration.
- Provision Wi-Fi security profiles securely rather than embedding plaintext passwords in scripts.
Explanation
Correct Answers
B:Use traceroute or tracepath and corroborate with routing/firewall evidence for the relevant hops. The change should be accepted only after this test: Compare a working destination and failing destination path without treating each nonreply as a hard failure.
C:Use multiple path and endpoint tests because routers may rate-limit probe replies. It prevents repetition of the condition: The failure is likely beyond the local interface and should be localized by path probes.
D:Compare a working destination and failing destination path without treating each nonreply as a hard failure. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: The failure is likely beyond the local interface and should be localized by path probes.
Incorrect Answers
A: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: The failure is likely beyond the local interface and should be localized by path probes.
E:This belongs to host name managed by hostnamectl, where The hostname command can alter runtime state without changing the static hostname policy. The current issue instead is: The failure is likely beyond the local interface and should be localized by path probes.
F:It would address wi-fi network name and authentication rather than the present problem. The appropriate correction here is: Use traceroute or tracepath and corroborate with routing/firewall evidence for the relevant hops.
LPI Level 1 (102-500) Practice Tests