100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 570
A host can ping a local neighbor but cannot reach a remote network and has no default route. Select THREE measures that follow directly from the root cause and lifecycle risk.
- Use traceroute or tracepath and corroborate with routing/firewall evidence for the relevant hops.
- Install a valid default route via the appropriate on-link gateway, then make it persistent.
- Verify gateways and route persistence when provisioning interfaces.
- Use ip route get for a remote address and test reachability through the gateway.
- Provision Wi-Fi security profiles securely rather than embedding plaintext passwords in scripts.
- Compare short-name and fully qualified getent lookups after reconnect.
Explanation
Correct Answers
B:Install a valid default route via the appropriate on-link gateway, then make it persistent. Unlike a broad workaround, it targets the observed cause: The local connected route does not tell the kernel where to send traffic outside the connected subnet.
C:Verify gateways and route persistence when provisioning interfaces. It preserves the corrective behavior established through: Install a valid default route via the appropriate on-link gateway, then make it persistent.
D:Use ip route get for a remote address and test reachability through the gateway. This check is tied to the expected behavior rather than mere process uptime.
Incorrect Answers
A:That choice responds to a traceroute reveals upstream hop loss failure. In this incident, The local connected route does not tell the kernel where to send traffic outside the connected subnet.
E:Provision Wi-Fi security profiles securely rather than embedding plaintext passwords in scripts. belongs to a situation where SSID selection alone is insufficient when the wireless security and credentials do not match the access point. Here the evidence supports a different requirement: Verify gateways and route persistence when provisioning interfaces.
F:The resolver's search list affects qualification of unqualified hostnames. That describes a different fault. Here, The local connected route does not tell the kernel where to send traffic outside the connected subnet.
Question 571
A firewall allows UDP 53 only and large DNS replies or zone-transfer workflows fail unexpectedly. Why does the reported configuration behave this way?
- Resolver search-domain configuration can qualify a short name differently than the operator expects.
- DNS commonly uses UDP and also uses TCP for responses and operations requiring it.
- The active profile's automatic method permits DHCP to supply network settings.
- NXDOMAIN indicates a negative name response, not by itself a broken physical network connection.
Explanation
Correct Answer
B:DNS commonly uses UDP and also uses TCP for responses and operations requiring it. This is the explanation that justifies the specific remedy: Allow approved TCP 53 traffic in addition to UDP 53 where the DNS deployment requires it.
Incorrect Answers
A:This option assumes Resolver search-domain configuration can qualify a short name differently than the operator expects. The reported symptoms instead call for: Allow approved TCP 53 traffic in addition to UDP 53 where the DNS deployment requires it.
C:The active profile's automatic method permits DHCP to supply network settings. That describes a different fault. Here, DNS commonly uses UDP and also uses TCP for responses and operations requiring it.
D:This option assumes NXDOMAIN indicates a negative name response, not by itself a broken physical network connection. The reported symptoms instead call for: Allow approved TCP 53 traffic in addition to UDP 53 where the DNS deployment requires it.
Question 572
A firewall allows UDP 53 only and large DNS replies or zone-transfer workflows fail unexpectedly. Which remedial step follows from the observed mechanism?
- Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits.
- Activate or reapply the modified connection using an approved nmcli operation with safe remote-access planning.
- Allow approved TCP 53 traffic in addition to UDP 53 where the DNS deployment requires it.
- Assign the intended interface to the correct profile and review autoconnect priority for competing profiles.
Explanation
Correct Answer
C:Allow approved TCP 53 traffic in addition to UDP 53 where the DNS deployment requires it. Unlike a broad workaround, it targets the observed cause: DNS commonly uses UDP and also uses TCP for responses and operations requiring it.
Incorrect Answers
A:The test for resolver nameserver failure would be: Use dig against the configured server and an alternate known-good server to isolate the issue. The relevant acceptance check here is: Test a suitable DNS-over-TCP query separately from a UDP lookup.
B: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: Test a suitable DNS-over-TCP query separately from a UDP lookup.
D:The test for multiple saved profiles for one device would be: List connection profiles and check which UUID becomes active after reboot. The relevant acceptance check here is: Test a suitable DNS-over-TCP query separately from a UDP lookup.
Question 573
A firewall allows UDP 53 only and large DNS replies or zone-transfer workflows fail unexpectedly. Which observation should be used for acceptance testing?
- Reapply the profile or reboot and confirm ip addr and nmcli connection show the intended values.
- Test a suitable DNS-over-TCP query separately from a UDP lookup.
- Reboot a test system and inspect active connections without manual intervention.
- Reconnect and inspect effective resolver configuration and a known DNS query.
Explanation
Correct Answer
B:Test a suitable DNS-over-TCP query separately from a UDP lookup. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
Incorrect Answers
A:iproute2 changes live interface state; the connection profile governs persistent NetworkManager configuration. That describes a different fault. Here, DNS commonly uses UDP and also uses TCP for responses and operations requiring it.
C:The saved NetworkManager profile may not be set to autoconnect on device availability. That describes a different fault. Here, DNS commonly uses UDP and also uses TCP for responses and operations requiring it.
D:Reconnect and inspect effective resolver configuration and a known DNS query. could help with persistent dns in managed connection; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Test a suitable DNS-over-TCP query separately from a UDP lookup.
Question 574
A firewall allows UDP 53 only and large DNS replies or zone-transfer workflows fail unexpectedly. Which practice is most useful after the immediate repair succeeds?
- Use named-server comparisons to distinguish resolver-local faults from zone data.
- Include protocol-specific checks for important service dependencies.
- Model protocol and port combinations rather than assuming one transport for all DNS behavior.
- Document local stub and upstream resolver layers separately.
Explanation
Correct Answer
C:Model protocol and port combinations rather than assuming one transport for all DNS behavior. It prevents repetition of the condition: DNS commonly uses UDP and also uses TCP for responses and operations requiring it.
Incorrect Answers
A:Use named-server comparisons to distinguish resolver-local faults from zone data. belongs to a situation where A configured or caching resolver may differ from authoritative or alternative resolver results. Here the evidence supports a different requirement: Model protocol and port combinations rather than assuming one transport for all DNS behavior.
B:This belongs to network port test without application protocol, where ICMP echo tests do not prove a particular TCP destination port is reachable. The current issue instead is: DNS commonly uses UDP and also uses TCP for responses and operations requiring it.
D:It would address systemd-resolved stub target rather than the present problem. The appropriate correction here is: Allow approved TCP 53 traffic in addition to UDP 53 where the DNS deployment requires it.
Question 575
A firewall allows UDP 53 only and large DNS replies or zone-transfer workflows fail unexpectedly. Choose TWO case-specific steps: one that fixes the issue and one that proves the result.
- Review the saved profile's interface name and MAC match and update it for the authorized adapter.
- Inspect service states and verify the interface configuration is persistent after reboot.
- Audit default routes after VLAN and subnet migrations.
- Test a suitable DNS-over-TCP query separately from a UDP lookup.
- Allow approved TCP 53 traffic in addition to UDP 53 where the DNS deployment requires it.
Explanation
Correct Answers
D:Test a suitable DNS-over-TCP query separately from a UDP lookup. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
E:Allow approved TCP 53 traffic in addition to UDP 53 where the DNS deployment requires it. It corrects the mechanism identified in the scenario: DNS commonly uses UDP and also uses TCP for responses and operations requiring it.
Incorrect Answers
A:That choice responds to a wired mac and device association failure. In this incident, DNS commonly uses UDP and also uses TCP for responses and operations requiring it.
B:Inspect service states and verify the interface configuration is persistent after reboot. belongs to a situation where nmcli controls NetworkManager profiles and cannot manage an unrelated active network stack by itself. Here the evidence supports a different requirement: Test a suitable DNS-over-TCP query separately from a UDP lookup.
C:It would address default route points to wrong gateway rather than the present problem. The appropriate correction here is: Allow approved TCP 53 traffic in addition to UDP 53 where the DNS deployment requires it.
Question 576
A security rule blocks outbound TCP 443 while allowing TCP 80, and browsers can load plain HTTP but fail HTTPS sites. Which mechanism best explains the difference between expectation and result?
- A timeout can indicate drops or path loss; a received refusal indicates an endpoint actively rejected the connection.
- Conventional HTTPS traffic uses TLS over TCP port 443 rather than TCP port 80.
- Application lookup may use NSS with files before DNS, while dig queries DNS directly.
- The client resolver is sending queries to an unavailable configured DNS server.
Explanation
Correct Answer
B:Conventional HTTPS traffic uses TLS over TCP port 443 rather than TCP port 80. That cause connects the stated symptom to the corrective action: Permit policy-approved HTTPS egress on the correct transport and destination ranges.
Incorrect Answers
A:A timeout can indicate drops or path loss; a received refusal indicates an endpoint actively rejected the connection. could help with timeout versus refusal; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Connect to a known HTTPS endpoint and inspect the negotiated TLS session.
C:Application lookup may use NSS with files before DNS, while dig queries DNS directly. could help with nss hosts lookup order; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Connect to a known HTTPS endpoint and inspect the negotiated TLS session.
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: Connect to a known HTTPS endpoint and inspect the negotiated TLS session.
Question 577
A security rule blocks outbound TCP 443 while allowing TCP 80, and browsers can load plain HTTP but fail HTTPS sites. Which change most directly meets the stated requirement?
- Configure the connection with the approved SSID and authentication settings using NetworkManager.
- Set DNS servers and search domains in the appropriate NetworkManager connection profile or resolver manager.
- Assign the intended interface to the correct profile and review autoconnect priority for competing profiles.
- Permit policy-approved HTTPS egress on the correct transport and destination ranges.
Explanation
Correct Answer
D:Permit policy-approved HTTPS egress on the correct transport and destination ranges. It addresses the root cause, while Document service ports with protocol and destination scope in firewall changes. reduces future recurrence.
Incorrect Answers
A: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: Connect to a known HTTPS endpoint and inspect the negotiated TLS session.
B:This option assumes A network manager may regenerate resolver configuration from active connection properties. The reported symptoms instead call for: Permit policy-approved HTTPS egress on the correct transport and destination ranges.
C:Assign the intended interface to the correct profile and review autoconnect priority for competing profiles. belongs to a situation where Profile priority and autoconnect policy can select an unintended saved connection. Here the evidence supports a different requirement: Permit policy-approved HTTPS egress on the correct transport and destination ranges.
Question 578
A security rule blocks outbound TCP 443 while allowing TCP 80, and browsers can load plain HTTP but fail HTTPS sites. What focused test would distinguish a real correction from a cosmetic change?
- Connect to a known HTTPS endpoint and inspect the negotiated TLS session.
- Compare short-name and fully qualified getent lookups after reconnect.
- Query the authoritative/approved DNS source for the exact FQDN and inspect the returned status.
- Use ip route get for a target and verify the selected outgoing interface.
Explanation
Correct Answer
A:Connect to a known HTTPS endpoint and inspect the negotiated TLS session. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
Incorrect Answers
B:That choice responds to a separate dns search domains failure. In this incident, Conventional HTTPS traffic uses TLS over TCP port 443 rather than TCP port 80.
C:It would address dns record absent versus network down rather than the present problem. The appropriate correction here is: Permit policy-approved HTTPS egress on the correct transport and destination ranges.
D:This option assumes Routing preference can depend on metrics when multiple eligible routes share a destination prefix. The reported symptoms instead call for: Permit policy-approved HTTPS egress on the correct transport and destination ranges.
Question 579
A security rule blocks outbound TCP 443 while allowing TCP 80, and browsers can load plain HTTP but fail HTTPS sites. Which repeatable check would reduce recurrence?
- Baseline per-interface error counters and alert on unexpected growth.
- Use multiple path and endpoint tests because routers may rate-limit probe replies.
- Document service ports with protocol and destination scope in firewall changes.
- Include protocol-specific checks for important service dependencies.
Explanation
Correct Answer
C:Document service ports with protocol and destination scope in firewall changes. It preserves the corrective behavior established through: Permit policy-approved HTTPS egress on the correct transport and destination ranges.
Incorrect Answers
A:Physical/link or buffering issues are indicated by interface statistics, not necessarily a DNS fault. That describes a different fault. Here, Conventional HTTPS traffic uses TLS over TCP port 443 rather than TCP port 80.
B:This belongs to traceroute reveals upstream hop loss, where The failure is likely beyond the local interface and should be localized by path probes. The current issue instead is: Conventional HTTPS traffic uses TLS over TCP port 443 rather than TCP port 80.
D:ICMP echo tests do not prove a particular TCP destination port is reachable. That describes a different fault. Here, Conventional HTTPS traffic uses TLS over TCP port 443 rather than TCP port 80.
Question 580
A security rule blocks outbound TCP 443 while allowing TCP 80, and browsers can load plain HTTP but fail HTTPS sites. Which THREE case-specific steps cover immediate repair, test evidence and sustained control?
- Activate or reapply the modified connection using an approved nmcli operation with safe remote-access planning.
- Connect to a known HTTPS endpoint and inspect the negotiated TLS session.
- Permit policy-approved HTTPS egress on the correct transport and destination ranges.
- Separate DNS data correctness from link reachability in help-desk triage.
- Document service ports with protocol and destination scope in firewall changes.
- Use resolvectl query and compare with a direct upstream query to trace the chain.
Explanation
Correct Answers
B:Connect to a known HTTPS endpoint and inspect the negotiated TLS session. The test is evidence-based because the underlying failure was: Conventional HTTPS traffic uses TLS over TCP port 443 rather than TCP port 80.
C:Permit policy-approved HTTPS egress on the correct transport and destination ranges. It addresses the root cause, while Document service ports with protocol and destination scope in firewall changes. reduces future recurrence.
E:Document service ports with protocol and destination scope in firewall changes. The underlying risk is Conventional HTTPS traffic uses TLS over TCP port 443 rather than TCP port 80.
Incorrect Answers
A:This option assumes Changing saved profile properties does not always update the already-active connection state immediately. The reported symptoms instead call for: Permit policy-approved HTTPS egress on the correct transport and destination ranges.
D:That choice responds to a dns record absent versus network down failure. In this incident, Conventional HTTPS traffic uses TLS over TCP port 443 rather than TCP port 80.
F:This option assumes 127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers. The reported symptoms instead call for: Permit policy-approved HTTPS egress on the correct transport and destination ranges.
LPI Level 1 (102-500) Practice Tests