100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 740
A user enters a short hostname and reaches an unintended system because the client appends an old search domain. Select THREE measures that follow directly from the root cause and lifecycle risk.
- Record actual service listener ports before writing transport rules.
- Set the static hostname using hostnamectl or the distribution's supported persistent configuration.
- Avoid relying on ambiguous single-label names across administrative zones.
- Compare lookups for the short name and the explicit FQDN under the same resolver.
- Correct the resolver's search list or use the intended fully qualified name.
- Test the port from both sides of the filtering boundary and compare the result.
Explanation
Correct Answers
C:Avoid relying on ambiguous single-label names across administrative zones. It preserves the corrective behavior established through: Correct the resolver's search list or use the intended fully qualified name.
D:Compare lookups for the short name and the explicit FQDN under the same resolver. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
E:Correct the resolver's search list or use the intended fully qualified name. It addresses the root cause, while Avoid relying on ambiguous single-label names across administrative zones. reduces future recurrence.
Incorrect Answers
A:It would address ssh and mail protocol ports rather than the present problem. The appropriate correction here is: Correct the resolver's search list or use the intended fully qualified name.
B:That choice responds to a host name managed by hostnamectl failure. In this incident, Resolver search-domain configuration can qualify a short name differently than the operator expects.
F:It would address network port test without application protocol rather than the present problem. The appropriate correction here is: Correct the resolver's search list or use the intended fully qualified name.
Question 741
A host has 127.0.0.53 in resolv.conf and an operator assumes that address itself is an external DNS server. Which mechanism best explains the difference between expectation and result?
- Routing preference can depend on metrics when multiple eligible routes share a destination prefix.
- Physical/link or buffering issues are indicated by interface statistics, not necessarily a DNS fault.
- The active profile's automatic method permits DHCP to supply network settings.
- 127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers.
Explanation
Correct Answer
D:127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers. This is the explanation that justifies the specific remedy: Inspect resolvectl status for the real per-link upstream DNS configuration.
Incorrect Answers
A:This belongs to unexpected route metric, where Routing preference can depend on metrics when multiple eligible routes share a destination prefix. The current issue instead is: 127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers.
B:This option assumes Physical/link or buffering issues are indicated by interface statistics, not necessarily a DNS fault. The reported symptoms instead call for: Inspect resolvectl status for the real per-link upstream DNS configuration.
C:The active profile's automatic method permits DHCP to supply network settings. That describes a different fault. Here, 127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers.
Question 742
A host has 127.0.0.53 in resolv.conf and an operator assumes that address itself is an external DNS server. Which configuration approach is appropriate for this requirement?
- Store and parse IPv6 addresses with an IPv6-capable library or iproute2 tool.
- Inspect resolvectl status for the real per-link upstream DNS configuration.
- Set DNS servers and search domains in the appropriate NetworkManager connection profile or resolver manager.
- Install a valid default route via the appropriate on-link gateway, then make it persistent.
Explanation
Correct Answer
B:Inspect resolvectl status for the real per-link upstream DNS configuration. It addresses the root cause, while Document local stub and upstream resolver layers separately. reduces future recurrence.
Incorrect Answers
A:That choice responds to a ipv6 address length failure. In this incident, 127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers.
C: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: Inspect resolvectl status for the real per-link upstream DNS configuration.
D:This belongs to default route necessary for off-subnet traffic, where The local connected route does not tell the kernel where to send traffic outside the connected subnet. The current issue instead is: 127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers.
Question 743
A host has 127.0.0.53 in resolv.conf and an operator assumes that address itself is an external DNS server. Which check would provide the strongest evidence that the fix worked?
- Capture the actual packet source and compare it with the service's allowlist.
- Use ss -ltnp and a local TCP connection test before testing remotely.
- Use resolvectl query and compare with a direct upstream query to trace the chain.
- Check ip addr show dev interface and run an on-link test to confirm reachability.
Explanation
Correct Answer
C:Use resolvectl query and compare with a direct upstream query to trace the chain. The test is evidence-based because the underlying failure was: 127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers.
Incorrect Answers
A:Capture the actual packet source and compare it with the service's allowlist. could help with wrong source address selection; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use resolvectl query and compare with a direct upstream query to trace the chain.
B:This option assumes The application is not listening on the target address and port, independent of basic IP reachability. The reported symptoms instead call for: Inspect resolvectl status for the real per-link upstream DNS configuration.
D:Layer-two link state does not imply that an IPv4 or IPv6 address has been configured. That describes a different fault. Here, 127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers.
Question 744
A host has 127.0.0.53 in resolv.conf and an operator assumes that address itself is an external DNS server. What longer-term control best supports this requirement?
- Include operational link-state checks in incident triage.
- Size subnets from required usable addresses and reserve capacity for growth.
- Test both IPv4 and IPv6 profile persistence in dual-stack provisioning checks.
- Document local stub and upstream resolver layers separately.
Explanation
Correct Answer
D:Document local stub and upstream resolver layers separately. Sustained checks matter because 127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers.
Incorrect Answers
A:This option assumes An administratively down interface cannot pass ordinary traffic until brought up. The reported symptoms instead call for: Inspect resolvectl status for the real per-link upstream DNS configuration.
B:Size subnets from required usable addresses and reserve capacity for growth. could help with ipv4 /27 address plan; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use resolvectl query and compare with a direct upstream query to trace the chain.
C:The saved NetworkManager profile has IPv6 disabled, so router advertisements cannot supply the intended host configuration. That describes a different fault. Here, 127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers.
Question 745
A host has 127.0.0.53 in resolv.conf and an operator assumes that address itself is an external DNS server. Select TWO justified actions that address this particular problem and confirm closure.
- Include protocol-specific checks for important service dependencies.
- Set DNS servers and search domains in the appropriate NetworkManager connection profile or resolver manager.
- Capture the actual packet source and compare it with the service's allowlist.
- Inspect resolvectl status for the real per-link upstream DNS configuration.
- Use resolvectl query and compare with a direct upstream query to trace the chain.
Explanation
Correct Answers
D:Inspect resolvectl status for the real per-link upstream DNS configuration. This is appropriate because 127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers.
E:Use resolvectl query and compare with a direct upstream query to trace the chain. The test is evidence-based because the underlying failure was: 127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers.
Incorrect Answers
A:ICMP echo tests do not prove a particular TCP destination port is reachable. That describes a different fault. Here, 127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers.
B:Set DNS servers and search domains in the appropriate NetworkManager connection profile or resolver manager. could help with persistent dns in managed connection; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use resolvectl query and compare with a direct upstream query to trace the chain.
C:Source address selection and policy routing can choose an unintended outbound identity. That describes a different fault. Here, 127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers.
Question 746
An administrator sees NXDOMAIN for a recently added hostname and starts troubleshooting the workstation's Ethernet cable. Which mechanism best explains the difference between expectation and result?
- NXDOMAIN indicates a negative name response, not by itself a broken physical network connection.
- The local connected route does not tell the kernel where to send traffic outside the connected subnet.
- Physical/link or buffering issues are indicated by interface statistics, not necessarily a DNS fault.
- An IPv4 default route does not substitute for IPv6 routing information.
Explanation
Correct Answer
A:NXDOMAIN indicates a negative name response, not by itself a broken physical network connection. This is the explanation that justifies the specific remedy: Verify the intended DNS zone and record existence before changing interface settings.
Incorrect Answers
B:The local connected route does not tell the kernel where to send traffic outside the connected subnet. could help with default route necessary for off-subnet traffic; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Query the authoritative/approved DNS source for the exact FQDN and inspect the returned status.
C:This option assumes Physical/link or buffering issues are indicated by interface statistics, not necessarily a DNS fault. The reported symptoms instead call for: Verify the intended DNS zone and record existence before changing interface settings.
D:This belongs to ipv6 route omission, where An IPv4 default route does not substitute for IPv6 routing information. The current issue instead is: NXDOMAIN indicates a negative name response, not by itself a broken physical network connection.
Question 747
An administrator sees NXDOMAIN for a recently added hostname and starts troubleshooting the workstation's Ethernet cable. Which configuration approach is appropriate for this requirement?
- Install a valid default route via the appropriate on-link gateway, then make it persistent.
- Verify the intended DNS zone and record existence before changing interface settings.
- Configure the approved SSH destination on TCP 22 or the explicitly overridden service port.
- Enable connection.autoconnect for the correct profile and interface under policy.
Explanation
Correct Answer
B:Verify the intended DNS zone and record existence before changing interface settings. Unlike a broad workaround, it targets the observed cause: NXDOMAIN indicates a negative name response, not by itself a broken physical network connection.
Incorrect Answers
A:This belongs to default route necessary for off-subnet traffic, where The local connected route does not tell the kernel where to send traffic outside the connected subnet. The current issue instead is: NXDOMAIN indicates a negative name response, not by itself a broken physical network connection.
C:Configure the approved SSH destination on TCP 22 or the explicitly overridden service port. could help with ssh and mail protocol ports; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Query the authoritative/approved DNS source for the exact FQDN and inspect the returned status.
D:This belongs to autoconnect disabled, where The saved NetworkManager profile may not be set to autoconnect on device availability. The current issue instead is: NXDOMAIN indicates a negative name response, not by itself a broken physical network connection.
Question 748
An administrator sees NXDOMAIN for a recently added hostname and starts troubleshooting the workstation's Ethernet cable. Which observation should be used for acceptance testing?
- Capture the actual packet source and compare it with the service's allowlist.
- Reconnect and inspect effective resolver configuration and a known DNS query.
- List connection profiles and check which UUID becomes active after reboot.
- Query the authoritative/approved DNS source for the exact FQDN and inspect the returned status.
Explanation
Correct Answer
D:Query the authoritative/approved DNS source for the exact FQDN and inspect the returned status. It verifies that the targeted action (Verify the intended DNS zone and record existence before changing interface settings.) achieved its intended outcome.
Incorrect Answers
A:Source address selection and policy routing can choose an unintended outbound identity. That describes a different fault. Here, NXDOMAIN indicates a negative name response, not by itself a broken physical network connection.
B:A network manager may regenerate resolver configuration from active connection properties. That describes a different fault. Here, NXDOMAIN indicates a negative name response, not by itself a broken physical network connection.
C: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: Query the authoritative/approved DNS source for the exact FQDN and inspect the returned status.
Question 749
An administrator sees NXDOMAIN for a recently added hostname and starts troubleshooting the workstation's Ethernet cable. Which ongoing control would best reduce the chance of the issue returning?
- Document timeout and refusal as distinct evidence types in runbooks.
- Record actual service listener ports before writing transport rules.
- Baseline per-interface error counters and alert on unexpected growth.
- Separate DNS data correctness from link reachability in help-desk triage.
Explanation
Correct Answer
D:Separate DNS data correctness from link reachability in help-desk triage. It makes the outcome of the targeted repair (Verify the intended DNS zone and record existence before changing interface settings.) repeatable.
Incorrect Answers
A:This belongs to timeout versus refusal, where A timeout can indicate drops or path loss; a received refusal indicates an endpoint actively rejected the connection. The current issue instead is: NXDOMAIN indicates a negative name response, not by itself a broken physical network connection.
B:The test for ssh and mail protocol ports would be: Use ss -ltn and an SSH client to verify the server's actual configured listener. The relevant acceptance check here is: Query the authoritative/approved DNS source for the exact FQDN and inspect the returned status.
C:Baseline per-interface error counters and alert on unexpected growth. could help with interface rx errors and drops; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Query the authoritative/approved DNS source for the exact FQDN and inspect the returned status.
Question 750
An administrator sees NXDOMAIN for a recently added hostname and starts troubleshooting the workstation's Ethernet cable. Which THREE case-specific steps cover immediate repair, test evidence and sustained control?
- Separate DNS data correctness from link reachability in help-desk triage.
- Query the authoritative/approved DNS source for the exact FQDN and inspect the returned status.
- Compute the network and broadcast addresses using the mask and confirm the host configuration.
- Avoid hand-written IPv4-only parsing in dual-stack automation.
- Apply the correct dynamic or static address to the proper interface using the authoritative manager.
- Verify the intended DNS zone and record existence before changing interface settings.
Explanation
Correct Answers
A:Separate DNS data correctness from link reachability in help-desk triage. The underlying risk is NXDOMAIN indicates a negative name response, not by itself a broken physical network connection.
B:Query the authoritative/approved DNS source for the exact FQDN and inspect the returned status. The test is evidence-based because the underlying failure was: NXDOMAIN indicates a negative name response, not by itself a broken physical network connection.
F:Verify the intended DNS zone and record existence before changing interface settings. This is appropriate because NXDOMAIN indicates a negative name response, not by itself a broken physical network connection.
Incorrect Answers
C:It would address ipv4 network boundary rather than the present problem. The appropriate correction here is: Verify the intended DNS zone and record existence before changing interface settings.
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: Query the authoritative/approved DNS source for the exact FQDN and inspect the returned status.
E:It would address missing address on live interface rather than the present problem. The appropriate correction here is: Verify the intended DNS zone and record existence before changing interface settings.
LPI Level 1 (102-500) Practice Tests