LPI 102-500 Exam Dumps, Practice Test Questions

100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!

LPI 102-500 Premium Bundle
$79.97
$59.98

102-500 Premium Bundle

  • Premium File: 120 Questions & Answers. Last update: Nov 18, 2026
  • Training Course: 126 Video Lectures
  • Study Guide: 962 Pages
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

102-500 Premium Bundle

LPI 102-500 Premium Bundle
  • Premium File: 120 Questions & Answers. Last update: Nov 18, 2026
  • Training Course: 126 Video Lectures
  • Study Guide: 962 Pages
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
$79.97
$59.98

LPI 102-500 Practice Test 74

Question 730

A host's IP connectivity is healthy but every public hostname lookup fails; /etc/resolv.conf points to a retired resolver. Select THREE measures that follow directly from the root cause and lifecycle risk.

  1. Drop and reorder packets in a test and observe how the application handles missing data.
  2. Monitor DNS resolver availability and configuration provenance.
  3. Change the connection profile to an approved IPv6 auto method and reactivate it under a controlled rollback plan.
  4. Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits.
  5. Use dig against the configured server and an alternate known-good server to isolate the issue.
  6. Test both IPv4 and IPv6 profile persistence in dual-stack provisioning checks.

Explanation

Correct Answers

B:

Monitor DNS resolver availability and configuration provenance. It preserves the corrective behavior established through: Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits.

D:

Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits. This is appropriate because The client resolver is sending queries to an unavailable configured DNS server.

E:

Use dig against the configured server and an alternate known-good server to isolate the issue. The test is evidence-based because the underlying failure was: The client resolver is sending queries to an unavailable configured DNS server.

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: Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits.

C:

It would address ipv6 disabled in a persistent profile rather than the present problem. The appropriate correction here is: Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits.

F:

That choice responds to a ipv6 disabled in a persistent profile failure. In this incident, The client resolver is sending queries to an unavailable configured DNS server.

Question 731

Only one branch reports the wrong DNS answer, but administrators test only their default recursive resolver. Why does the reported configuration behave this way?

  1. IPv6 addresses are 128 bits and use colon-separated hexadecimal presentation with compression rules.
  2. The saved NetworkManager profile has IPv6 disabled, so router advertisements cannot supply the intended host configuration.
  3. Layer-two link state does not imply that an IPv4 or IPv6 address has been configured.
  4. A configured or caching resolver may differ from authoritative or alternative resolver results.

Explanation

Correct Answer

D:

A configured or caching resolver may differ from authoritative or alternative resolver results. The administrator should distinguish this from unrelated symptoms by checking: Check query results and TTLs from each resolver before deciding whether caching or source data differs.

Incorrect Answers

A:

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: Check query results and TTLs from each resolver before deciding whether caching or source data differs.

B:

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 query results and TTLs from each resolver before deciding whether caching or source data differs.

C:

The test for missing address on live interface would be: Check ip addr show dev interface and run an on-link test to confirm reachability. The relevant acceptance check here is: Check query results and TTLs from each resolver before deciding whether caching or source data differs.

Question 732

Only one branch reports the wrong DNS answer, but administrators test only their default recursive resolver. Which change most directly meets the stated requirement?

  1. Configure the connection with the approved SSID and authentication settings using NetworkManager.
  2. Change the connection profile to an approved IPv6 auto method and reactivate it under a controlled rollback plan.
  3. Configure the approved SSH destination on TCP 22 or the explicitly overridden service port.
  4. Query the suspect server explicitly with dig @server name and compare with an approved reference.

Explanation

Correct Answer

D:

Query the suspect server explicitly with dig @server name and compare with an approved reference. This is appropriate because A configured or caching resolver may differ from authoritative or alternative resolver results.

Incorrect Answers

A:

Configure the connection with the approved SSID and authentication settings using NetworkManager. could help with wi-fi network name and authentication; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Check query results and TTLs from each resolver before deciding whether caching or source data differs.

B:

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 query results and TTLs from each resolver before deciding whether caching or source data differs.

C:

That choice responds to a ssh and mail protocol ports failure. In this incident, A configured or caching resolver may differ from authoritative or alternative resolver results.

Question 733

Only one branch reports the wrong DNS answer, but administrators test only their default recursive resolver. What diagnostic result would demonstrate the target behavior?

  1. Compare short-name and fully qualified getent lookups after reconnect.
  2. Reapply the profile or reboot and confirm ip addr and nmcli connection show the intended values.
  3. Check query results and TTLs from each resolver before deciding whether caching or source data differs.
  4. Use ip -6 route get and ping -6 to a known reachable IPv6 endpoint.

Explanation

Correct Answer

C:

Check query results and TTLs from each resolver before deciding whether caching or source data differs. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: A configured or caching resolver may differ from authoritative or alternative resolver results.

Incorrect Answers

A:

Compare short-name and fully qualified getent lookups after reconnect. belongs to a situation where The resolver's search list affects qualification of unqualified hostnames. Here the evidence supports a different requirement: Check query results and TTLs from each resolver before deciding whether caching or source data differs.

B:

That choice responds to a persistent static address with networkmanager failure. In this incident, A configured or caching resolver may differ from authoritative or alternative resolver results.

D:

This belongs to ipv6 route omission, where An IPv4 default route does not substitute for IPv6 routing information. The current issue instead is: A configured or caching resolver may differ from authoritative or alternative resolver results.

Question 734

Only one branch reports the wrong DNS answer, but administrators test only their default recursive resolver. What operational safeguard addresses the root cause?

  1. Verify gateways and route persistence when provisioning interfaces.
  2. Use named-server comparisons to distinguish resolver-local faults from zone data.
  3. Maintain an authoritative private-address plan and avoid blanket assumptions from the first octet.
  4. Review interface identity constraints during hardware replacement.

Explanation

Correct Answer

B:

Use named-server comparisons to distinguish resolver-local faults from zone data. Sustained checks matter because A configured or caching resolver may differ from authoritative or alternative resolver results.

Incorrect Answers

A:

The test for default route necessary for off-subnet traffic would be: Use ip route get for a remote address and test reachability through the gateway. The relevant acceptance check here is: Check query results and TTLs from each resolver before deciding whether caching or source data differs.

C:

Maintain an authoritative private-address plan and avoid blanket assumptions from the first octet. could help with rfc1918 private ipv4; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Check query results and TTLs from each resolver before deciding whether caching or source data differs.

D:

That choice responds to a wired mac and device association failure. In this incident, A configured or caching resolver may differ from authoritative or alternative resolver results.

Question 735

Only one branch reports the wrong DNS answer, but administrators test only their default recursive resolver. Select TWO justified actions that address this particular problem and confirm closure.

  1. Set the approved search domain in the active connection or resolver manager.
  2. Check query results and TTLs from each resolver before deciding whether caching or source data differs.
  3. Query the suspect server explicitly with dig @server name and compare with an approved reference.
  4. Test the port from both sides of the filtering boundary and compare the result.
  5. Baseline per-interface error counters and alert on unexpected growth.

Explanation

Correct Answers

B:

Check query results and TTLs from each resolver before deciding whether caching or source data differs. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.

C:

Query the suspect server explicitly with dig @server name and compare with an approved reference. It corrects the mechanism identified in the scenario: A configured or caching resolver may differ from authoritative or alternative resolver results.

Incorrect Answers

A:

This belongs to separate dns search domains, where The resolver's search list affects qualification of unqualified hostnames. The current issue instead is: A configured or caching resolver may differ from authoritative or alternative resolver results.

D:

Test the port from both sides of the filtering boundary and compare the result. belongs to a situation where ICMP echo tests do not prove a particular TCP destination port is reachable. Here the evidence supports a different requirement: Check query results and TTLs from each resolver before deciding whether caching or source data differs.

E:

That choice responds to a interface rx errors and drops failure. In this incident, A configured or caching resolver may differ from authoritative or alternative resolver results.

Question 736

A user enters a short hostname and reaches an unintended system because the client appends an old search domain. What underlying Linux behavior should the administrator identify first?

  1. Profile priority and autoconnect policy can select an unintended saved connection.
  2. Resolver search-domain configuration can qualify a short name differently than the operator expects.
  3. The local connected route does not tell the kernel where to send traffic outside the connected subnet.
  4. Profile matching constraints can prevent a saved connection from applying to the intended new interface.

Explanation

Correct Answer

B:

Resolver search-domain configuration can qualify a short name differently than the operator expects. The observation is consistent with this mechanism; a targeted repair would be: Correct the resolver's search list or use the intended fully qualified name.

Incorrect Answers

A:

Profile priority and autoconnect policy can select an unintended saved connection. That describes a different fault. Here, Resolver search-domain configuration can qualify a short name differently than the operator expects.

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: Correct the resolver's search list or use the intended fully qualified name.

D:

It would address wired mac and device association rather than the present problem. The appropriate correction here is: Correct the resolver's search list or use the intended fully qualified name.

Question 737

A user enters a short hostname and reaches an unintended system because the client appends an old search domain. What should the administrator do to correct this behavior?

  1. Store and parse IPv6 addresses with an IPv6-capable library or iproute2 tool.
  2. Correct the resolver's search list or use the intended fully qualified name.
  3. Allocate at least a /27 network, which ordinarily provides 30 usable host addresses.
  4. Configure or obtain a valid IPv6 default route from the network's authorized router.

Explanation

Correct Answer

B:

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:

IPv6 addresses are 128 bits and use colon-separated hexadecimal presentation with compression rules. That describes a different fault. Here, Resolver search-domain configuration can qualify a short name differently than the operator expects.

C:

That choice responds to a ipv4 /27 address plan failure. In this incident, Resolver search-domain configuration can qualify a short name differently than the operator expects.

D:

This belongs to ipv6 route omission, where An IPv4 default route does not substitute for IPv6 routing information. The current issue instead is: Resolver search-domain configuration can qualify a short name differently than the operator expects.

Question 738

A user enters a short hostname and reaches an unintended system because the client appends an old search domain. What focused test would distinguish a real correction from a cosmetic change?

  1. Capture the actual packet source and compare it with the service's allowlist.
  2. Compare a working destination and failing destination path without treating each nonreply as a hard failure.
  3. List connection profiles and check which UUID becomes active after reboot.
  4. Compare lookups for the short name and the explicit FQDN under the same resolver.

Explanation

Correct Answer

D:

Compare lookups for the short name and the explicit FQDN under the same resolver. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: Resolver search-domain configuration can qualify a short name differently than the operator expects.

Incorrect Answers

A:

Source address selection and policy routing can choose an unintended outbound identity. That describes a different fault. Here, Resolver search-domain configuration can qualify a short name differently than the operator expects.

B:

It would address traceroute reveals upstream hop loss rather than the present problem. The appropriate correction here is: Correct the resolver's search list or use the intended fully qualified name.

C:

This belongs to multiple saved profiles for one device, where Profile priority and autoconnect policy can select an unintended saved connection. The current issue instead is: Resolver search-domain configuration can qualify a short name differently than the operator expects.

Question 739

A user enters a short hostname and reaches an unintended system because the client appends an old search domain. What operational safeguard addresses the root cause?

  1. Maintain an authoritative private-address plan and avoid blanket assumptions from the first octet.
  2. Use layered diagnostics rather than interpreting one ICMP result as application health.
  3. Specify multi-homed route preferences and test after interface reconnects.
  4. Avoid relying on ambiguous single-label names across administrative zones.

Explanation

Correct Answer

D:

Avoid relying on ambiguous single-label names across administrative zones. Sustained checks matter because Resolver search-domain configuration can qualify a short name differently than the operator expects.

Incorrect Answers

A:

Only 172.16.0.0 through 172.31.255.255 belongs to the 172.16/12 private range. That describes a different fault. Here, Resolver search-domain configuration can qualify a short name differently than the operator expects.

B:

It would address icmp diagnostic role rather than the present problem. The appropriate correction here is: Correct the resolver's search list or use the intended fully qualified name.

C:

That choice responds to a unexpected route metric failure. In this incident, Resolver search-domain configuration can qualify a short name differently than the operator expects.

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.

  1. Record actual service listener ports before writing transport rules.
  2. Set the static hostname using hostnamectl or the distribution's supported persistent configuration.
  3. Avoid relying on ambiguous single-label names across administrative zones.
  4. Compare lookups for the short name and the explicit FQDN under the same resolver.
  5. Correct the resolver's search list or use the intended fully qualified name.
  6. 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.

LPI Level 1 (102-500) Practice Tests

UP

SPECIAL OFFER: GET 10% OFF

This is ONE TIME OFFER

ExamSnap Discount Offer
Enter Your Email Address to Receive Your 10% Off Discount Code

A confirmation link will be sent to this email address to verify your login. *We value your privacy. We will not rent or sell your email address.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your e-mail address below to get started with our interactive software demo of your free trial.

Free Demo Limits: In the demo version you will be able to access only first 5 questions from exam.