You save $69.98
102-500 Premium Bundle
- Premium File 120 Questions & Answers
- Last Update: Nov 10, 2026
- Training Course 126 Lectures
- Study Guide 962 Pages
You save $69.98
A Linux troubleshooter is gathering specific evidence for this situation: Two hosts cannot synchronize their clocks after a network policy permits only TCP port 123 for the time service. Which check MOST directly diagnoses or confirms the technical condition described?
Inspect UDP 123 counters and the NTP client's peer statistics. This check targets the relevant state for ntp port and udp transport and directly assesses the observed behavior. The result should be evaluated against: The NTP client selects a reachable source and measured offset approaches the expected range.
Inspect the server's listener, TLS handshake and requested URL scheme. This check is relevant to https service versus plain http but not the most targeted diagnosis of ntp port and udp transport. The specific check is: Inspect UDP 123 counters and the NTP client's peer statistics.
Inspect resolvectl status together with resolv.conf and listener addresses. This check is relevant to distinguishing a systemd-resolved stub from external dns but not the most targeted diagnosis of ntp port and udp transport. The specific check is: Inspect UDP 123 counters and the NTP client's peer statistics.
Trace protocol selection and run a packet-loss transfer test. This check is relevant to tcp delivery versus udp datagrams but not the most targeted diagnosis of ntp port and udp transport. The specific check is: Inspect UDP 123 counters and the NTP client's peer statistics.
A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: A network diagram labels TCP port 80 as the default encrypted HTTPS endpoint and clients receive protocol errors. Which step MOST directly corrects the specific problem described?
Use HTTPS with the configured TLS listener, conventionally TCP 443, rather than assuming port 80 is encrypted. This targets the observed issue, https service versus plain http, rather than a separate Linux configuration. Underlying behavior: HTTP over TCP 80 is normally plaintext; HTTPS typically uses TLS over TCP 443. Verify the action by checking: The client completes an authenticated TLS handshake on the expected HTTPS endpoint.
Test the actual application protocol and interpret ICMP results as one diagnostic signal only. This is an appropriate response to a different issue (icmp diagnostic traffic limitations) but does not MOST directly address the explicit https service versus plain http failure.
Test the remote host's actual IPv6 address, reserving ::1 for the local loopback interface. This is an appropriate response to a different issue (ipv6 loopback diagnosis) but does not MOST directly address the explicit https service versus plain http failure.
Configure the intended static address in the persistent NetworkManager connection profile using nmcli. This is an appropriate response to a different issue (persistent static ipv4 with networkmanager) but does not MOST directly address the explicit https service versus plain http failure.
A Linux team is checking the acceptance evidence for this specific situation: A network diagram labels TCP port 80 as the default encrypted HTTPS endpoint and clients receive protocol errors. Which observation BEST confirms that this particular issue has been corrected?
The client completes an authenticated TLS handshake on the expected HTTPS endpoint. That evidence specifically demonstrates recovery from https service versus plain http. The technical reason is: HTTP over TCP 80 is normally plaintext; HTTPS typically uses TLS over TCP 443.
The same needed interface status is obtained without installing deprecated legacy tools. This can validate recognizing legacy net-tools alternatives, but it does not establish that the described https service versus plain http issue is fixed. The case-specific evidence is: The client completes an authenticated TLS handshake on the expected HTTPS endpoint.
A test under packet loss preserves expected ordering and complete data transfer. This can validate tcp delivery versus udp datagrams, but it does not establish that the described https service versus plain http issue is fixed. The case-specific evidence is: The client completes an authenticated TLS handshake on the expected HTTPS endpoint.
An authenticated SSH session reaches the expected host key over the authorized port. This can validate ssh default port recognition, but it does not establish that the described https service versus plain http issue is fixed. The case-specific evidence is: The client completes an authenticated TLS handshake on the expected HTTPS endpoint.
A Linux engineer reviews the underlying behavior in this particular case: A network diagram labels TCP port 80 as the default encrypted HTTPS endpoint and clients receive protocol errors. Which technical behavior BEST explains this particular failure and its remedy?
HTTP over TCP 80 is normally plaintext; HTTPS typically uses TLS over TCP 443. This Linux behavior explains the observed symptoms and supports the precise remedy: Use HTTPS with the configured TLS listener, conventionally TCP 443, rather than assuming port 80 is encrypted.
SSH normally listens on TCP 22; TCP 23 is traditionally associated with Telnet. This describes another behavior (ssh default port recognition) and does not explain the stated https service versus plain http failure. The operative behavior is: HTTP over TCP 80 is normally plaintext; HTTPS typically uses TLS over TCP 443.
An IPv4 /26 leaves six host bits, yielding 64 total addresses for the subnet. This describes another behavior (cidr prefix and ipv4 usable hosts) and does not explain the stated https service versus plain http failure. The operative behavior is: HTTP over TCP 80 is normally plaintext; HTTPS typically uses TLS over TCP 443.
IPv4 hosts need link-layer neighbor resolution to send packets to an on-link gateway. This describes another behavior (inspecting neighbor discovery for an ipv4 gateway) and does not explain the stated https service versus plain http failure. The operative behavior is: HTTP over TCP 80 is normally plaintext; HTTPS typically uses TLS over TCP 443.
A Linux operating control has not corrected the following specific problem: A network diagram labels TCP port 80 as the default encrypted HTTPS endpoint and clients receive protocol errors. Which outcome is the MOST directly associated operational risk if this problem remains?
Credential-bearing traffic may be sent without expected transport protection. This is the directly relevant consequence of leaving the https service versus plain http problem unresolved. The appropriate preventive change is: Use HTTPS with the configured TLS listener, conventionally TCP 443, rather than assuming port 80 is encrypted.
Remote clients cannot reach a service addressed only by a link-local destination. This consequence is connected to ipv6 link-local scope rather than the MOST direct exposure in the stated https service versus plain http problem. The specific consequence is: Credential-bearing traffic may be sent without expected transport protection.
External services may reject or fail to return traffic from unroutable private addresses. This consequence is connected to private ipv4 address identification rather than the MOST direct exposure in the stated https service versus plain http problem. The specific consequence is: Credential-bearing traffic may be sent without expected transport protection.
Ad-hoc file changes may disconnect clients from the active stub resolver. This consequence is connected to resolver file managed by systemd-resolved rather than the MOST direct exposure in the stated https service versus plain http problem. The specific consequence is: Credential-bearing traffic may be sent without expected transport protection.
A Linux troubleshooter is gathering specific evidence for this situation: A network diagram labels TCP port 80 as the default encrypted HTTPS endpoint and clients receive protocol errors. Which check MOST directly diagnoses or confirms the technical condition described?
Inspect the server's listener, TLS handshake and requested URL scheme. This check targets the relevant state for https service versus plain http and directly assesses the observed behavior. The result should be evaluated against: The client completes an authenticated TLS handshake on the expected HTTPS endpoint.
Inspect nmcli connection interface-name and nmcli device status. This check is relevant to networkmanager connection bound to wrong interface but not the most targeted diagnosis of https service versus plain http. The specific check is: Inspect the server's listener, TLS handshake and requested URL scheme.
Compare ping results with a direct TCP service connection attempt. This check is relevant to icmp diagnostic traffic limitations but not the most targeted diagnosis of https service versus plain http. The specific check is: Inspect the server's listener, TLS handshake and requested URL scheme.
Inspect UDP 123 counters and the NTP client's peer statistics. This check is relevant to ntp port and udp transport but not the most targeted diagnosis of https service versus plain http. The specific check is: Inspect the server's listener, TLS handshake and requested URL scheme.
A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: An engineer sets a temporary IPv4 address using ip addr, but the machine loses it after NetworkManager reconnects. Which step MOST directly corrects the specific problem described?
Configure the intended static address in the persistent NetworkManager connection profile using nmcli. This targets the observed issue, persistent static ipv4 with networkmanager, rather than a separate Linux configuration. Underlying behavior: ip addr changes runtime kernel interface state; NetworkManager connection profiles store persistent settings. Verify the action by checking: The IP address survives connection reactivation and a reboot of the test machine.
Test the actual application protocol and interpret ICMP results as one diagnostic signal only. This is an appropriate response to a different issue (icmp diagnostic traffic limitations) but does not MOST directly address the explicit persistent static ipv4 with networkmanager failure.
Change the relevant NetworkManager connection DNS properties and reactivate the profile. This is an appropriate response to a different issue (persisting dns settings through networkmanager) but does not MOST directly address the explicit persistent static ipv4 with networkmanager failure.
Enable connection autoconnect for the correct NetworkManager profile. This is an appropriate response to a different issue (enabling automatic activation of a connection) but does not MOST directly address the explicit persistent static ipv4 with networkmanager failure.
A Linux team is checking the acceptance evidence for this specific situation: An engineer sets a temporary IPv4 address using ip addr, but the machine loses it after NetworkManager reconnects. Which observation BEST confirms that this particular issue has been corrected?
The IP address survives connection reactivation and a reboot of the test machine. That evidence specifically demonstrates recovery from persistent static ipv4 with networkmanager. The technical reason is: ip addr changes runtime kernel interface state; NetworkManager connection profiles store persistent settings.
The interface associates with the intended access point and receives valid network configuration. This can validate managing wi-fi association in networkmanager, but it does not establish that the described persistent static ipv4 with networkmanager issue is fixed. The case-specific evidence is: The IP address survives connection reactivation and a reboot of the test machine.
The connection becomes active automatically when the link and system are ready. This can validate enabling automatic activation of a connection, but it does not establish that the described persistent static ipv4 with networkmanager issue is fixed. The case-specific evidence is: The IP address survives connection reactivation and a reboot of the test machine.
The planned subnet contains 64 addresses including the network and broadcast addresses, with 62 conventional usable hosts. This can validate cidr prefix and ipv4 usable hosts, but it does not establish that the described persistent static ipv4 with networkmanager issue is fixed. The case-specific evidence is: The IP address survives connection reactivation and a reboot of the test machine.
A Linux engineer reviews the underlying behavior in this particular case: An engineer sets a temporary IPv4 address using ip addr, but the machine loses it after NetworkManager reconnects. Which technical behavior BEST explains this particular failure and its remedy?
ip addr changes runtime kernel interface state; NetworkManager connection profiles store persistent settings. This Linux behavior explains the observed symptoms and supports the precise remedy: Configure the intended static address in the persistent NetworkManager connection profile using nmcli.
Wireless association and authentication precede DHCP or static IP connectivity. This describes another behavior (managing wi-fi association in networkmanager) and does not explain the stated persistent static ipv4 with networkmanager failure. The operative behavior is: ip addr changes runtime kernel interface state; NetworkManager connection profiles store persistent settings.
Persistent interface profiles recreate routes when interfaces are activated. This describes another behavior (persisting an ipv4 default gateway) and does not explain the stated persistent static ipv4 with networkmanager failure. The operative behavior is: ip addr changes runtime kernel interface state; NetworkManager connection profiles store persistent settings.
A TCP connection test probes application transport reachability even when ICMP echo is filtered. This describes another behavior (testing a tcp service directly with netcat) and does not explain the stated persistent static ipv4 with networkmanager failure. The operative behavior is: ip addr changes runtime kernel interface state; NetworkManager connection profiles store persistent settings.
A Linux operating control has not corrected the following specific problem: An engineer sets a temporary IPv4 address using ip addr, but the machine loses it after NetworkManager reconnects. Which outcome is the MOST directly associated operational risk if this problem remains?
A host may lose network service after restart despite a successful temporary test. This is the directly relevant consequence of leaving the persistent static ipv4 with networkmanager problem unresolved. The appropriate preventive change is: Configure the intended static address in the persistent NetworkManager connection profile using nmcli.
Hidden routing loops or detours can persist despite a successful basic ping. This consequence is connected to tracing unexpected intermediate hops rather than the MOST direct exposure in the stated persistent static ipv4 with networkmanager problem. The specific consequence is: A host may lose network service after restart despite a successful temporary test.
The host can reach local peers but not off-subnet services after reboot. This consequence is connected to persisting an ipv4 default gateway rather than the MOST direct exposure in the stated persistent static ipv4 with networkmanager problem. The specific consequence is: A host may lose network service after restart despite a successful temporary test.
Applications can connect to retired addresses despite healthy authoritative DNS. This consequence is connected to host lookup precedence between files and dns rather than the MOST direct exposure in the stated persistent static ipv4 with networkmanager problem. The specific consequence is: A host may lose network service after restart despite a successful temporary test.
A Linux troubleshooter is gathering specific evidence for this situation: An engineer sets a temporary IPv4 address using ip addr, but the machine loses it after NetworkManager reconnects. Which check MOST directly diagnoses or confirms the technical condition described?
Compare ip address output with nmcli connection show for the relevant profile. This check targets the relevant state for persistent static ipv4 with networkmanager and directly assesses the observed behavior. The result should be evaluated against: The IP address survives connection reactivation and a reboot of the test machine.
Check nmcli device show DNS information and the effective resolv.conf ownership. This check is relevant to persisting dns settings through networkmanager but not the most targeted diagnosis of persistent static ipv4 with networkmanager. The specific check is: Compare ip address output with nmcli connection show for the relevant profile.
Compare hostnamectl status with the effective hostname command after reboot. This check is relevant to persisting the system hostname but not the most targeted diagnosis of persistent static ipv4 with networkmanager. The specific check is: Compare ip address output with nmcli connection show for the relevant profile.
Compare ip route get with all matching entries in ip route show. This check is relevant to choosing routes through longest-prefix match but not the most targeted diagnosis of persistent static ipv4 with networkmanager. The specific check is: Compare ip address output with nmcli connection show for the relevant profile.
or Guarantee your success by buying the full version which covers the full latest pool of questions. (120 Questions, Last Updated on Nov 10, 2026)
Please check your mailbox for a message from support@examlabs.com and follow the directions.