100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 660
A development host resolves short internal names only when fully qualified because the configured search domain is missing. Choose THREE measures that together correct the failure, demonstrate success and reduce recurrence.
- Compare short-name and fully qualified getent lookups after reconnect.
- Set the approved search domain in the active connection or resolver manager.
- Install a valid default route via the appropriate on-link gateway, then make it persistent.
- Compute the network and broadcast addresses using the mask and confirm the host configuration.
- Document search domains explicitly to avoid ambiguous short-name resolution.
- Use multiple path and endpoint tests because routers may rate-limit probe replies.
Explanation
Correct Answers
A:Compare short-name and fully qualified getent lookups after reconnect. It verifies that the targeted action (Set the approved search domain in the active connection or resolver manager.) achieved its intended outcome.
B:Set the approved search domain in the active connection or resolver manager. Unlike a broad workaround, it targets the observed cause: The resolver's search list affects qualification of unqualified hostnames.
E:Document search domains explicitly to avoid ambiguous short-name resolution. Sustained checks matter because The resolver's search list affects qualification of unqualified hostnames.
Incorrect Answers
C:Install a valid default route via the appropriate on-link gateway, then make it persistent. 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: Set the approved search domain in the active connection or resolver manager.
D:Compute the network and broadcast addresses using the mask and confirm the host configuration. could help with ipv4 network boundary; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Compare short-name and fully qualified getent lookups after reconnect.
F:It would address traceroute reveals upstream hop loss rather than the present problem. The appropriate correction here is: Set the approved search domain in the active connection or resolver manager.
Question 661
A host has a correctly configured IP address but ip link shows its Ethernet interface state DOWN. Which failure condition fits the evidence without assuming an unrelated fault?
- An administratively down interface cannot pass ordinary traffic until brought up.
- 127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers.
- ICMP echo tests basic reachability where permitted and can be filtered independently of an application.
- IPv6 addresses are 128 bits and use colon-separated hexadecimal presentation with compression rules.
Explanation
Correct Answer
A:An administratively down interface cannot pass ordinary traffic until brought up. This is the explanation that justifies the specific remedy: Use ip link set dev interface up after confirming the intended port and policy.
Incorrect Answers
B:That choice responds to a systemd-resolved stub target failure. In this incident, An administratively down interface cannot pass ordinary traffic until brought up.
C:It would address icmp diagnostic role rather than the present problem. The appropriate correction here is: Use ip link set dev interface up after confirming the intended port and policy.
D:IPv6 addresses are 128 bits and use colon-separated hexadecimal presentation with compression rules. That describes a different fault. Here, An administratively down interface cannot pass ordinary traffic until brought up.
Question 662
A host has a correctly configured IP address but ip link shows its Ethernet interface state DOWN. What should the administrator do to correct this behavior?
- Inspect resolvectl status for the real per-link upstream DNS configuration.
- Store and parse IPv6 addresses with an IPv6-capable library or iproute2 tool.
- Use ip link set dev interface up after confirming the intended port and policy.
- Set DNS servers and search domains in the appropriate NetworkManager connection profile or resolver manager.
Explanation
Correct Answer
C:Use ip link set dev interface up after confirming the intended port and policy. It corrects the mechanism identified in the scenario: An administratively down interface cannot pass ordinary traffic until brought up.
Incorrect Answers
A:That choice responds to a systemd-resolved stub target failure. In this incident, An administratively down interface cannot pass ordinary traffic until brought up.
B: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: Inspect ip link state and ping a known on-link neighbor after activation.
D: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: Inspect ip link state and ping a known on-link neighbor after activation.
Question 663
A host has a correctly configured IP address but ip link shows its Ethernet interface state DOWN. How should the administrator verify the required behavior?
- Inspect ip link state and ping a known on-link neighbor after activation.
- Reconnect and inspect effective resolver configuration and a known DNS query.
- List connection profiles and check which UUID becomes active after reboot.
- Compare the candidate address against RFC1918 ranges, including 10/8 and 192.168/16.
Explanation
Correct Answer
A:Inspect ip link state and ping a known on-link neighbor after activation. It verifies that the targeted action (Use ip link set dev interface up after confirming the intended port and policy.) achieved its intended outcome.
Incorrect Answers
B:It would address persistent dns in managed connection rather than the present problem. The appropriate correction here is: Use ip link set dev interface up after confirming the intended port and policy.
C:This option assumes Profile priority and autoconnect policy can select an unintended saved connection. The reported symptoms instead call for: Use ip link set dev interface up after confirming the intended port and policy.
D:This option assumes Only 172.16.0.0 through 172.31.255.255 belongs to the 172.16/12 private range. The reported symptoms instead call for: Use ip link set dev interface up after confirming the intended port and policy.
Question 664
A host has a correctly configured IP address but ip link shows its Ethernet interface state DOWN. What operational safeguard addresses the root cause?
- Include operational link-state checks in incident triage.
- Audit DHCP versus static intent for each deployment role.
- Verify gateways and route persistence when provisioning interfaces.
- Avoid relying on ambiguous single-label names across administrative zones.
Explanation
Correct Answer
A:Include operational link-state checks in incident triage. The underlying risk is An administratively down interface cannot pass ordinary traffic until brought up.
Incorrect Answers
B:Audit DHCP versus static intent for each deployment role. belongs to a situation where The active profile's automatic method permits DHCP to supply network settings. Here the evidence supports a different requirement: Include operational link-state checks in incident triage.
C:This option assumes The local connected route does not tell the kernel where to send traffic outside the connected subnet. The reported symptoms instead call for: Use ip link set dev interface up after confirming the intended port and policy.
D:That choice responds to a search suffix causes misleading name failure. In this incident, An administratively down interface cannot pass ordinary traffic until brought up.
Question 665
A host has a correctly configured IP address but ip link shows its Ethernet interface state DOWN. Which TWO options provide a coherent remediation-and-test response to this incident?
- Document service ports with protocol and destination scope in firewall changes.
- Use ip link set dev interface up after confirming the intended port and policy.
- Verify the intended DNS zone and record existence before changing interface settings.
- Inspect ip link state and ping a known on-link neighbor after activation.
- Use ip route get for a remote address and test reachability through the gateway.
Explanation
Correct Answers
B:Use ip link set dev interface up after confirming the intended port and policy. It is the direct response; verify the result by: Inspect ip link state and ping a known on-link neighbor after activation.
D:Inspect ip link state and ping a known on-link neighbor after activation. This measures the specific result of applying: Use ip link set dev interface up after confirming the intended port and policy.
Incorrect Answers
A:Conventional HTTPS traffic uses TLS over TCP port 443 rather than TCP port 80. That describes a different fault. Here, An administratively down interface cannot pass ordinary traffic until brought up.
C:Verify the intended DNS zone and record existence before changing interface settings. could help with dns record absent versus network down; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Inspect ip link state and ping a known on-link neighbor after activation.
E: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: An administratively down interface cannot pass ordinary traffic until brought up.
Question 666
A Linux guest has carrier and a default route expectation, but ip addr reveals no address on the intended interface. Which explanation most directly accounts for the failure in this environment?
- Layer-two link state does not imply that an IPv4 or IPv6 address has been configured.
- Changing saved profile properties does not always update the already-active connection state immediately.
- DNS commonly uses UDP and also uses TCP for responses and operations requiring it.
- UDP datagrams do not inherently provide TCP's reliable stream, retransmission and ordering guarantees.
Explanation
Correct Answer
A:Layer-two link state does not imply that an IPv4 or IPv6 address has been configured. This is the explanation that justifies the specific remedy: Apply the correct dynamic or static address to the proper interface using the authoritative manager.
Incorrect Answers
B:This option assumes Changing saved profile properties does not always update the already-active connection state immediately. The reported symptoms instead call for: Apply the correct dynamic or static address to the proper interface using the authoritative manager.
C:This belongs to dns usually udp but can use tcp, where DNS commonly uses UDP and also uses TCP for responses and operations requiring it. The current issue instead is: Layer-two link state does not imply that an IPv4 or IPv6 address has been configured.
D:This option assumes UDP datagrams do not inherently provide TCP's reliable stream, retransmission and ordering guarantees. The reported symptoms instead call for: Apply the correct dynamic or static address to the proper interface using the authoritative manager.
Question 667
A Linux guest has carrier and a default route expectation, but ip addr reveals no address on the intended interface. What should the administrator do to correct this behavior?
- Use a valid internal private range or plan routing for a properly assigned public address.
- Inspect resolvectl status for the real per-link upstream DNS configuration.
- Change the connection profile to an approved IPv6 auto method and reactivate it under a controlled rollback plan.
- Apply the correct dynamic or static address to the proper interface using the authoritative manager.
Explanation
Correct Answer
D:Apply the correct dynamic or static address to the proper interface using the authoritative manager. It addresses the root cause, while Test address assignment separately from physical carrier and routing. reduces future recurrence.
Incorrect Answers
A:Use a valid internal private range or plan routing for a properly assigned public address. could help with rfc1918 private ipv4; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Check ip addr show dev interface and run an on-link test to confirm reachability.
B:Inspect resolvectl status for the real per-link upstream DNS configuration. could help with systemd-resolved stub target; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Check ip addr show dev interface and run an on-link test to confirm reachability.
C:The test for ipv6 disabled in a persistent profile would be: Check nmcli connection IPv6 method, ip -6 addr and ip -6 route after a clean reconnect. The relevant acceptance check here is: Check ip addr show dev interface and run an on-link test to confirm reachability.
Question 668
A Linux guest has carrier and a default route expectation, but ip addr reveals no address on the intended interface. How should the administrator verify the required behavior?
- Drop and reorder packets in a test and observe how the application handles missing data.
- Check ip addr show dev interface and run an on-link test to confirm reachability.
- Compare lookups for the short name and the explicit FQDN under the same resolver.
- Reboot and compare hostnamectl status with hostname output.
Explanation
Correct Answer
B:Check ip addr show dev interface and run an on-link test to confirm reachability. The test is evidence-based because the underlying failure was: Layer-two link state does not imply that an IPv4 or IPv6 address has been configured.
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: Apply the correct dynamic or static address to the proper interface using the authoritative manager.
C:Compare lookups for the short name and the explicit FQDN under the same resolver. belongs to a situation where Resolver search-domain configuration can qualify a short name differently than the operator expects. Here the evidence supports a different requirement: Check ip addr show dev interface and run an on-link test to confirm reachability.
D:Reboot and compare hostnamectl status with hostname output. could help with host name managed by hostnamectl; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Check ip addr show dev interface and run an on-link test to confirm reachability.
Question 669
A Linux guest has carrier and a default route expectation, but ip addr reveals no address on the intended interface. What longer-term control best supports this requirement?
- Separate DNS data correctness from link reachability in help-desk triage.
- Avoid hand-written IPv4-only parsing in dual-stack automation.
- Use layered diagnostics rather than interpreting one ICMP result as application health.
- Test address assignment separately from physical carrier and routing.
Explanation
Correct Answer
D:Test address assignment separately from physical carrier and routing. It preserves the corrective behavior established through: Apply the correct dynamic or static address to the proper interface using the authoritative manager.
Incorrect Answers
A:Separate DNS data correctness from link reachability in help-desk triage. belongs to a situation where NXDOMAIN indicates a negative name response, not by itself a broken physical network connection. Here the evidence supports a different requirement: Test address assignment separately from physical carrier and routing.
B:Avoid hand-written IPv4-only parsing in dual-stack automation. could help with ipv6 address length; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Check ip addr show dev interface and run an on-link test to confirm reachability.
C:ICMP echo tests basic reachability where permitted and can be filtered independently of an application. That describes a different fault. Here, Layer-two link state does not imply that an IPv4 or IPv6 address has been configured.
Question 670
A Linux guest has carrier and a default route expectation, but ip addr reveals no address on the intended interface. Choose THREE measures that together correct the failure, demonstrate success and reduce recurrence.
- Allow approved TCP 53 traffic in addition to UDP 53 where the DNS deployment requires it.
- Apply the correct dynamic or static address to the proper interface using the authoritative manager.
- Test address assignment separately from physical carrier and routing.
- Check ip addr show dev interface and run an on-link test to confirm reachability.
- Check ip -6 addr and ping with the correct interface scope to an on-link neighbor.
- Manage DNS at its authoritative configuration layer instead of editing generated files.
Explanation
Correct Answers
B:Apply the correct dynamic or static address to the proper interface using the authoritative manager. Unlike a broad workaround, it targets the observed cause: Layer-two link state does not imply that an IPv4 or IPv6 address has been configured.
C:Test address assignment separately from physical carrier and routing. Sustained checks matter because Layer-two link state does not imply that an IPv4 or IPv6 address has been configured.
D:Check ip addr show dev interface and run an on-link test to confirm reachability. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: Layer-two link state does not imply that an IPv4 or IPv6 address has been configured.
Incorrect Answers
A:This option assumes DNS commonly uses UDP and also uses TCP for responses and operations requiring it. The reported symptoms instead call for: Apply the correct dynamic or static address to the proper interface using the authoritative manager.
E:The test for ipv6 link-local scope would be: Check ip -6 addr and ping with the correct interface scope to an on-link neighbor. The relevant acceptance check here is: Check ip addr show dev interface and run an on-link test to confirm reachability.
F:It would address persistent dns in managed connection rather than the present problem. The appropriate correction here is: Apply the correct dynamic or static address to the proper interface using the authoritative manager.
LPI Level 1 (102-500) Practice Tests