LPI 102-500 Practice Test 59 - Prepaway
Practice Exams:

Pass LPI 102-500 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium Bundle
$29.98
$79.99 $109.97

102-500 Premium Bundle


  • Premium File 120 Questions & Answers. Last update: Nov 13, 2026
  • Training Course 126 Lectures
  • Study Guide 962 Pages

LPI 102-500 Practice Test 59

Question 580

At fictional Clearwater Logistics, the Linux network operations team is working while investigating an observed production-like support incident. The Linux scenario is: A network test tries to reach an fe80 IPv6 address from a different routed subnet and times out. The decisive evidence is: The destination address is link-local and lacks a usable local interface scope in the command. Which paired action and independent proof BEST satisfies the requirement?

  1. For Clearwater Logistics, the Linux support team should: Scoped correction: Activate the correct approved profile and disable or prioritize conflicting profiles appropriately. Independent acceptance: The interface reports the intended address on reconnect and an authorized service remains reachable.
  2. For Clearwater Logistics, the Linux support team should: Scoped correction: Use a protocol-appropriate health check and inspect expected ICMP policy before changing firewall rules. Independent acceptance: Health monitoring identifies service availability accurately while disallowed ICMP remains filtered.
  3. For Clearwater Logistics, the Linux support team should: Scoped correction: Add the intended route to the correct persistent NetworkManager connection profile and activate safely. Independent acceptance: After a controlled reboot the route remains and traffic follows the approved next hop.
  4. For Clearwater Logistics, the Linux support team should: Scoped correction: Use a valid reachable scoped link-local address for a same-link test or an appropriate global/ULA address for routed reachability. Independent acceptance: The same-link scoped ping succeeds and the routed test uses a valid routable IPv6 destination.

Explanation

Correct Answer

D:

The same-link scoped ping succeeds and the routed test uses a valid routable IPv6 destination. Without that result, the finding the destination address is link-local and lacks a usable local interface scope in the command would remain unresolved.

Incorrect Answers

A:

A test that scoped correction: Activate the correct approved profile and disable or prioritize conflicting profiles appropriately. Independent acceptance: The interface reports the intended address on reconnect and an authorized service remains reachable would not demonstrate closure of this condition. The needed proof is the same-link scoped ping succeeds and the routed test uses a valid routable IPv6 destination.

B:

Scoped correction: Use a protocol-appropriate health check and inspect expected ICMP policy before changing firewall rules. Independent acceptance: Health monitoring identifies service availability accurately while disallowed ICMP remains filtered. That does not demonstrate the case-specific success condition: the same-link scoped ping succeeds and the routed test uses a valid routable IPv6 destination. IPv6 link-local addresses are only valid on a local link and require scope when ambiguous.

C:

Scoped correction: Add the intended route to the correct persistent NetworkManager connection profile and activate safely. Independent acceptance: After a controlled reboot the route remains and traffic follows the approved next hop. That result does not test the original problem, identified by the destination address is link-local and lacks a usable local interface scope in the command. Recovery must show that the same-link scoped ping succeeds and the routed test uses a valid routable IPv6 destination.

Question 581

At fictional Lakeshore Analytics, the Linux network operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: Two servers on an intended /24 subnet cannot communicate directly because one interface was configured as /16. The diagnostic evidence is: ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. Which bounded step BEST resolves the described problem?

  1. For Lakeshore Analytics, the Linux support team should: Apply the approved CIDR prefix consistently and verify routing for nonlocal addresses.
  2. For Lakeshore Analytics, the Linux support team should: Select one intended network configuration manager for that interface and remove the conflicting configuration.
  3. For Lakeshore Analytics, the Linux support team should: Coordinate an approved supported interface or tunnel MTU and validate path MTU discovery behavior.
  4. For Lakeshore Analytics, the Linux support team should: Correct the approved NetworkManager profile preferences and authentication settings without storing secrets in plain text.

Explanation

Correct Answer

A:

The case reveals ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. That matters because a network prefix controls local neighbor determination and route selection. The corrective step is to apply the approved CIDR prefix consistently and verify routing for nonlocal addresses. Preserve this constraint during the change: Do not widen the subnet to bypass routing or security segmentation requirements.

Incorrect Answers

B:

Another possible response is to select one intended network configuration manager for that interface and remove the conflicting configuration. The case evidence instead shows that ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. A network prefix controls local neighbor determination and route selection.

C:

Coordinate an approved supported interface or tunnel MTU and validate path MTU discovery behavior. This does not address the reported incident: two servers on an intended /24 subnet cannot communicate directly because one interface was configured as /16. Ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. The case-specific correction is to apply the approved CIDR prefix consistently and verify routing for nonlocal addresses.

D:

One alternative would be to correct the approved NetworkManager profile preferences and authentication settings without storing secrets in plain text. The observed evidence instead shows that ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. The more relevant correction is to apply the approved CIDR prefix consistently and verify routing for nonlocal addresses.

Question 582

At fictional Lakeshore Analytics, the Linux network operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: Two servers on an intended /24 subnet cannot communicate directly because one interface was configured as /16. Which observation MOST directly supports the underlying diagnosis before any changes are made?

  1. The deciding Linux diagnostic evidence for Lakeshore Analytics is: Service state and configuration files show overlapping ownership of the interface.
  2. The deciding Linux diagnostic evidence for Lakeshore Analytics is: ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers.
  3. The deciding Linux diagnostic evidence for Lakeshore Analytics is: ip link and path tests reveal inconsistent MTU along the intended network path.
  4. The deciding Linux diagnostic evidence for Lakeshore Analytics is: nmcli connection priorities and saved SSIDs show an auto-connect guest profile preferred over the managed one.

Explanation

Correct Answer

B:

Ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. It identifies the problem behind two servers on an intended /24 subnet cannot communicate directly because one interface was configured as /16. A network prefix controls local neighbor determination and route selection.

Incorrect Answers

A:

A competing Linux diagnostic finding for Lakeshore Analytics is: Service state and configuration files show overlapping ownership of the interface. It does not account for the observation ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers in the reported situation.

C:

At Lakeshore Analytics, another diagnostic finding is: ip link and path tests reveal inconsistent MTU along the intended network path. This would indicate another failure; here ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. A network prefix controls local neighbor determination and route selection.

D:

At Lakeshore Analytics, a different observation is: nmcli connection priorities and saved SSIDs show an auto-connect guest profile preferred over the managed one. It concerns another dependency. This incident is distinguished by ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. A network prefix controls local neighbor determination and route selection.

Question 583

At fictional Lakeshore Analytics, the Linux network operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: Two servers on an intended /24 subnet cannot communicate directly because one interface was configured as /16. The proposed intervention is: Apply the approved CIDR prefix consistently and verify routing for nonlocal addresses. Which independent result BEST demonstrates a successful correction?

  1. The independent acceptance evidence for Lakeshore Analytics is: After two controlled reboots the interface keeps one consistent address, route and DNS configuration.
  2. The independent acceptance evidence for Lakeshore Analytics is: Large authorized transfers succeed repeatedly without fragmentation-related errors.
  3. The independent acceptance evidence for Lakeshore Analytics is: Hosts on the intended subnet communicate directly and external destinations use the gateway.
  4. The independent acceptance evidence for Lakeshore Analytics is: After a reconnect, the laptop selects the managed secured network and does not automatically join the guest network.

Explanation

Correct Answer

C:

Success requires hosts on the intended subnet communicate directly and external destinations use the gateway. That result tests the previously observed condition: ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. A network prefix controls local neighbor determination and route selection.

Incorrect Answers

A:

At Lakeshore Analytics, another acceptance finding might be: After two controlled reboots the interface keeps one consistent address, route and DNS configuration. That would still leave the reported failure unproven. An acceptance test must show that hosts on the intended subnet communicate directly and external destinations use the gateway.

B:

At Lakeshore Analytics, a different acceptance result would be: Large authorized transfers succeed repeatedly without fragmentation-related errors. It may validate a separate setting, but not the required action: apply the approved CIDR prefix consistently and verify routing for nonlocal addresses. The required observation is hosts on the intended subnet communicate directly and external destinations use the gateway.

D:

The independent acceptance evidence for Lakeshore Analytics is: After a reconnect, the laptop selects the managed secured network and does not automatically join the guest network. The evidence relevant to this incident is ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. Confirm the corresponding recovery result: Hosts on the intended subnet communicate directly and external destinations use the gateway.

Question 584

At fictional Lakeshore Analytics, the Linux network operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: Two servers on an intended /24 subnet cannot communicate directly because one interface was configured as /16. The relevant evidence is: ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. Which Linux administration principle MOST accurately explains the correct response?

  1. The relevant Linux system principle for Lakeshore Analytics is: Persistent network configuration needs a clear owning daemon per interface.
  2. The relevant Linux system principle for Lakeshore Analytics is: Path MTU constraints affect packet delivery independently of basic interface link state.
  3. The relevant Linux system principle for Lakeshore Analytics is: NetworkManager stored connection profiles determine persistent wireless connection behavior.
  4. The relevant Linux system principle for Lakeshore Analytics is: A network prefix controls local neighbor determination and route selection.

Explanation

Correct Answer

D:

The governing distinction is that a network prefix controls local neighbor determination and route selection. Here, ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. Apply the approved CIDR prefix consistently and verify routing for nonlocal addresses.

Incorrect Answers

A:

A competing Linux principle for Lakeshore Analytics is: Persistent network configuration needs a clear owning daemon per interface. The decisive observation, ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers, requires a different explanation: A network prefix controls local neighbor determination and route selection.

B:

A different principle is: the relevant Linux system principle for Lakeshore Analytics is: Path MTU constraints affect packet delivery independently of basic interface link state. The causal link actually supported by ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers is a network prefix controls local neighbor determination and route selection.

C:

A competing Linux principle for Lakeshore Analytics is: NetworkManager stored connection profiles determine persistent wireless connection behavior. However, it does not explain ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. The applicable principle is that a network prefix controls local neighbor determination and route selection.

Question 585

At fictional Lakeshore Analytics, the Linux network operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: Two servers on an intended /24 subnet cannot communicate directly because one interface was configured as /16. The decisive evidence is: ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. Which paired action and independent proof BEST satisfies the requirement?

  1. For Lakeshore Analytics, the Linux support team should: Scoped correction: Apply the approved CIDR prefix consistently and verify routing for nonlocal addresses. Independent acceptance: Hosts on the intended subnet communicate directly and external destinations use the gateway.
  2. For Lakeshore Analytics, the Linux support team should: Scoped correction: Select one intended network configuration manager for that interface and remove the conflicting configuration. Independent acceptance: After two controlled reboots the interface keeps one consistent address, route and DNS configuration.
  3. For Lakeshore Analytics, the Linux support team should: Scoped correction: Coordinate an approved supported interface or tunnel MTU and validate path MTU discovery behavior. Independent acceptance: Large authorized transfers succeed repeatedly without fragmentation-related errors.
  4. For Lakeshore Analytics, the Linux support team should: Scoped correction: Correct the approved NetworkManager profile preferences and authentication settings without storing secrets in plain text. Independent acceptance: After a reconnect, the laptop selects the managed secured network and does not automatically join the guest network.

Explanation

Correct Answer

A:

Verify the change by checking that hosts on the intended subnet communicate directly and external destinations use the gateway. The original clue was ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. The test is meaningful because a network prefix controls local neighbor determination and route selection.

Incorrect Answers

B:

Even verifying scoped correction: Select one intended network configuration manager for that interface and remove the conflicting configuration. Independent acceptance: After two controlled reboots the interface keeps one consistent address, route and DNS configuration leaves the reported failure unproven. An acceptance test must show that hosts on the intended subnet communicate directly and external destinations use the gateway.

C:

The alternative outcome is scoped correction: Coordinate an approved supported interface or tunnel MTU and validate path MTU discovery behavior. Independent acceptance: Large authorized transfers succeed repeatedly without fragmentation-related errors. It may validate a separate setting, but not the required action: apply the approved CIDR prefix consistently and verify routing for nonlocal addresses. The required observation is hosts on the intended subnet communicate directly and external destinations use the gateway.

D:

Scoped correction: Correct the approved NetworkManager profile preferences and authentication settings without storing secrets in plain text. Independent acceptance: After a reconnect, the laptop selects the managed secured network and does not automatically join the guest network. The evidence relevant to this incident is ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. Confirm the corresponding recovery result: Hosts on the intended subnet communicate directly and external destinations use the gateway.

Question 586

At fictional Redridge Insurance, the Linux network operations team is working while investigating an observed production-like support incident. The Linux scenario is: Two servers on an intended /24 subnet cannot communicate directly because one interface was configured as /16. The diagnostic evidence is: ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. Which bounded step BEST resolves the described problem?

  1. For Redridge Insurance, the Linux support team should: Select one intended network configuration manager for that interface and remove the conflicting configuration.
  2. For Redridge Insurance, the Linux support team should: Apply the approved CIDR prefix consistently and verify routing for nonlocal addresses.
  3. For Redridge Insurance, the Linux support team should: Coordinate an approved supported interface or tunnel MTU and validate path MTU discovery behavior.
  4. For Redridge Insurance, the Linux support team should: Correct the approved NetworkManager profile preferences and authentication settings without storing secrets in plain text.

Explanation

Correct Answer

B:

Ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. Instead of unrelated changes, apply the approved CIDR prefix consistently and verify routing for nonlocal addresses. The expected result is hosts on the intended subnet communicate directly and external destinations use the gateway. Preserve this constraint during the change: Do not widen the subnet to bypass routing or security segmentation requirements.

Incorrect Answers

A:

Select one intended network configuration manager for that interface and remove the conflicting configuration. It could be useful for another problem, but it does not change ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. The response needs to apply the approved CIDR prefix consistently and verify routing for nonlocal addresses.

C:

An alternative action is coordinate an approved supported interface or tunnel MTU and validate path MTU discovery behavior. This incident instead involves ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. Confirm the scoped change through hosts on the intended subnet communicate directly and external destinations use the gateway.

D:

Correct the approved NetworkManager profile preferences and authentication settings without storing secrets in plain text. That would not correct the reported ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. The supported response is to apply the approved CIDR prefix consistently and verify routing for nonlocal addresses.

Question 587

At fictional Redridge Insurance, the Linux network operations team is working while investigating an observed production-like support incident. The Linux scenario is: Two servers on an intended /24 subnet cannot communicate directly because one interface was configured as /16. Which observation MOST directly supports the underlying diagnosis before any changes are made?

  1. The deciding Linux diagnostic evidence for Redridge Insurance is: Service state and configuration files show overlapping ownership of the interface.
  2. The deciding Linux diagnostic evidence for Redridge Insurance is: ip link and path tests reveal inconsistent MTU along the intended network path.
  3. The deciding Linux diagnostic evidence for Redridge Insurance is: ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers.
  4. The deciding Linux diagnostic evidence for Redridge Insurance is: nmcli connection priorities and saved SSIDs show an auto-connect guest profile preferred over the managed one.

Explanation

Correct Answer

C:

Look for the recorded condition: Ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. That is decisive because a network prefix controls local neighbor determination and route selection. Correction should target apply the approved CIDR prefix consistently and verify routing for nonlocal addresses.

Incorrect Answers

A:

A competing Linux diagnostic finding for Redridge Insurance is: Service state and configuration files show overlapping ownership of the interface. That finding does not isolate the reported issue: two servers on an intended /24 subnet cannot communicate directly because one interface was configured as /16. The determining evidence is ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers.

B:

At Redridge Insurance, that alternative suggests: ip link and path tests reveal inconsistent MTU along the intended network path. The actual diagnostic record shows ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers instead. The difference matters because a network prefix controls local neighbor determination and route selection.

D:

At Redridge Insurance, another potential finding is: nmcli connection priorities and saved SSIDs show an auto-connect guest profile preferred over the managed one. That would not establish the cause here. Ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. The case-specific correction is to apply the approved CIDR prefix consistently and verify routing for nonlocal addresses.

Question 588

At fictional Redridge Insurance, the Linux network operations team is working while investigating an observed production-like support incident. The Linux scenario is: Two servers on an intended /24 subnet cannot communicate directly because one interface was configured as /16. The proposed intervention is: Apply the approved CIDR prefix consistently and verify routing for nonlocal addresses. Which independent result BEST demonstrates a successful correction?

  1. The independent acceptance evidence for Redridge Insurance is: After two controlled reboots the interface keeps one consistent address, route and DNS configuration.
  2. The independent acceptance evidence for Redridge Insurance is: Large authorized transfers succeed repeatedly without fragmentation-related errors.
  3. The independent acceptance evidence for Redridge Insurance is: After a reconnect, the laptop selects the managed secured network and does not automatically join the guest network.
  4. The independent acceptance evidence for Redridge Insurance is: Hosts on the intended subnet communicate directly and external destinations use the gateway.

Explanation

Correct Answer

D:

To close the incident, demonstrate that hosts on the intended subnet communicate directly and external destinations use the gateway. That addresses ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers and reflects the rule that a network prefix controls local neighbor determination and route selection.

Incorrect Answers

A:

A separate test at Redridge Insurance could show: After two controlled reboots the interface keeps one consistent address, route and DNS configuration. That would not demonstrate closure of this condition. The needed proof is hosts on the intended subnet communicate directly and external destinations use the gateway.

B:

The independent acceptance evidence for Redridge Insurance is: Large authorized transfers succeed repeatedly without fragmentation-related errors. That does not demonstrate the case-specific success condition: hosts on the intended subnet communicate directly and external destinations use the gateway. A network prefix controls local neighbor determination and route selection.

C:

The independent acceptance evidence for Redridge Insurance is: After a reconnect, the laptop selects the managed secured network and does not automatically join the guest network. That result does not test the original problem, identified by ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. Recovery must show that hosts on the intended subnet communicate directly and external destinations use the gateway.

Question 589

At fictional Redridge Insurance, the Linux network operations team is working while investigating an observed production-like support incident. The Linux scenario is: Two servers on an intended /24 subnet cannot communicate directly because one interface was configured as /16. The relevant evidence is: ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. Which Linux administration principle MOST accurately explains the correct response?

  1. The relevant Linux system principle for Redridge Insurance is: A network prefix controls local neighbor determination and route selection.
  2. The relevant Linux system principle for Redridge Insurance is: Persistent network configuration needs a clear owning daemon per interface.
  3. The relevant Linux system principle for Redridge Insurance is: Path MTU constraints affect packet delivery independently of basic interface link state.
  4. The relevant Linux system principle for Redridge Insurance is: NetworkManager stored connection profiles determine persistent wireless connection behavior.

Explanation

Correct Answer

A:

A network prefix controls local neighbor determination and route selection. That explains the observed condition: ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. The scoped response is to apply the approved CIDR prefix consistently and verify routing for nonlocal addresses.

Incorrect Answers

B:

At Redridge Insurance, another Linux system principle is: Persistent network configuration needs a clear owning daemon per interface. The present evidence is ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers, which instead follows from a network prefix controls local neighbor determination and route selection.

C:

A competing Linux principle for Redridge Insurance is: Path MTU constraints affect packet delivery independently of basic interface link state. This describes another relationship, not the cause of two servers on an intended /24 subnet cannot communicate directly because one interface was configured as /16. A network prefix controls local neighbor determination and route selection.

D:

At Redridge Insurance, a different Linux system principle is: NetworkManager stored connection profiles determine persistent wireless connection behavior does not account for ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. This case is governed by a network prefix controls local neighbor determination and route selection.

Question 590

At fictional Redridge Insurance, the Linux network operations team is working while investigating an observed production-like support incident. The Linux scenario is: Two servers on an intended /24 subnet cannot communicate directly because one interface was configured as /16. The decisive evidence is: ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. Which paired action and independent proof BEST satisfies the requirement?

  1. For Redridge Insurance, the Linux support team should: Scoped correction: Select one intended network configuration manager for that interface and remove the conflicting configuration. Independent acceptance: After two controlled reboots the interface keeps one consistent address, route and DNS configuration.
  2. For Redridge Insurance, the Linux support team should: Scoped correction: Apply the approved CIDR prefix consistently and verify routing for nonlocal addresses. Independent acceptance: Hosts on the intended subnet communicate directly and external destinations use the gateway.
  3. For Redridge Insurance, the Linux support team should: Scoped correction: Coordinate an approved supported interface or tunnel MTU and validate path MTU discovery behavior. Independent acceptance: Large authorized transfers succeed repeatedly without fragmentation-related errors.
  4. For Redridge Insurance, the Linux support team should: Scoped correction: Correct the approved NetworkManager profile preferences and authentication settings without storing secrets in plain text. Independent acceptance: After a reconnect, the laptop selects the managed secured network and does not automatically join the guest network.

Explanation

Correct Answer

B:

Hosts on the intended subnet communicate directly and external destinations use the gateway. This measures whether the response corrected ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers rather than merely completing a configuration step.

Incorrect Answers

A:

A test that scoped correction: Select one intended network configuration manager for that interface and remove the conflicting configuration. Independent acceptance: After two controlled reboots the interface keeps one consistent address, route and DNS configuration would not demonstrate closure of this condition. The needed proof is hosts on the intended subnet communicate directly and external destinations use the gateway.

C:

Scoped correction: Coordinate an approved supported interface or tunnel MTU and validate path MTU discovery behavior. Independent acceptance: Large authorized transfers succeed repeatedly without fragmentation-related errors. That does not demonstrate the case-specific success condition: hosts on the intended subnet communicate directly and external destinations use the gateway. A network prefix controls local neighbor determination and route selection.

D:

Scoped correction: Correct the approved NetworkManager profile preferences and authentication settings without storing secrets in plain text. Independent acceptance: After a reconnect, the laptop selects the managed secured network and does not automatically join the guest network. That result does not test the original problem, identified by ip addr shows mismatched prefix lengths, and ARP or neighbor requests are issued for out-of-subnet peers. Recovery must show that hosts on the intended subnet communicate directly and external destinations use the gateway.

LPI Level 1 (102-500) Practice Tests