cert
cert-1
cert-2

Pass LPI 102-500 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
102-500 Exam - Verified By Experts
102-500 Premium Bundle
$29.98

102-500 Premium Bundle

$79.99
$109.97
  • Premium File 120 Questions & Answers. Last update: Nov 13, 2026
  • Training Course 126 Video Lectures
  • Study Guide 962 Pages
 
$109.97
$79.99
accept 15 downloads in last 7 days
block-screenshots
Purchase LPI 102-500 Exam Training Products Individually
LPI 102-500 Premium File
Premium File 120 Q&A
$76.99$69.99
LPI 102-500 Video Training Course
Training Course 126 Lectures
$21.99 $19.99
LPI 102-500 PDF Study Guide
Study Guide 962 Pages
$21.99 $19.99
LPI 102-500 Practice Test 46

Question 450

During an LPIC-1 practice lab, the operator encounters this condition: A cloud host is assigned 172.33.5.10 and a team labels it private merely because its first octet is 172. Which TWO complementary steps provide the best corrective action and its most direct diagnostic verification? Select TWO answers.

  1. Identify RFC1918 blocks precisely and plan appropriate routing or address translation for connectivity to public destinations.
  2. Claim every 172.x.x.x address is private and that any RFC1918 host can route directly across the public internet with no translation.
  3. Review hosts lookup precedence in nsswitch.conf and maintain the correct /etc/hosts and resolver settings for each source.
  4. Inspect interface addresses and routing, compare to the exact RFC1918 CIDR ranges, and test external source visibility where permitted.
  5. Inspect `ss -ltnp`, service bind configuration, local and remote connection attempts and firewall rules.

Explanation

Correct Answers

A:

Recommended administrative action: Identify RFC1918 blocks precisely and plan appropriate routing or address translation for connectivity to public destinations. Scenario: A cloud host is assigned 172.33.5.10 and a team labels it private merely because its first octet is 172. Linux principle: RFC1918 private IPv4 ranges are 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16; not every 172.x or 192.x address is private.

D:

Most direct verification evidence: Inspect interface addresses and routing, compare to the exact RFC1918 CIDR ranges, and test external source visibility where permitted. Scenario: A cloud host is assigned 172.33.5.10 and a team labels it private merely because its first octet is 172. Linux principle: RFC1918 private IPv4 ranges are 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16; not every 172.x or 192.x address is private.

Incorrect Answers

B:

This shortcut is unsafe for the present Linux issue: Claim every 172.x.x.x address is private and that any RFC1918 host can route directly across the public internet with no translation. Scenario: A cloud host is assigned 172.33.5.10 and a team labels it private merely because its first octet is 172. RFC1918 private IPv4 ranges are 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16; not every 172.x or 192.x address is private.

C:

That option would review hosts lookup precedence in nsswitch.conf and maintain the correct /etc/hosts and resolver settings for each source, but it addresses a different concern. RFC1918 private IPv4 ranges are 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16; not every 172.x or 192.x address is private.

E:

That option would inspect `ss -ltnp`, service bind configuration, local and remote connection attempts and firewall rules, but it addresses a different concern. RFC1918 private IPv4 ranges are 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16; not every 172.x or 192.x address is private.

Question 451

A helpdesk escalation describes this Linux behavior: A monitoring application sends UDP telemetry but support expects reliable retransmission and ordering from UDP itself. Which administrative step is the MOST appropriate way to resolve this issue? Select ONE best answer.

  1. Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics.
  2. Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable.
  3. Set the intended persistent static hostname with `hostnamectl` or supported distribution settings and validate local host mapping separately.
  4. Review hosts lookup precedence in nsswitch.conf and maintain the correct /etc/hosts and resolver settings for each source.

Explanation

Correct Answer

A:

Recommended administrative action: Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics.

Incorrect Answers

B:

That option would assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable, but it addresses a different concern. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

C:

That option would set the intended persistent static hostname with `hostnamectl` or supported distribution settings and validate local host mapping separately, but it addresses a different concern. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

D:

That option would review hosts lookup precedence in nsswitch.conf and maintain the correct /etc/hosts and resolver settings for each source, but it addresses a different concern. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

Question 452

An operations handoff identifies this problem: A monitoring application sends UDP telemetry but support expects reliable retransmission and ordering from UDP itself. Which Linux behavior or technical principle BEST explains why the issue occurs? Select ONE best answer.

  1. A direct DNS query to a named server tests that server, while application resolution follows local NSS, caching and resolver configuration.
  2. Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable.
  3. Different Linux networking managers apply persistent interface settings through their own configurations; conflicting ownership can cause changes to be ignored or overwritten.
  4. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

Explanation

Correct Answer

D:

Relevant Linux operating principle: TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

Incorrect Answers

A:

This alternative addresses DNS query tools and authoritative versus recursive answers, not the specific issue of TCP versus UDP versus ICMP diagnostics: A direct DNS query to a named server tests that server, while application resolution follows local NSS, caching and resolver configuration. Linux principle: TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability. Appropriate response: Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics. Root-cause evidence: Inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering rules. Independent acceptance: The selected transport matches reliability requirements and diagnostics distinguish blocked ICMP from a reachable TCP service.

B:

That option would assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable, but it addresses a different concern. Independent acceptance: The selected transport matches reliability requirements and diagnostics distinguish blocked ICMP from a reachable TCP service.

C:

This alternative addresses NetworkManager and systemd-networkd configuration ownership, not the specific issue of TCP versus UDP versus ICMP diagnostics: Different Linux networking managers apply persistent interface settings through their own configurations; conflicting ownership can cause changes to be ignored or overwritten. Linux principle: TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability. Appropriate response: Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics. Root-cause evidence: Inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering rules. Independent acceptance: The selected transport matches reliability requirements and diagnostics distinguish blocked ICMP from a reachable TCP service.

Question 453

A team maintaining a Linux host reports: A monitoring application sends UDP telemetry but support expects reliable retransmission and ordering from UDP itself. Which evidence or command result MOST directly tests the suspected root cause? Select ONE best answer.

  1. Compare `dig name`, `dig @server name`, `host name`, `getent ahosts name` and the resolver settings.
  2. Inspect `systemctl` service state, NetworkManager device management, /etc/systemd/network and active connection profiles alongside `ip` state.
  3. Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable.
  4. Inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering rules.

Explanation

Correct Answer

D:

Most direct verification evidence: Inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering rules.

Incorrect Answers

A:

That option would compare `dig name`, `dig @server name`, `host name`, `getent ahosts name` and the resolver settings, but it addresses a different concern. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

B:

This alternative addresses NetworkManager and systemd-networkd configuration ownership, not the specific issue of TCP versus UDP versus ICMP diagnostics: Inspect `systemctl` service state, NetworkManager device management, /etc/systemd/network and active connection profiles alongside `ip` state.

C:

This shortcut is unsafe for the present Linux issue: Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable. It cannot establish a safe correction.

Question 454

While verifying a Linux change request, an engineer finds: A monitoring application sends UDP telemetry but support expects reliable retransmission and ordering from UDP itself. Which observed outcome BEST confirms a successful and properly scoped correction? Select ONE best answer.

  1. The selected transport matches reliability requirements and diagnostics distinguish blocked ICMP from a reachable TCP service.
  2. The host reports the approved name consistently and local resolution returns the correct intended addresses.
  3. The intended profile reconnects after a restart with the correct address, gateway and DNS while unrelated devices remain intact.
  4. Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable.

Explanation

Correct Answer

A:

Observable acceptance criterion: The selected transport matches reliability requirements and diagnostics distinguish blocked ICMP from a reachable TCP service.

Incorrect Answers

B:

This alternative addresses Hostnamectl and durable host identification, not the specific issue of TCP versus UDP versus ICMP diagnostics: The host reports the approved name consistently and local resolution returns the correct intended addresses.

C:

This alternative addresses NetworkManager persistent wired connection profiles, not the specific issue of TCP versus UDP versus ICMP diagnostics: The intended profile reconnects after a restart with the correct address, gateway and DNS while unrelated devices remain intact. Linux principle: TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability. Appropriate response: Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics. Root-cause evidence: Inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering rules. Independent acceptance: The selected transport matches reliability requirements and diagnostics distinguish blocked ICMP from a reachable TCP service.

D:

This shortcut is unsafe for the present Linux issue: Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

Question 455

A Linux administrator investigates the following system incident: A monitoring application sends UDP telemetry but support expects reliable retransmission and ordering from UDP itself. Which misleading assumption MOST directly contributes to this failure and should be rejected? Select ONE best answer.

  1. Attempt DNS repairs for an interface that is administratively DOWN and assume temporary `ip` state cannot be overwritten by NetworkManager.
  2. Use only a transient `ip addr add` command and expect NetworkManager to persist it automatically after every reboot.
  3. Assume any file under /etc/systemd/network will control an interface regardless of which network manager actually owns the device.
  4. Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable.

Explanation

Correct Answer

D:

Reject this specific misconception: Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable. It incorrectly assumes behavior that conflicts with the observed Linux conditions.

Incorrect Answers

A:

This alternative addresses Ip command address and link troubleshooting, not the specific issue of TCP versus UDP versus ICMP diagnostics: Attempt DNS repairs for an interface that is administratively DOWN and assume temporary `ip` state cannot be overwritten by NetworkManager. Linux principle: TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability. Appropriate response: Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics. Root-cause evidence: Inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering rules. Independent acceptance: The selected transport matches reliability requirements and diagnostics distinguish blocked ICMP from a reachable TCP service.

B:

That option would use only a transient `ip addr add` command and expect NetworkManager to persist it automatically after every reboot, but it addresses a different concern. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

C:

That option would assume any file under /etc/systemd/network will control an interface regardless of which network manager actually owns the device, but it addresses a different concern. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

Question 456

On a production Linux workstation or server, a technician observes: An operator blocks all ICMP and then misinterprets the absence of ping replies as proof that HTTPS over TCP must be down. Which administrative step is the MOST appropriate way to resolve this issue? Select ONE best answer.

  1. Use `ip link` and `ip addr` to examine and adjust temporary interface state and repair the persistent manager configuration where required.
  2. Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable.
  3. Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics.
  4. Use dig or host to test chosen DNS servers explicitly and separately verify normal resolver lookup through getent and local client settings.

Explanation

Correct Answer

C:

Recommended administrative action: Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

Incorrect Answers

A:

That option would use `ip link` and `ip addr` to examine and adjust temporary interface state and repair the persistent manager configuration where required, but it addresses a different concern. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

B:

This shortcut is unsafe for the present Linux issue: Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

D:

That option would use dig or host to test chosen DNS servers explicitly and separately verify normal resolver lookup through getent and local client settings, but it addresses a different concern. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

Question 457

During an LPIC-1 practice lab, the operator encounters this condition: An operator blocks all ICMP and then misinterprets the absence of ping replies as proof that HTTPS over TCP must be down. Which Linux behavior or technical principle BEST explains why the issue occurs? Select ONE best answer.

  1. Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable.
  2. Port numbers identify transport endpoints within TCP or UDP; the same numeric port can be used differently across protocols and policy must match actual service bindings.
  3. In IPv4 CIDR the prefix length specifies network bits; the remaining host bits determine subnet boundaries and usable address ranges.
  4. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

Explanation

Correct Answer

D:

Relevant Linux operating principle: TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

Incorrect Answers

A:

This shortcut is unsafe for the present Linux issue: Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable. It cannot establish a safe correction. Linux principle: TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

B:

This alternative addresses Well-known TCP UDP port mapping, not the specific issue of TCP versus UDP versus ICMP diagnostics: Port numbers identify transport endpoints within TCP or UDP; the same numeric port can be used differently across protocols and policy must match actual service bindings. Linux principle: TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability. Appropriate response: Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics. Root-cause evidence: Inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering rules. Independent acceptance: The selected transport matches reliability requirements and diagnostics distinguish blocked ICMP from a reachable TCP service.

C:

This alternative addresses IPv4 CIDR network masks and subnet reachability, not the specific issue of TCP versus UDP versus ICMP diagnostics: In IPv4 CIDR the prefix length specifies network bits; the remaining host bits determine subnet boundaries and usable address ranges. Linux principle: TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability. Appropriate response: Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics. Root-cause evidence: Inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering rules. Independent acceptance: The selected transport matches reliability requirements and diagnostics distinguish blocked ICMP from a reachable TCP service.

Question 458

A helpdesk escalation describes this Linux behavior: An operator blocks all ICMP and then misinterprets the absence of ping replies as proof that HTTPS over TCP must be down. Which evidence or command result MOST directly tests the suspected root cause? Select ONE best answer.

  1. Examine `ip route show`, `ip route get` for a remote address, next-hop reachability and persisted route configuration.
  2. Inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering rules.
  3. Inspect interface addresses and routing, compare to the exact RFC1918 CIDR ranges, and test external source visibility where permitted.
  4. Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable.

Explanation

Correct Answer

B:

Most direct verification evidence: Inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering rules. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

Incorrect Answers

A:

This alternative addresses Linux routing tables and default gateway selection, not the specific issue of TCP versus UDP versus ICMP diagnostics: Examine `ip route show`, `ip route get` for a remote address, next-hop reachability and persisted route configuration. Linux principle: TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability. Appropriate response: Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics. Root-cause evidence: Inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering rules. Independent acceptance: The selected transport matches reliability requirements and diagnostics distinguish blocked ICMP from a reachable TCP service.

C:

That option would inspect interface addresses and routing, compare to the exact RFC1918 CIDR ranges, and test external source visibility where permitted, but it addresses a different concern. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

D:

This shortcut is unsafe for the present Linux issue: Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable. It cannot establish a safe correction. Linux principle: TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability. Appropriate response: Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics. Root-cause evidence: Inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering rules. Independent acceptance: The selected transport matches reliability requirements and diagnostics distinguish blocked ICMP from a reachable TCP service.

Question 459

An operations handoff identifies this problem: An operator blocks all ICMP and then misinterprets the absence of ping replies as proof that HTTPS over TCP must be down. Which observed outcome BEST confirms a successful and properly scoped correction? Select ONE best answer.

  1. The selected transport matches reliability requirements and diagnostics distinguish blocked ICMP from a reachable TCP service.
  2. Host resolution follows the documented local and DNS precedence without stale overrides for the service name.
  3. Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable.
  4. The device associates to the approved wireless network, authenticates successfully and receives the expected network configuration.

Explanation

Correct Answer

A:

Observable acceptance criterion: The selected transport matches reliability requirements and diagnostics distinguish blocked ICMP from a reachable TCP service. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

Incorrect Answers

B:

This alternative addresses Local hosts resolution versus DNS settings, not the specific issue of TCP versus UDP versus ICMP diagnostics: Host resolution follows the documented local and DNS precedence without stale overrides for the service name. Linux principle: TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability. Appropriate response: Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics. Root-cause evidence: Inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering rules. Independent acceptance: The selected transport matches reliability requirements and diagnostics distinguish blocked ICMP from a reachable TCP service.

C:

This shortcut is unsafe for the present Linux issue: Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

D:

This alternative addresses NetworkManager Wi-Fi authentication and saved profiles, not the specific issue of TCP versus UDP versus ICMP diagnostics: The device associates to the approved wireless network, authenticates successfully and receives the expected network configuration. Linux principle: TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability. Appropriate response: Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics. Root-cause evidence: Inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering rules. Independent acceptance: The selected transport matches reliability requirements and diagnostics distinguish blocked ICMP from a reachable TCP service.

Question 460

A team maintaining a Linux host reports: An operator blocks all ICMP and then misinterprets the absence of ping replies as proof that HTTPS over TCP must be down. Which TWO complementary steps provide the best corrective action and its most direct diagnostic verification? Select TWO answers.

  1. Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable.
  2. Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics.
  3. Identify the active network configuration manager and express persistent settings in its supported profiles or .network files without competing managers.
  4. Inspect `ip -6 addr`, `ip -6 route`, router advertisements and a scoped ping6 to the link-local destination.
  5. Inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering rules.

Explanation

Correct Answers

B:

Recommended administrative action: Choose TCP when reliable ordered byte streams are needed, UDP for connectionless datagrams with application-level reliability as required, and ICMP for appropriate network control and diagnostics. Linux principle: TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

E:

Most direct verification evidence: Inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering rules. Linux principle: TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

Incorrect Answers

A:

This shortcut is unsafe for the present Linux issue: Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

C:

That option would identify the active network configuration manager and express persistent settings in its supported profiles or .network files without competing managers, but it addresses a different concern. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

D:

That option would inspect `ip -6 addr`, `ip -6 route`, router advertisements and a scoped ping6 to the link-local destination, but it addresses a different concern. TCP, UDP and ICMP have different roles; UDP does not inherently acknowledge or reorder delivery and ICMP ping behavior does not establish application TCP availability.

LPI Level 1 (102-500) Practice Tests