100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 710
A file-transfer server's throughput falls while ip -s link shows rapidly growing RX error and dropped-packet counters. Which THREE case-specific steps cover immediate repair, test evidence and sustained control?
- Compare counter deltas under load and after replacing a suspected link component.
- Investigate cable, optics, NIC, duplex and receive queue behavior based on the actual counter pattern.
- Check nmcli connection IPv6 method, ip -6 addr and ip -6 route after a clean reconnect.
- Use nmcli connection modify to set the profile's IPv4 address, method and gateway, then activate it.
- Baseline per-interface error counters and alert on unexpected growth.
- Track local hostname overrides that supersede DNS in incident playbooks.
Explanation
Correct Answers
A:Compare counter deltas under load and after replacing a suspected link component. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
B:Investigate cable, optics, NIC, duplex and receive queue behavior based on the actual counter pattern. It addresses the root cause, while Baseline per-interface error counters and alert on unexpected growth. reduces future recurrence.
E:Baseline per-interface error counters and alert on unexpected growth. The underlying risk is Physical/link or buffering issues are indicated by interface statistics, not necessarily a DNS fault.
Incorrect Answers
C: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: Physical/link or buffering issues are indicated by interface statistics, not necessarily a DNS fault.
D:iproute2 changes live interface state; the connection profile governs persistent NetworkManager configuration. That describes a different fault. Here, Physical/link or buffering issues are indicated by interface statistics, not necessarily a DNS fault.
F:Track local hostname overrides that supersede DNS in incident playbooks. could help with nss hosts lookup order; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Compare counter deltas under load and after replacing a suspected link component.
Question 711
A technician can ping a mail server but cannot tell whether its TCP SMTP listener is reachable through an intermediate firewall. Which mechanism best explains the difference between expectation and result?
- NXDOMAIN indicates a negative name response, not by itself a broken physical network connection.
- A network manager may regenerate resolver configuration from active connection properties.
- 127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers.
- ICMP echo tests do not prove a particular TCP destination port is reachable.
Explanation
Correct Answer
D:ICMP echo tests do not prove a particular TCP destination port is reachable. The administrator should distinguish this from unrelated symptoms by checking: Test the port from both sides of the filtering boundary and compare the result.
Incorrect Answers
A:This option assumes NXDOMAIN indicates a negative name response, not by itself a broken physical network connection. The reported symptoms instead call for: Use netcat or an equivalent TCP connection check against the approved hostname and port.
B:It would address persistent dns in managed connection rather than the present problem. The appropriate correction here is: Use netcat or an equivalent TCP connection check against the approved hostname and port.
C:The test for systemd-resolved stub target would be: Use resolvectl query and compare with a direct upstream query to trace the chain. The relevant acceptance check here is: Test the port from both sides of the filtering boundary and compare the result.
Question 712
A technician can ping a mail server but cannot tell whether its TCP SMTP listener is reachable through an intermediate firewall. Which remedial step follows from the observed mechanism?
- Install a valid default route via the appropriate on-link gateway, then make it persistent.
- Use netcat or an equivalent TCP connection check against the approved hostname and port.
- Query the suspect server explicitly with dig @server name and compare with an approved reference.
- Allow narrowly scoped polling traffic on UDP 161 to the approved agent.
Explanation
Correct Answer
B:Use netcat or an equivalent TCP connection check against the approved hostname and port. It is the direct response; verify the result by: Test the port from both sides of the filtering boundary and compare the result.
Incorrect Answers
A:The local connected route does not tell the kernel where to send traffic outside the connected subnet. That describes a different fault. Here, ICMP echo tests do not prove a particular TCP destination port is reachable.
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: Test the port from both sides of the filtering boundary and compare the result.
D:Allow narrowly scoped polling traffic on UDP 161 to the approved agent. could help with snmp manager polling; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Test the port from both sides of the filtering boundary and compare the result.
Question 713
A technician can ping a mail server but cannot tell whether its TCP SMTP listener is reachable through an intermediate firewall. Which test would confirm the suspected Linux mechanism?
- Test the port from both sides of the filtering boundary and compare the result.
- Compare nmcli device status with profile match fields and confirm activation.
- Drop and reorder packets in a test and observe how the application handles missing data.
- Compare getent hosts and dig for the name and identify the selected source.
Explanation
Correct Answer
A:Test the port from both sides of the filtering boundary and compare the result. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: ICMP echo tests do not prove a particular TCP destination port is reachable.
Incorrect Answers
B:It would address wired mac and device association rather than the present problem. The appropriate correction here is: Use netcat or an equivalent TCP connection check against the approved hostname and port.
C:This belongs to tcp versus udp application fit, where UDP datagrams do not inherently provide TCP's reliable stream, retransmission and ordering guarantees. The current issue instead is: ICMP echo tests do not prove a particular TCP destination port is reachable.
D:Application lookup may use NSS with files before DNS, while dig queries DNS directly. That describes a different fault. Here, ICMP echo tests do not prove a particular TCP destination port is reachable.
Question 714
A technician can ping a mail server but cannot tell whether its TCP SMTP listener is reachable through an intermediate firewall. Which repeatable check would reduce recurrence?
- Model protocol and port combinations rather than assuming one transport for all DNS behavior.
- Audit DHCP versus static intent for each deployment role.
- Verify gateways and route persistence when provisioning interfaces.
- Include protocol-specific checks for important service dependencies.
Explanation
Correct Answer
D:Include protocol-specific checks for important service dependencies. The underlying risk is ICMP echo tests do not prove a particular TCP destination port is reachable.
Incorrect Answers
A:The test for dns usually udp but can use tcp would be: Test a suitable DNS-over-TCP query separately from a UDP lookup. The relevant acceptance check here is: Test the port from both sides of the filtering boundary and compare the result.
B:This option assumes The active profile's automatic method permits DHCP to supply network settings. The reported symptoms instead call for: Use netcat or an equivalent TCP connection check against the approved hostname and port.
C:Verify gateways and route persistence when provisioning interfaces. belongs to a situation where The local connected route does not tell the kernel where to send traffic outside the connected subnet. Here the evidence supports a different requirement: Include protocol-specific checks for important service dependencies.
Question 715
A technician can ping a mail server but cannot tell whether its TCP SMTP listener is reachable through an intermediate firewall. Choose TWO case-specific steps: one that fixes the issue and one that proves the result.
- Use a valid internal private range or plan routing for a properly assigned public address.
- Choose one authoritative network-management stack per interface.
- Use dig against the configured server and an alternate known-good server to isolate the issue.
- Test the port from both sides of the filtering boundary and compare the result.
- Use netcat or an equivalent TCP connection check against the approved hostname and port.
Explanation
Correct Answers
D:Test the port from both sides of the filtering boundary and compare the result. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
E:Use netcat or an equivalent TCP connection check against the approved hostname and port. It is the direct response; verify the result by: Test the port from both sides of the filtering boundary and compare the result.
Incorrect Answers
A:That choice responds to a rfc1918 private ipv4 failure. In this incident, ICMP echo tests do not prove a particular TCP destination port is reachable.
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: Test the port from both sides of the filtering boundary and compare the result.
C: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 the port from both sides of the filtering boundary and compare the result.
Question 716
A multi-address host reaches a remote service only when the source address is specified manually. What underlying Linux behavior should the administrator identify first?
- A configured or caching resolver may differ from authoritative or alternative resolver results.
- A network manager may regenerate resolver configuration from active connection properties.
- Profile priority and autoconnect policy can select an unintended saved connection.
- Source address selection and policy routing can choose an unintended outbound identity.
Explanation
Correct Answer
D:Source address selection and policy routing can choose an unintended outbound identity. That cause connects the stated symptom to the corrective action: Inspect ip route get with source and interface context, then adjust source policy or route configuration safely.
Incorrect Answers
A:A configured or caching resolver may differ from authoritative or alternative resolver results. 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: Source address selection and policy routing can choose an unintended outbound identity.
B:That choice responds to a persistent dns in managed connection failure. In this incident, Source address selection and policy routing can choose an unintended outbound identity.
C:Profile priority and autoconnect policy can select an unintended saved connection. could help with multiple saved profiles for one device; 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 717
A multi-address host reaches a remote service only when the source address is specified manually. Which change most directly meets the stated requirement?
- Activate or reapply the modified connection using an approved nmcli operation with safe remote-access planning.
- Use nmcli connection modify to set the profile's IPv4 address, method and gateway, then activate it.
- Inspect ip route get with source and interface context, then adjust source policy or route configuration safely.
- Choose TCP when transport-level reliability is required or implement those controls in the UDP application.
Explanation
Correct Answer
C:Inspect ip route get with source and interface context, then adjust source policy or route configuration safely. It is the direct response; verify the result by: Capture the actual packet source and compare it with the service's allowlist.
Incorrect Answers
A:The test for bring up modified networkmanager profile would be: Inspect nmcli device show and ip addr after the profile is applied. The relevant acceptance check here is: Capture the actual packet source and compare it with the service's allowlist.
B:iproute2 changes live interface state; the connection profile governs persistent NetworkManager configuration. That describes a different fault. Here, Source address selection and policy routing can choose an unintended outbound identity.
D:This belongs to tcp versus udp application fit, where UDP datagrams do not inherently provide TCP's reliable stream, retransmission and ordering guarantees. The current issue instead is: Source address selection and policy routing can choose an unintended outbound identity.
Question 718
A multi-address host reaches a remote service only when the source address is specified manually. What diagnostic result would demonstrate the target behavior?
- Capture the actual packet source and compare it with the service's allowlist.
- Verify agent polling and trap delivery separately under the final firewall policy.
- Use dig against the configured server and an alternate known-good server to isolate the issue.
- Reboot and compare hostnamectl status with hostname output.
Explanation
Correct Answer
A: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:Verify agent polling and trap delivery separately under the final firewall policy. belongs to a situation where SNMP polling commonly targets UDP 161, whereas SNMP traps commonly use UDP 162. Here the evidence supports a different requirement: Capture the actual packet source and compare it with the service's allowlist.
C: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: Capture the actual packet source and compare it with the service's allowlist.
D:The hostname command can alter runtime state without changing the static hostname policy. That describes a different fault. Here, Source address selection and policy routing can choose an unintended outbound identity.
Question 719
A multi-address host reaches a remote service only when the source address is specified manually. What longer-term control best supports this requirement?
- Check first and last subnet addresses before IP assignment.
- Audit DHCP versus static intent for each deployment role.
- Maintain stable host identities through declarative provisioning.
- Record intended source identities for multi-homed application traffic.
Explanation
Correct Answer
D:Record intended source identities for multi-homed application traffic. Sustained checks matter because Source address selection and policy routing can choose an unintended outbound identity.
Incorrect Answers
A:For 192.0.2.0/26, address .63 is the broadcast address, not a usable host address. That describes a different fault. Here, Source address selection and policy routing can choose an unintended outbound identity.
B:That choice responds to a static ipv4 method versus dhcp failure. In this incident, Source address selection and policy routing can choose an unintended outbound identity.
C:The test for host name managed by hostnamectl would be: Reboot and compare hostnamectl status with hostname output. The relevant acceptance check here is: Capture the actual packet source and compare it with the service's allowlist.
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.
LPI Level 1 (102-500) Practice Tests