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!

$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

Purchase LPI 102-500 Exam Training Products Individually

Premium File 120 Q&A

$76.99$69.99

Training Course 126 Lectures

$21.99 $19.99

Study Guide 962 Pages

$21.99 $19.99

LPI 102-500 Practice Test 47

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.

Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable.
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.
Identify the active network configuration manager and express persistent settings in its supported profiles or .network files without competing managers.
Inspect `ip -6 addr`, `ip -6 route`, router advertisements and a scoped ping6 to the link-local destination.
Inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering rules.

Explanation

Correct Answers

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.

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

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.

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.

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.

Question 461

While verifying a Linux change request, an engineer finds: A firewall rule opens TCP port 53 but DNS lookups fail when the resolver needs UDP query traffic. Which administrative step is the MOST appropriate way to resolve this issue? Select ONE best answer.

Assume all DNS queries always use TCP and that knowing port 53 alone identifies the transport without checking protocol.
Set the intended persistent static hostname with `hostnamectl` or supported distribution settings and validate local host mapping separately.
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.
Use `ss -ltn` or related appropriate flags to inspect listening endpoints and netcat or another client to test real transport reachability.

Explanation

Correct Answer

Recommended administrative action: 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.

Incorrect Answers

That option would assume all DNS queries always use TCP and that knowing port 53 alone identifies the transport without checking protocol, but it addresses a different concern. 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.

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

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

Question 462

A Linux administrator investigates the following system incident: A firewall rule opens TCP port 53 but DNS lookups fail when the resolver needs UDP query traffic. Which Linux behavior or technical principle BEST explains why the issue occurs? Select ONE best answer.

In IPv4 CIDR the prefix length specifies network bits; the remaining host bits determine subnet boundaries and usable address ranges.
Assume all DNS queries always use TCP and that knowing port 53 alone identifies the transport without checking protocol.
Wireless association, authentication and IP configuration are distinct stages; an SSID's visibility does not establish authorized connectivity.
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.

Explanation

Correct Answer

Relevant Linux operating principle: 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.

Incorrect Answers

This alternative addresses IPv4 CIDR network masks and subnet reachability, not the specific issue of Well-known TCP UDP port mapping: In IPv4 CIDR the prefix length specifies network bits; the remaining host bits determine subnet boundaries and usable address ranges. Linux principle: 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. Appropriate response: 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. Root-cause evidence: Consult /etc/services, inspect listening sockets with `ss` and test service behavior against firewall or resolver rules. Independent acceptance: Required traffic uses only documented service ports and protocols while irrelevant exposure stays blocked.

That option would assume all DNS queries always use TCP and that knowing port 53 alone identifies the transport without checking protocol, but it addresses a different concern. Appropriate response: 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.

This alternative addresses NetworkManager Wi-Fi authentication and saved profiles, not the specific issue of Well-known TCP UDP port mapping: Wireless association, authentication and IP configuration are distinct stages; an SSID's visibility does not establish authorized connectivity. Linux principle: 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. Appropriate response: 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. Root-cause evidence: Consult /etc/services, inspect listening sockets with `ss` and test service behavior against firewall or resolver rules. Independent acceptance: Required traffic uses only documented service ports and protocols while irrelevant exposure stays blocked.

Question 463

On a production Linux workstation or server, a technician observes: A firewall rule opens TCP port 53 but DNS lookups fail when the resolver needs UDP query traffic. Which evidence or command result MOST directly tests the suspected root cause? Select ONE best answer.

Assume all DNS queries always use TCP and that knowing port 53 alone identifies the transport without checking protocol.
Consult /etc/services, inspect listening sockets with `ss` and test service behavior against firewall or resolver rules.
Inspect protocol-specific packet traces and socket details, run both ICMP and application-layer reachability tests, and check filtering rules.
Compare `getent hosts name`, /etc/nsswitch.conf hosts line, /etc/hosts entry and DNS-only `dig` output.

Explanation

Correct Answer

Most direct verification evidence: Consult /etc/services, inspect listening sockets with `ss` and test service behavior against firewall or resolver rules.

Incorrect Answers

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

This alternative addresses Local hosts resolution versus DNS settings, not the specific issue of Well-known TCP UDP port mapping: Compare `getent hosts name`, /etc/nsswitch.conf hosts line, /etc/hosts entry and DNS-only `dig` output.

Question 464

During an LPIC-1 practice lab, the operator encounters this condition: A firewall rule opens TCP port 53 but DNS lookups fail when the resolver needs UDP query traffic. Which observed outcome BEST confirms a successful and properly scoped correction? Select ONE best answer.

Required traffic uses only documented service ports and protocols while irrelevant exposure stays blocked.
Host resolution follows the documented local and DNS precedence without stale overrides for the service name.
Assume all DNS queries always use TCP and that knowing port 53 alone identifies the transport without checking protocol.
The device associates to the approved wireless network, authenticates successfully and receives the expected network configuration.

Explanation

Correct Answer

Observable acceptance criterion: Required traffic uses only documented service ports and protocols while irrelevant exposure stays blocked.

Incorrect Answers

This alternative addresses Local hosts resolution versus DNS settings, not the specific issue of Well-known TCP UDP port mapping: Host resolution follows the documented local and DNS precedence without stale overrides for the service name. Linux principle: 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. Appropriate response: 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. Root-cause evidence: Consult /etc/services, inspect listening sockets with `ss` and test service behavior against firewall or resolver rules. Independent acceptance: Required traffic uses only documented service ports and protocols while irrelevant exposure stays blocked.

This shortcut is unsafe for the present Linux issue: Assume all DNS queries always use TCP and that knowing port 53 alone identifies the transport without checking protocol. 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.

This alternative addresses NetworkManager Wi-Fi authentication and saved profiles, not the specific issue of Well-known TCP UDP port mapping: The device associates to the approved wireless network, authenticates successfully and receives the expected network configuration. Linux principle: 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. Appropriate response: 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. Root-cause evidence: Consult /etc/services, inspect listening sockets with `ss` and test service behavior against firewall or resolver rules. Independent acceptance: Required traffic uses only documented service ports and protocols while irrelevant exposure stays blocked.

Question 465

A helpdesk escalation describes this Linux behavior: A firewall rule opens TCP port 53 but DNS lookups fail when the resolver needs UDP query traffic. Which misleading assumption MOST directly contributes to this failure and should be rejected? Select ONE best answer.

Assume all DNS queries always use TCP and that knowing port 53 alone identifies the transport without checking protocol.
Assume editing /etc/resolv.conf always overrides a conflicting /etc/hosts entry regardless of NSS hosts order.
Assume UDP automatically retries dropped packets and that failure of ping always means every TCP application on the destination is unreachable.
Assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover.

Explanation

Correct Answer

Reject this specific misconception: Assume all DNS queries always use TCP and that knowing port 53 alone identifies the transport without checking protocol. It incorrectly assumes behavior that conflicts with the observed Linux conditions.

Incorrect Answers

This alternative addresses Local hosts resolution versus DNS settings, not the specific issue of Well-known TCP UDP port mapping: Assume editing /etc/resolv.conf always overrides a conflicting /etc/hosts entry regardless of NSS hosts order.

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

That option would assume having any IPv4 address automatically creates a correct default gateway and that multiple default routes always provide harmless equal-cost failover, but it addresses a different concern. 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.

Question 466

An operations handoff identifies this problem: A technician claims port 22 provides HTTP rather than SSH and moves web-service firewall permissions to the wrong socket. Which administrative step is the MOST appropriate way to resolve this issue? Select ONE best answer.

Use `ss -ltn` or related appropriate flags to inspect listening endpoints and netcat or another client to test real transport reachability.
Configure and interpret IPv6 addresses and prefix lengths correctly and supply a scope interface for link-local communication when needed.
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.
Assume all DNS queries always use TCP and that knowing port 53 alone identifies the transport without checking protocol.

Explanation

Correct Answer

Recommended administrative action: 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.

Incorrect Answers

This alternative addresses Listening sockets with ss and netcat testing, not the specific issue of Well-known TCP UDP port mapping: Use `ss -ltn` or related appropriate flags to inspect listening endpoints and netcat or another client to test real transport reachability.

That option would configure and interpret IPv6 addresses and prefix lengths correctly and supply a scope interface for link-local communication when needed, but it addresses a different concern. 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.

Question 467

A team maintaining a Linux host reports: A technician claims port 22 provides HTTP rather than SSH and moves web-service firewall permissions to the wrong socket. Which Linux behavior or technical principle BEST explains why the issue occurs? Select ONE best answer.

Different Linux networking managers apply persistent interface settings through their own configurations; conflicting ownership can cause changes to be ignored or overwritten.
Assume all DNS queries always use TCP and that knowing port 53 alone identifies the transport without checking protocol.
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.
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.

Explanation

Correct Answer

Incorrect Answers

This alternative addresses NetworkManager and systemd-networkd configuration ownership, not the specific issue of Well-known TCP UDP port mapping: Different Linux networking managers apply persistent interface settings through their own configurations; conflicting ownership can cause changes to be ignored or overwritten. Linux principle: 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. Appropriate response: 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. Root-cause evidence: Consult /etc/services, inspect listening sockets with `ss` and test service behavior against firewall or resolver rules. Independent acceptance: Required traffic uses only documented service ports and protocols while irrelevant exposure stays blocked.

This alternative addresses RFC1918 private addressing and internet routing, not the specific issue of Well-known TCP UDP port mapping: 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. Linux principle: 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. Appropriate response: 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. Root-cause evidence: Consult /etc/services, inspect listening sockets with `ss` and test service behavior against firewall or resolver rules. Independent acceptance: Required traffic uses only documented service ports and protocols while irrelevant exposure stays blocked.

Question 468

While verifying a Linux change request, an engineer finds: A technician claims port 22 provides HTTP rather than SSH and moves web-service firewall permissions to the wrong socket. Which evidence or command result MOST directly tests the suspected root cause? Select ONE best answer.

Inspect `ip -br link`, `ip address show`, carrier state and manager logs before and after a controlled interface activation.
Consult /etc/services, inspect listening sockets with `ss` and test service behavior against firewall or resolver rules.
Inspect `hostnamectl status`, /etc/hostname, /etc/hosts and `getent hosts` output before and after reboot.
Assume all DNS queries always use TCP and that knowing port 53 alone identifies the transport without checking protocol.

Explanation

Correct Answer

Most direct verification evidence: Consult /etc/services, inspect listening sockets with `ss` and test service behavior against firewall or resolver rules.

Incorrect Answers

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

This alternative addresses Hostnamectl and durable host identification, not the specific issue of Well-known TCP UDP port mapping: Inspect `hostnamectl status`, /etc/hostname, /etc/hosts and `getent hosts` output before and after reboot.

This shortcut is unsafe for the present Linux issue: Assume all DNS queries always use TCP and that knowing port 53 alone identifies the transport without checking protocol. It cannot establish a safe correction. Linux principle: 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. Appropriate response: 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. Root-cause evidence: Consult /etc/services, inspect listening sockets with `ss` and test service behavior against firewall or resolver rules. Independent acceptance: Required traffic uses only documented service ports and protocols while irrelevant exposure stays blocked.

Question 469

A Linux administrator investigates the following system incident: A technician claims port 22 provides HTTP rather than SSH and moves web-service firewall permissions to the wrong socket. Which observed outcome BEST confirms a successful and properly scoped correction? Select ONE best answer.

The device associates to the approved wireless network, authenticates successfully and receives the expected network configuration.
The selected transport matches reliability requirements and diagnostics distinguish blocked ICMP from a reachable TCP service.
Assume all DNS queries always use TCP and that knowing port 53 alone identifies the transport without checking protocol.
Required traffic uses only documented service ports and protocols while irrelevant exposure stays blocked.

Explanation

Correct Answer

Observable acceptance criterion: Required traffic uses only documented service ports and protocols while irrelevant exposure stays blocked.

Incorrect Answers

This alternative addresses TCP versus UDP versus ICMP diagnostics, not the specific issue of Well-known TCP UDP port mapping: The selected transport matches reliability requirements and diagnostics distinguish blocked ICMP from a reachable TCP service. Linux principle: 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. Appropriate response: 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. Root-cause evidence: Consult /etc/services, inspect listening sockets with `ss` and test service behavior against firewall or resolver rules. Independent acceptance: Required traffic uses only documented service ports and protocols while irrelevant exposure stays blocked.

Question 470

On a production Linux workstation or server, a technician observes: A technician claims port 22 provides HTTP rather than SSH and moves web-service firewall permissions to the wrong socket. Which TWO complementary steps provide the best corrective action and its most direct diagnostic verification? Select TWO answers.

Identify the active network configuration manager and express persistent settings in its supported profiles or .network files without competing managers.
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.
Consult /etc/services, inspect listening sockets with `ss` and test service behavior against firewall or resolver rules.
Inspect `ss -ltnp`, service bind configuration, local and remote connection attempts and firewall rules.
Assume all DNS queries always use TCP and that knowing port 53 alone identifies the transport without checking protocol.

Explanation

Correct Answers

Recommended administrative action: 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. Linux principle: 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.

Most direct verification evidence: Consult /etc/services, inspect listening sockets with `ss` and test service behavior against firewall or resolver rules. Linux principle: 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.

Incorrect Answers

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

This alternative addresses Listening sockets with ss and netcat testing, not the specific issue of Well-known TCP UDP port mapping: Inspect `ss -ltnp`, service bind configuration, local and remote connection attempts and firewall rules.

LPI Level 1 (102-500) Practice Tests

LPI 102-500 Practice Test 45 - 10 Questions (Last Reviewed 30-Sep-2026)
LPI 102-500 Practice Test 46 - 10 Questions (Last Reviewed 29-Sep-2026)
LPI 102-500 Practice Test 47 - 10 Questions (Last Reviewed 28-Sep-2026)
LPI 102-500 Practice Test 48 - 10 Questions (Last Reviewed 27-Sep-2026)
LPI 102-500 Practice Test 49 - 10 Questions (Last Reviewed 26-Sep-2026)