100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 650
A host intermittently activates the wrong static address after reboot because two eligible NetworkManager profiles target the same interface. Which THREE actions form a suitable remediation, verification and prevention plan? Select THREE.
- Verify agent polling and trap delivery separately under the final firewall policy.
- Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits.
- Use layered diagnostics rather than interpreting one ICMP result as application health.
- Retire obsolete profiles and document deterministic activation priority.
- List connection profiles and check which UUID becomes active after reboot.
- Assign the intended interface to the correct profile and review autoconnect priority for competing profiles.
Explanation
Correct Answers
D:Retire obsolete profiles and document deterministic activation priority. It prevents repetition of the condition: Profile priority and autoconnect policy can select an unintended saved connection.
E:List connection profiles and check which UUID becomes active after reboot. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: Profile priority and autoconnect policy can select an unintended saved connection.
F:Assign the intended interface to the correct profile and review autoconnect priority for competing profiles. It is the direct response; verify the result by: List connection profiles and check which UUID becomes active after reboot.
Incorrect Answers
A:Verify agent polling and trap delivery separately under the final firewall policy. could help with snmp manager polling; it neither resolves nor demonstrates the current requirement. The distinguishing check is: List connection profiles and check which UUID becomes active after reboot.
B:Set reachable approved DNS servers through the active resolver manager, avoiding generated-file edits. could help with resolver nameserver failure; it neither resolves nor demonstrates the current requirement. The distinguishing check is: List connection profiles and check which UUID becomes active after reboot.
C:It would address icmp diagnostic role rather than the present problem. The appropriate correction here is: Assign the intended interface to the correct profile and review autoconnect priority for competing profiles.
Question 651
A cloned network profile binds to an old device MAC and does not activate on a replacement adapter. Which mechanism best explains the difference between expectation and result?
- Physical/link or buffering issues are indicated by interface statistics, not necessarily a DNS fault.
- Profile matching constraints can prevent a saved connection from applying to the intended new interface.
- DNS commonly uses UDP and also uses TCP for responses and operations requiring it.
- An IPv4 default route does not substitute for IPv6 routing information.
Explanation
Correct Answer
B:Profile matching constraints can prevent a saved connection from applying to the intended new interface. That cause connects the stated symptom to the corrective action: Review the saved profile's interface name and MAC match and update it for the authorized adapter.
Incorrect Answers
A:This belongs to interface rx errors and drops, where Physical/link or buffering issues are indicated by interface statistics, not necessarily a DNS fault. The current issue instead is: Profile matching constraints can prevent a saved connection from applying to the intended new interface.
C:This belongs to dns usually udp but can use tcp, where DNS commonly uses UDP and also uses TCP for responses and operations requiring it. The current issue instead is: Profile matching constraints can prevent a saved connection from applying to the intended new interface.
D:This belongs to ipv6 route omission, where An IPv4 default route does not substitute for IPv6 routing information. The current issue instead is: Profile matching constraints can prevent a saved connection from applying to the intended new interface.
Question 652
A cloned network profile binds to an old device MAC and does not activate on a replacement adapter. Which remedial step follows from the observed mechanism?
- Correct the default route via the approved on-link gateway and persist the configuration.
- Review the saved profile's interface name and MAC match and update it for the authorized adapter.
- Choose TCP when transport-level reliability is required or implement those controls in the UDP application.
- Test the actual application protocol and inspect routing/firewall policy before concluding service failure.
Explanation
Correct Answer
B:Review the saved profile's interface name and MAC match and update it for the authorized adapter. Unlike a broad workaround, it targets the observed cause: Profile matching constraints can prevent a saved connection from applying to the intended new interface.
Incorrect Answers
A:That choice responds to a default route points to wrong gateway failure. In this incident, Profile matching constraints can prevent a saved connection from applying to the intended new interface.
C:The test for tcp versus udp application fit would be: Drop and reorder packets in a test and observe how the application handles missing data. The relevant acceptance check here is: Compare nmcli device status with profile match fields and confirm activation.
D:The test for icmp diagnostic role would be: Compare ping, traceroute and a protocol-specific connection test to the same host. The relevant acceptance check here is: Compare nmcli device status with profile match fields and confirm activation.
Question 653
A cloned network profile binds to an old device MAC and does not activate on a replacement adapter. What diagnostic result would demonstrate the target behavior?
- Compare nmcli device status with profile match fields and confirm activation.
- Check ip -6 addr and ping with the correct interface scope to an on-link neighbor.
- Drop and reorder packets in a test and observe how the application handles missing data.
- Compare a local listener test with network captures and remote TCP connection behavior.
Explanation
Correct Answer
A:Compare nmcli device status with profile match fields and confirm activation. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
Incorrect Answers
B:This belongs to ipv6 link-local scope, where IPv6 link-local addresses are scoped to one link and are not routed across ordinary network boundaries. The current issue instead is: Profile matching constraints can prevent a saved connection from applying to the intended new interface.
C:This belongs to tcp versus udp application fit, where UDP datagrams do not inherently provide TCP's reliable stream, retransmission and ordering guarantees. The current issue instead is: Profile matching constraints can prevent a saved connection from applying to the intended new interface.
D:The test for timeout versus refusal would be: Compare a local listener test with network captures and remote TCP connection behavior. The relevant acceptance check here is: Compare nmcli device status with profile match fields and confirm activation.
Question 654
A cloned network profile binds to an old device MAC and does not activate on a replacement adapter. Which ongoing control would best reduce the chance of the issue returning?
- Review interface identity constraints during hardware replacement.
- Model protocol and port combinations rather than assuming one transport for all DNS behavior.
- Document timeout and refusal as distinct evidence types in runbooks.
- Avoid relying on ambiguous single-label names across administrative zones.
Explanation
Correct Answer
A:Review interface identity constraints during hardware replacement. It prevents repetition of the condition: Profile matching constraints can prevent a saved connection from applying to the intended new interface.
Incorrect Answers
B:Model protocol and port combinations rather than assuming one transport for all DNS behavior. could help with dns usually udp but can use tcp; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Compare nmcli device status with profile match fields and confirm activation.
C:That choice responds to a timeout versus refusal failure. In this incident, Profile matching constraints can prevent a saved connection from applying to the intended new interface.
D:The test for search suffix causes misleading name would be: Compare lookups for the short name and the explicit FQDN under the same resolver. The relevant acceptance check here is: Compare nmcli device status with profile match fields and confirm activation.
Question 655
A cloned network profile binds to an old device MAC and does not activate on a replacement adapter. Select TWO justified actions that address this particular problem and confirm closure.
- Include protocol-specific checks for important service dependencies.
- Compare ping, traceroute and a protocol-specific connection test to the same host.
- Use ip link set dev interface up after confirming the intended port and policy.
- Review the saved profile's interface name and MAC match and update it for the authorized adapter.
- Compare nmcli device status with profile match fields and confirm activation.
Explanation
Correct Answers
D:Review the saved profile's interface name and MAC match and update it for the authorized adapter. It addresses the root cause, while Review interface identity constraints during hardware replacement. reduces future recurrence.
E:Compare nmcli device status with profile match fields and confirm activation. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
Incorrect Answers
A:The test for network port test without application protocol would be: Test the port from both sides of the filtering boundary and compare the result. The relevant acceptance check here is: Compare nmcli device status with profile match fields and confirm activation.
B:Compare ping, traceroute and a protocol-specific connection test to the same host. could help with icmp diagnostic role; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Compare nmcli device status with profile match fields and confirm activation.
C:This option assumes An administratively down interface cannot pass ordinary traffic until brought up. The reported symptoms instead call for: Review the saved profile's interface name and MAC match and update it for the authorized adapter.
Question 656
A development host resolves short internal names only when fully qualified because the configured search domain is missing. Which mechanism best explains the difference between expectation and result?
- The failure is likely beyond the local interface and should be localized by path probes.
- DNS commonly uses UDP and also uses TCP for responses and operations requiring it.
- 127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers.
- The resolver's search list affects qualification of unqualified hostnames.
Explanation
Correct Answer
D:The resolver's search list affects qualification of unqualified hostnames. The administrator should distinguish this from unrelated symptoms by checking: Compare short-name and fully qualified getent lookups after reconnect.
Incorrect Answers
A:That choice responds to a traceroute reveals upstream hop loss failure. In this incident, The resolver's search list affects qualification of unqualified hostnames.
B:This option assumes DNS commonly uses UDP and also uses TCP for responses and operations requiring it. The reported symptoms instead call for: Set the approved search domain in the active connection or resolver manager.
C:This belongs to systemd-resolved stub target, where 127.0.0.53 commonly represents the local systemd-resolved stub resolver forwarding to configured upstream servers. The current issue instead is: The resolver's search list affects qualification of unqualified hostnames.
Question 657
A development host resolves short internal names only when fully qualified because the configured search domain is missing. Which change most directly meets the stated requirement?
- Configure the approved SSH destination on TCP 22 or the explicitly overridden service port.
- Start or reconfigure the service to bind its intended listener, then review host firewall rules.
- Set the approved search domain in the active connection or resolver manager.
- Allow narrowly scoped polling traffic on UDP 161 to the approved agent.
Explanation
Correct Answer
C:Set the approved search domain in the active connection or resolver manager. This is appropriate because The resolver's search list affects qualification of unqualified hostnames.
Incorrect Answers
A:Configure the approved SSH destination on TCP 22 or the explicitly overridden service port. belongs to a situation where Standard SSH service is TCP 22; SMTP mail transfer commonly uses TCP 25. Here the evidence supports a different requirement: Set the approved search domain in the active connection or resolver manager.
B:The test for listener missing on local port would be: Use ss -ltnp and a local TCP connection test before testing remotely. The relevant acceptance check here is: Compare short-name and fully qualified getent lookups after reconnect.
D:The test for snmp manager polling would be: Verify agent polling and trap delivery separately under the final firewall policy. The relevant acceptance check here is: Compare short-name and fully qualified getent lookups after reconnect.
Question 658
A development host resolves short internal names only when fully qualified because the configured search domain is missing. How should the administrator verify the required behavior?
- Compare short-name and fully qualified getent lookups after reconnect.
- Check ip addr show dev interface and run an on-link test to confirm reachability.
- Test the port from both sides of the filtering boundary and compare the result.
- Use ip route get destination and compare path selection before and after.
Explanation
Correct Answer
A:Compare short-name and fully qualified getent lookups after reconnect. The test is evidence-based because the underlying failure was: The resolver's search list affects qualification of unqualified hostnames.
Incorrect Answers
B:That choice responds to a missing address on live interface failure. In this incident, The resolver's search list affects qualification of unqualified hostnames.
C:The test for network port test without application protocol would be: Test the port from both sides of the filtering boundary and compare the result. The relevant acceptance check here is: Compare short-name and fully qualified getent lookups after reconnect.
D:The test for default route points to wrong gateway would be: Use ip route get destination and compare path selection before and after. The relevant acceptance check here is: Compare short-name and fully qualified getent lookups after reconnect.
Question 659
A development host resolves short internal names only when fully qualified because the configured search domain is missing. What operational safeguard addresses the root cause?
- Avoid hand-written IPv4-only parsing in dual-stack automation.
- Document search domains explicitly to avoid ambiguous short-name resolution.
- Record interface scope and address type when debugging IPv6 endpoints.
- Record intended source identities for multi-homed application traffic.
Explanation
Correct Answer
B:Document search domains explicitly to avoid ambiguous short-name resolution. It makes the outcome of the targeted repair (Set the approved search domain in the active connection or resolver manager.) repeatable.
Incorrect Answers
A:IPv6 addresses are 128 bits and use colon-separated hexadecimal presentation with compression rules. That describes a different fault. Here, The resolver's search list affects qualification of unqualified hostnames.
C:Record interface scope and address type when debugging IPv6 endpoints. belongs to a situation where IPv6 link-local addresses are scoped to one link and are not routed across ordinary network boundaries. Here the evidence supports a different requirement: Document search domains explicitly to avoid ambiguous short-name resolution.
D:This belongs to wrong source address selection, where Source address selection and policy routing can choose an unintended outbound identity. The current issue instead is: The resolver's search list affects qualification of unqualified hostnames.
Question 660
A development host resolves short internal names only when fully qualified because the configured search domain is missing. Choose THREE measures that together correct the failure, demonstrate success and reduce recurrence.
- Compare short-name and fully qualified getent lookups after reconnect.
- Set the approved search domain in the active connection or resolver manager.
- Install a valid default route via the appropriate on-link gateway, then make it persistent.
- Compute the network and broadcast addresses using the mask and confirm the host configuration.
- Document search domains explicitly to avoid ambiguous short-name resolution.
- Use multiple path and endpoint tests because routers may rate-limit probe replies.
Explanation
Correct Answers
A:Compare short-name and fully qualified getent lookups after reconnect. It verifies that the targeted action (Set the approved search domain in the active connection or resolver manager.) achieved its intended outcome.
B:Set the approved search domain in the active connection or resolver manager. Unlike a broad workaround, it targets the observed cause: The resolver's search list affects qualification of unqualified hostnames.
E:Document search domains explicitly to avoid ambiguous short-name resolution. Sustained checks matter because The resolver's search list affects qualification of unqualified hostnames.
Incorrect Answers
C:Install a valid default route via the appropriate on-link gateway, then make it persistent. belongs to a situation where The local connected route does not tell the kernel where to send traffic outside the connected subnet. Here the evidence supports a different requirement: Set the approved search domain in the active connection or resolver manager.
D:Compute the network and broadcast addresses using the mask and confirm the host configuration. could help with ipv4 network boundary; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Compare short-name and fully qualified getent lookups after reconnect.
F:It would address traceroute reveals upstream hop loss rather than the present problem. The appropriate correction here is: Set the approved search domain in the active connection or resolver manager.
LPI Level 1 (102-500) Practice Tests