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 45

Question 440

While verifying a Linux change request, an engineer finds: A network installer configures 10.12.8.70/27 but assumes the first 27 bits designate 27 usable hosts rather than a network prefix. Which TWO complementary steps provide the best corrective action and its most direct diagnostic verification? Select TWO answers.

  1. Check `ip -4 addr`, compute bitwise network address and broadcast boundary, and inspect `ip route get` for representative peers.
  2. Inspect `hostnamectl status`, /etc/hostname, /etc/hosts and `getent hosts` output before and after reboot.
  3. Map required common services to their correct transport and port, including SSH 22/TCP, HTTP 80/TCP, HTTPS 443/TCP and DNS 53/UDP or TCP where used.
  4. Assume /26 means the first 26 hosts belong to one network and that all addresses with the same first three dotted-quad octets are local.
  5. Calculate network and host ranges from the prefix length and configure correct address, subnet prefix and route or gateway for remote destinations.

Explanation

Correct Answers

A:

Most direct verification evidence: Check `ip -4 addr`, compute bitwise network address and broadcast boundary, and inspect `ip route get` for representative peers. 12.8.70/27 but assumes the first 27 bits designate 27 usable hosts rather than a network prefix. Linux principle: In IPv4 CIDR the prefix length specifies network bits; the remaining host bits determine subnet boundaries and usable address ranges.

E:

Recommended administrative action: Calculate network and host ranges from the prefix length and configure correct address, subnet prefix and route or gateway for remote destinations. 12.8.70/27 but assumes the first 27 bits designate 27 usable hosts rather than a network prefix. Linux principle: In IPv4 CIDR the prefix length specifies network bits; the remaining host bits determine subnet boundaries and usable address ranges.

Incorrect Answers

B:

This alternative addresses Hostnamectl and durable host identification, not the specific issue of IPv4 CIDR network masks and subnet reachability: Inspect `hostnamectl status`, /etc/hostname, /etc/hosts and `getent hosts` output before and after reboot. 12.8.70/27 but assumes the first 27 bits designate 27 usable hosts rather than a network prefix. Linux principle: In IPv4 CIDR the prefix length specifies network bits; the remaining host bits determine subnet boundaries and usable address ranges.

C:

That option would map required common services to their correct transport and port, including SSH 22/TCP, HTTP 80/TCP, HTTPS 443/TCP and DNS 53/UDP or TCP where used, but it addresses a different concern. In IPv4 CIDR the prefix length specifies network bits; the remaining host bits determine subnet boundaries and usable address ranges.

D:

This shortcut is unsafe for the present Linux issue: Assume /26 means the first 26 hosts belong to one network and that all addresses with the same first three dotted-quad octets are local. 12.8.70/27 but assumes the first 27 bits designate 27 usable hosts rather than a network prefix. In IPv4 CIDR the prefix length specifies network bits; the remaining host bits determine subnet boundaries and usable address ranges.

Question 441

A Linux administrator investigates the following system incident: An application server uses 10.20.5.4 and an engineer calls it a globally routable public internet endpoint without NAT. Which administrative step is the MOST appropriate way to resolve this issue? Select ONE best answer.

  1. Claim every 172.x.x.x address is private and that any RFC1918 host can route directly across the public internet with no translation.
  2. Map required common services to their correct transport and port, including SSH 22/TCP, HTTP 80/TCP, HTTPS 443/TCP and DNS 53/UDP or TCP where used.
  3. Identify RFC1918 blocks precisely and plan appropriate routing or address translation for connectivity to public destinations.
  4. Use `nmcli connection` to edit the correct NetworkManager profile's IPv4 method, addresses, gateway and activation settings, then reapply deliberately.

Explanation

Correct Answer

C:

Recommended administrative action: Identify RFC1918 blocks precisely and plan appropriate routing or address translation for connectivity to public destinations. Scenario: An application server uses 10.20.5.4 and an engineer calls it a globally routable public internet endpoint without NAT.

Incorrect Answers

A:

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. It cannot establish a safe correction. Scenario: An application server uses 10.20.5.4 and an engineer calls it a globally routable public internet endpoint without NAT. 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. Appropriate response: Identify RFC1918 blocks precisely and plan appropriate routing or address translation for connectivity to public destinations. Root-cause evidence: Inspect interface addresses and routing, compare to the exact RFC1918 CIDR ranges, and test external source visibility where permitted. Independent acceptance: Hosts are classified as private or globally addressed correctly and required outbound communication uses approved routing or NAT.

B:

That option would map required common services to their correct transport and port, including SSH 22/TCP, HTTP 80/TCP, HTTPS 443/TCP and DNS 53/UDP or TCP where used, 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.

D:

That option would use `nmcli connection` to edit the correct NetworkManager profile's IPv4 method, addresses, gateway and activation settings, then reapply deliberately, 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 442

On a production Linux workstation or server, a technician observes: An application server uses 10.20.5.4 and an engineer calls it a globally routable public internet endpoint without NAT. Which Linux behavior or technical principle BEST explains why the issue occurs? Select ONE best answer.

  1. A running process does not prove it is listening on the expected socket or interface; TCP and UDP socket state and bind address matter.
  2. 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.
  3. In IPv4 CIDR the prefix length specifies network bits; the remaining host bits determine subnet boundaries and usable address ranges.
  4. Claim every 172.x.x.x address is private and that any RFC1918 host can route directly across the public internet with no translation.

Explanation

Correct Answer

B:

Relevant Linux operating 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. Scenario: An application server uses 10.20.5.4 and an engineer calls it a globally routable public internet endpoint without NAT.

Incorrect Answers

A:

This alternative addresses Listening sockets with ss and netcat testing, not the specific issue of RFC1918 private addressing and internet routing: A running process does not prove it is listening on the expected socket or interface; TCP and UDP socket state and bind address matter. Scenario: An application server uses 10.20.5.4 and an engineer calls it a globally routable public internet endpoint without NAT. 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. Appropriate response: Identify RFC1918 blocks precisely and plan appropriate routing or address translation for connectivity to public destinations. Root-cause evidence: Inspect interface addresses and routing, compare to the exact RFC1918 CIDR ranges, and test external source visibility where permitted. Independent acceptance: Hosts are classified as private or globally addressed correctly and required outbound communication uses approved routing or NAT.

C:

This alternative addresses IPv4 CIDR network masks and subnet reachability, not the specific issue of RFC1918 private addressing and internet routing: In IPv4 CIDR the prefix length specifies network bits; the remaining host bits determine subnet boundaries and usable address ranges. Scenario: An application server uses 10.20.5.4 and an engineer calls it a globally routable public internet endpoint without NAT. 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. Appropriate response: Identify RFC1918 blocks precisely and plan appropriate routing or address translation for connectivity to public destinations. Root-cause evidence: Inspect interface addresses and routing, compare to the exact RFC1918 CIDR ranges, and test external source visibility where permitted. Independent acceptance: Hosts are classified as private or globally addressed correctly and required outbound communication uses approved routing or NAT.

D:

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. 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 443

During an LPIC-1 practice lab, the operator encounters this condition: An application server uses 10.20.5.4 and an engineer calls it a globally routable public internet endpoint without NAT. Which evidence or command result MOST directly tests the suspected root cause? Select ONE best answer.

  1. Inspect `ip -br link`, `ip address show`, carrier state and manager logs before and after a controlled interface activation.
  2. Inspect available SSIDs, connection authentication settings, device state, connection activation logs and effective routes.
  3. Claim every 172.x.x.x address is private and that any RFC1918 host can route directly across the public internet with no translation.
  4. Inspect interface addresses and routing, compare to the exact RFC1918 CIDR ranges, and test external source visibility where permitted.

Explanation

Correct Answer

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: An application server uses 10.20.5.4 and an engineer calls it a globally routable public internet endpoint without NAT.

Incorrect Answers

A:

That option would inspect `ip -br link`, `ip address show`, carrier state and manager logs before and after a controlled interface activation, 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.

B:

This alternative addresses NetworkManager Wi-Fi authentication and saved profiles, not the specific issue of RFC1918 private addressing and internet routing: Inspect available SSIDs, connection authentication settings, device state, connection activation logs and effective routes.

C:

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. 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. Scenario: An application server uses 10.20.5.4 and an engineer calls it a globally routable public internet endpoint without NAT.

Question 444

A helpdesk escalation describes this Linux behavior: An application server uses 10.20.5.4 and an engineer calls it a globally routable public internet endpoint without NAT. Which observed outcome BEST confirms a successful and properly scoped correction? Select ONE best answer.

  1. Hosts are classified as private or globally addressed correctly and required outbound communication uses approved routing or NAT.
  2. Host resolution follows the documented local and DNS precedence without stale overrides for the service name.
  3. Claim every 172.x.x.x address is private and that any RFC1918 host can route directly across the public internet with no translation.
  4. The intended link is administratively up with the expected address and persistent configuration remains stable after service restart.

Explanation

Correct Answer

A:

Observable acceptance criterion: Hosts are classified as private or globally addressed correctly and required outbound communication uses approved routing or NAT. Scenario: An application server uses 10.20.5.4 and an engineer calls it a globally routable public internet endpoint without NAT.

Incorrect Answers

B:

This alternative addresses Local hosts resolution versus DNS settings, not the specific issue of RFC1918 private addressing and internet routing: Host resolution follows the documented local and DNS precedence without stale overrides for the service name. Scenario: An application server uses 10.20.5.4 and an engineer calls it a globally routable public internet endpoint without NAT. 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. Appropriate response: Identify RFC1918 blocks precisely and plan appropriate routing or address translation for connectivity to public destinations. Root-cause evidence: Inspect interface addresses and routing, compare to the exact RFC1918 CIDR ranges, and test external source visibility where permitted. Independent acceptance: Hosts are classified as private or globally addressed correctly and required outbound communication uses approved routing or NAT.

C:

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. It cannot establish a safe correction. Scenario: An application server uses 10.20.5.4 and an engineer calls it a globally routable public internet endpoint without NAT. 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:

This alternative addresses Ip command address and link troubleshooting, not the specific issue of RFC1918 private addressing and internet routing: The intended link is administratively up with the expected address and persistent configuration remains stable after service restart. Scenario: An application server uses 10.20.5.4 and an engineer calls it a globally routable public internet endpoint without NAT. 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. Appropriate response: Identify RFC1918 blocks precisely and plan appropriate routing or address translation for connectivity to public destinations. Root-cause evidence: Inspect interface addresses and routing, compare to the exact RFC1918 CIDR ranges, and test external source visibility where permitted. Independent acceptance: Hosts are classified as private or globally addressed correctly and required outbound communication uses approved routing or NAT.

Question 445

An operations handoff identifies this problem: An application server uses 10.20.5.4 and an engineer calls it a globally routable public internet endpoint without NAT. Which misleading assumption MOST directly contributes to this failure and should be rejected? Select ONE best answer.

  1. Assume /26 means the first 26 hosts belong to one network and that all addresses with the same first three dotted-quad octets are local.
  2. Assume an active systemd service implies TCP listener availability on every interface and omit direct socket inspection.
  3. Attempt DNS repairs for an interface that is administratively DOWN and assume temporary `ip` state cannot be overwritten by NetworkManager.
  4. Claim every 172.x.x.x address is private and that any RFC1918 host can route directly across the public internet with no translation.

Explanation

Correct Answer

D:

Reject this specific misconception: Claim every 172.x.x.x address is private and that any RFC1918 host can route directly across the public internet with no translation. It incorrectly assumes behavior that conflicts with the observed Linux conditions.

Incorrect Answers

A:

That option would assume /26 means the first 26 hosts belong to one network and that all addresses with the same first three dotted-quad octets are local, 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.

B:

That option would assume an active systemd service implies TCP listener availability on every interface and omit direct socket inspection, 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.

C:

This alternative addresses Ip command address and link troubleshooting, not the specific issue of RFC1918 private addressing and internet routing: Attempt DNS repairs for an interface that is administratively DOWN and assume temporary `ip` state cannot be overwritten by NetworkManager. Scenario: An application server uses 10.20.5.4 and an engineer calls it a globally routable public internet endpoint without NAT. 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. Appropriate response: Identify RFC1918 blocks precisely and plan appropriate routing or address translation for connectivity to public destinations. Root-cause evidence: Inspect interface addresses and routing, compare to the exact RFC1918 CIDR ranges, and test external source visibility where permitted. Independent acceptance: Hosts are classified as private or globally addressed correctly and required outbound communication uses approved routing or NAT.

Question 446

A team maintaining a Linux host reports: A cloud host is assigned 172.33.5.10 and a team labels it private merely because its first octet is 172. Which administrative step is the MOST appropriate way to resolve this issue? Select ONE best answer.

  1. Map required common services to their correct transport and port, including SSH 22/TCP, HTTP 80/TCP, HTTPS 443/TCP and DNS 53/UDP or TCP where used.
  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. Identify RFC1918 blocks precisely and plan appropriate routing or address translation for connectivity to public destinations.
  4. Use `ss -ltn` or related appropriate flags to inspect listening endpoints and netcat or another client to test real transport reachability.

Explanation

Correct Answer

C:

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.

Incorrect Answers

A:

This alternative addresses Well-known TCP UDP port mapping, not the specific issue of RFC1918 private addressing and internet routing: Map required common services to their correct transport and port, including SSH 22/TCP, HTTP 80/TCP, HTTPS 443/TCP and DNS 53/UDP or TCP where used. Scenario: A cloud host is assigned 172.33.5.10 and a team labels it private merely because its first octet is 172.

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. It cannot establish a safe correction. 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. Appropriate response: Identify RFC1918 blocks precisely and plan appropriate routing or address translation for connectivity to public destinations. Root-cause evidence: Inspect interface addresses and routing, compare to the exact RFC1918 CIDR ranges, and test external source visibility where permitted. Independent acceptance: Hosts are classified as private or globally addressed correctly and required outbound communication uses approved routing or NAT.

D:

That option would use `ss -ltn` or related appropriate flags to inspect listening endpoints and netcat or another client to test real transport reachability, 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 447

While verifying a Linux change request, an engineer finds: A cloud host is assigned 172.33.5.10 and a team labels it private merely because its first octet is 172. Which Linux behavior or technical principle BEST explains why the issue occurs? Select ONE best answer.

  1. A running process does not prove it is listening on the expected socket or interface; TCP and UDP socket state and bind address matter.
  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. 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.
  4. A transient hostname change is not necessarily persisted; hostname resolution and the configured system hostname are related but distinct functions.

Explanation

Correct Answer

C:

Relevant Linux operating 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. Scenario: A cloud host is assigned 172.33.5.10 and a team labels it private merely because its first octet is 172.

Incorrect Answers

A:

This alternative addresses Listening sockets with ss and netcat testing, not the specific issue of RFC1918 private addressing and internet routing: A running process does not prove it is listening on the expected socket or interface; TCP and UDP socket state and bind address matter. 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. Appropriate response: Identify RFC1918 blocks precisely and plan appropriate routing or address translation for connectivity to public destinations. Root-cause evidence: Inspect interface addresses and routing, compare to the exact RFC1918 CIDR ranges, and test external source visibility where permitted. Independent acceptance: Hosts are classified as private or globally addressed correctly and required outbound communication uses approved routing or NAT.

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. 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. Scenario: A cloud host is assigned 172.33.5.10 and a team labels it private merely because its first octet is 172.

D:

This alternative addresses Hostnamectl and durable host identification, not the specific issue of RFC1918 private addressing and internet routing: A transient hostname change is not necessarily persisted; hostname resolution and the configured system hostname are related but distinct functions. 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. Appropriate response: Identify RFC1918 blocks precisely and plan appropriate routing or address translation for connectivity to public destinations. Root-cause evidence: Inspect interface addresses and routing, compare to the exact RFC1918 CIDR ranges, and test external source visibility where permitted. Independent acceptance: Hosts are classified as private or globally addressed correctly and required outbound communication uses approved routing or NAT.

Question 448

A Linux administrator investigates the following system incident: A cloud host is assigned 172.33.5.10 and a team labels it private merely because its first octet is 172. Which evidence or command result MOST directly tests the suspected root cause? Select ONE best answer.

  1. Inspect interface addresses and routing, compare to the exact RFC1918 CIDR ranges, and test external source visibility where permitted.
  2. Inspect `systemctl` service state, NetworkManager device management, /etc/systemd/network and active connection profiles alongside `ip` state.
  3. Inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering rules.
  4. Claim every 172.x.x.x address is private and that any RFC1918 host can route directly across the public internet with no translation.

Explanation

Correct Answer

A:

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.

Incorrect Answers

B:

This alternative addresses NetworkManager and systemd-networkd configuration ownership, not the specific issue of RFC1918 private addressing and internet routing: Inspect `systemctl` service state, NetworkManager device management, /etc/systemd/network and active connection profiles alongside `ip` state.

C:

That option would inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering 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.

D:

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. It cannot establish a safe correction. 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.

Question 449

On a production Linux workstation or server, a technician observes: A cloud host is assigned 172.33.5.10 and a team labels it private merely because its first octet is 172. Which observed outcome BEST confirms a successful and properly scoped correction? Select ONE best answer.

  1. Claim every 172.x.x.x address is private and that any RFC1918 host can route directly across the public internet with no translation.
  2. Hosts are classified as private or globally addressed correctly and required outbound communication uses approved routing or NAT.
  3. Only the chosen manager owns the interface and configuration survives a controlled network-service restart without unexpected overrides.
  4. On-link hosts are identified correctly and off-link traffic follows the planned gateway without spurious local ARP attempts.

Explanation

Correct Answer

B:

Observable acceptance criterion: Hosts are classified as private or globally addressed correctly and required outbound communication uses approved routing or NAT. Scenario: A cloud host is assigned 172.33.5.10 and a team labels it private merely because its first octet is 172.

Incorrect Answers

A:

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. 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:

This alternative addresses NetworkManager and systemd-networkd configuration ownership, not the specific issue of RFC1918 private addressing and internet routing: Only the chosen manager owns the interface and configuration survives a controlled network-service restart without unexpected overrides. 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. Appropriate response: Identify RFC1918 blocks precisely and plan appropriate routing or address translation for connectivity to public destinations. Root-cause evidence: Inspect interface addresses and routing, compare to the exact RFC1918 CIDR ranges, and test external source visibility where permitted. Independent acceptance: Hosts are classified as private or globally addressed correctly and required outbound communication uses approved routing or NAT.

D:

This alternative addresses IPv4 CIDR network masks and subnet reachability, not the specific issue of RFC1918 private addressing and internet routing: On-link hosts are identified correctly and off-link traffic follows the planned gateway without spurious local ARP attempts. 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. Appropriate response: Identify RFC1918 blocks precisely and plan appropriate routing or address translation for connectivity to public destinations. Root-cause evidence: Inspect interface addresses and routing, compare to the exact RFC1918 CIDR ranges, and test external source visibility where permitted. Independent acceptance: Hosts are classified as private or globally addressed correctly and required outbound communication uses approved routing or NAT.

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.

LPI Level 1 (102-500) Practice Tests