Pass LPI 102-500 Exam in First Attempt Guaranteed!
Get 100% Latest Exam Questions, Accurate & Verified Answers!
30 Days Free Updates, Instant Download!
LPI 102-500 Practice Test 75
Question 740
At fictional Clearwater Logistics, the Linux network operations team is working while investigating an observed production-like support incident. The Linux scenario is: A troubleshooting script sees a valid dig response but applications still report an unknown hostname. The decisive evidence is: dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. Which paired action and independent proof BEST satisfies the requirement?
Explanation
Correct Answer
The application's standard name lookup and an appropriate DNS check both resolve the expected host. This measures whether the response corrected dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration rather than merely completing a configuration step.
Incorrect Answers
A test that scoped correction: Permit the required approved DNS transport paths and validate both UDP and TCP resolution behavior. Independent acceptance: A standard and a larger DNS response succeed through the intended IPv6 resolver would not demonstrate closure of this condition. The needed proof is the application's standard name lookup and an appropriate DNS check both resolve the expected host.
Scoped correction: Select one intended network configuration manager for that interface and remove the conflicting configuration. Independent acceptance: After two controlled reboots the interface keeps one consistent address, route and DNS configuration. That does not demonstrate the case-specific success condition: the application's standard name lookup and an appropriate DNS check both resolve the expected host. Direct DNS queries and system library hostname resolution may take different paths.
Scoped correction: Configure the approved transport protocol and port combination needed for the service. Independent acceptance: An authorized TCP connection to the service establishes while unrelated ports remain closed. That result does not test the original problem, identified by dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. Recovery must show that the application's standard name lookup and an appropriate DNS check both resolve the expected host.
Question 741
At fictional Lakeshore Analytics, the Linux network operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: Operators see 127.0.0.53 in /etc/resolv.conf and replace it with a public resolver, breaking split-DNS domains. The diagnostic evidence is: resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. Which bounded step BEST resolves the described problem?
Explanation
Correct Answer
Restore the supported systemd-resolved stub integration and configure per-link DNS through the proper owner. This addresses the evidence that resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. Validate the outcome by checking that an internal split-DNS name and an external name both resolve through approved resolvers. Preserve this constraint during the change: Do not expose private internal DNS queries to unapproved public services.
Incorrect Answers
Another possible response is to add the intended route to the correct persistent NetworkManager connection profile and activate safely. The case evidence instead shows that resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. A local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server.
Install the correct scoped next hop or persistent default route after validating gateway reachability. This does not address the reported incident: operators see 127.0.0.53 in /etc/resolv.conf and replace it with a public resolver, breaking split-DNS domains. Resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. The case-specific correction is to restore the supported systemd-resolved stub integration and configure per-link DNS through the proper owner.
One alternative would be to use an approved public endpoint and NAT or gateway architecture while keeping private hosts appropriately protected. The observed evidence instead shows that resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. The more relevant correction is to restore the supported systemd-resolved stub integration and configure per-link DNS through the proper owner.
Question 742
At fictional Lakeshore Analytics, the Linux network operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: Operators see 127.0.0.53 in /etc/resolv.conf and replace it with a public resolver, breaking split-DNS domains. Which observation MOST directly supports the underlying diagnosis before any changes are made?
Explanation
Correct Answer
Resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. The fault is consistent with a local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server. A change targeting the actual dependency is to restore the supported systemd-resolved stub integration and configure per-link DNS through the proper owner.
Incorrect Answers
A competing Linux diagnostic finding for Lakeshore Analytics is: ip route shows the route only during the current session, while nmcli connection data lacks the static route. It does not account for the observation resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes in the reported situation.
At Lakeshore Analytics, another diagnostic finding is: ip route displays only connected routes and no usable default or specific remote route. This would indicate another failure; here resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. A local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server.
At Lakeshore Analytics, a different observation is: The configured address falls in 10.0.0.0/8 and upstream internet routing cannot reach it. It concerns another dependency. This incident is distinguished by resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. A local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server.
Question 743
At fictional Lakeshore Analytics, the Linux network operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: Operators see 127.0.0.53 in /etc/resolv.conf and replace it with a public resolver, breaking split-DNS domains. The proposed intervention is: Restore the supported systemd-resolved stub integration and configure per-link DNS through the proper owner. Which independent result BEST demonstrates a successful correction?
Explanation
Correct Answer
The acceptance evidence is an internal split-DNS name and an external name both resolve through approved resolvers. This checks the intended outcome of restore the supported systemd-resolved stub integration and configure per-link DNS through the proper owner. A local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server.
Incorrect Answers
At Lakeshore Analytics, another acceptance finding might be: After a controlled reboot the route remains and traffic follows the approved next hop. That would still leave the reported failure unproven. An acceptance test must show that an internal split-DNS name and an external name both resolve through approved resolvers.
At Lakeshore Analytics, a different acceptance result would be: A remote test subnet is reachable and local-subnet traffic remains on-link. It may validate a separate setting, but not the required action: restore the supported systemd-resolved stub integration and configure per-link DNS through the proper owner. The required observation is an internal split-DNS name and an external name both resolve through approved resolvers.
The independent acceptance evidence for Lakeshore Analytics is: External authorized clients reach the published service but the private backend remains nonpublic. The evidence relevant to this incident is resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. Confirm the corresponding recovery result: An internal split-DNS name and an external name both resolve through approved resolvers.
Question 744
At fictional Lakeshore Analytics, the Linux network operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: Operators see 127.0.0.53 in /etc/resolv.conf and replace it with a public resolver, breaking split-DNS domains. The relevant evidence is: resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. Which Linux administration principle MOST accurately explains the correct response?
Explanation
Correct Answer
A local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server. This matters because operators see 127.0.0.53 in /etc/resolv.conf and replace it with a public resolver, breaking split-DNS domains. The specific evidence is resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes.
Incorrect Answers
A competing Linux principle for Lakeshore Analytics is: Transient iproute2 commands do not automatically write persistent NetworkManager connection configuration. The decisive observation, resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes, requires a different explanation: A local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server.
A different principle is: the relevant Linux system principle for Lakeshore Analytics is: IP routing tables determine the path to remote addresses independently of DNS resolution. The causal link actually supported by resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes is a local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server.
A competing Linux principle for Lakeshore Analytics is: RFC1918 private ranges are not globally routed on the public internet. However, it does not explain resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. The applicable principle is that a local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server.
Question 745
At fictional Lakeshore Analytics, the Linux network operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: Operators see 127.0.0.53 in /etc/resolv.conf and replace it with a public resolver, breaking split-DNS domains. The decisive evidence is: resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. Which paired action and independent proof BEST satisfies the requirement?
Explanation
Correct Answer
Success requires an internal split-DNS name and an external name both resolve through approved resolvers. That result tests the previously observed condition: resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. A local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server.
Incorrect Answers
Even verifying scoped correction: Add the intended route to the correct persistent NetworkManager connection profile and activate safely. Independent acceptance: After a controlled reboot the route remains and traffic follows the approved next hop leaves the reported failure unproven. An acceptance test must show that an internal split-DNS name and an external name both resolve through approved resolvers.
The alternative outcome is scoped correction: Install the correct scoped next hop or persistent default route after validating gateway reachability. Independent acceptance: A remote test subnet is reachable and local-subnet traffic remains on-link. It may validate a separate setting, but not the required action: restore the supported systemd-resolved stub integration and configure per-link DNS through the proper owner. The required observation is an internal split-DNS name and an external name both resolve through approved resolvers.
Scoped correction: Use an approved public endpoint and NAT or gateway architecture while keeping private hosts appropriately protected. Independent acceptance: External authorized clients reach the published service but the private backend remains nonpublic. The evidence relevant to this incident is resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. Confirm the corresponding recovery result: An internal split-DNS name and an external name both resolve through approved resolvers.
Question 746
At fictional Redridge Insurance, the Linux network operations team is working while investigating an observed production-like support incident. The Linux scenario is: Operators see 127.0.0.53 in /etc/resolv.conf and replace it with a public resolver, breaking split-DNS domains. The diagnostic evidence is: resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. Which bounded step BEST resolves the described problem?
Explanation
Correct Answer
The evidence that resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes points to the need to restore the supported systemd-resolved stub integration and configure per-link DNS through the proper owner. A local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server. Success is measured by an internal split-DNS name and an external name both resolve through approved resolvers. Preserve this constraint during the change: Do not expose private internal DNS queries to unapproved public services.
Incorrect Answers
Add the intended route to the correct persistent NetworkManager connection profile and activate safely. It could be useful for another problem, but it does not change resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. The response needs to restore the supported systemd-resolved stub integration and configure per-link DNS through the proper owner.
An alternative action is install the correct scoped next hop or persistent default route after validating gateway reachability. This incident instead involves resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. Confirm the scoped change through an internal split-DNS name and an external name both resolve through approved resolvers.
Use an approved public endpoint and NAT or gateway architecture while keeping private hosts appropriately protected. That would not correct the reported resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. The supported response is to restore the supported systemd-resolved stub integration and configure per-link DNS through the proper owner.
Question 747
At fictional Redridge Insurance, the Linux network operations team is working while investigating an observed production-like support incident. The Linux scenario is: Operators see 127.0.0.53 in /etc/resolv.conf and replace it with a public resolver, breaking split-DNS domains. Which observation MOST directly supports the underlying diagnosis before any changes are made?
Explanation
Correct Answer
The diagnostic clue is resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. A local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server. The response should therefore focus on restore the supported systemd-resolved stub integration and configure per-link DNS through the proper owner.
Incorrect Answers
A competing Linux diagnostic finding for Redridge Insurance is: ip route shows the route only during the current session, while nmcli connection data lacks the static route. That finding does not isolate the reported issue: operators see 127.0.0.53 in /etc/resolv.conf and replace it with a public resolver, breaking split-DNS domains. The determining evidence is resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes.
At Redridge Insurance, that alternative suggests: ip route displays only connected routes and no usable default or specific remote route. The actual diagnostic record shows resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes instead. The difference matters because a local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server.
At Redridge Insurance, another potential finding is: The configured address falls in 10.0.0.0/8 and upstream internet routing cannot reach it. That would not establish the cause here. Resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. The case-specific correction is to restore the supported systemd-resolved stub integration and configure per-link DNS through the proper owner.
Question 748
At fictional Redridge Insurance, the Linux network operations team is working while investigating an observed production-like support incident. The Linux scenario is: Operators see 127.0.0.53 in /etc/resolv.conf and replace it with a public resolver, breaking split-DNS domains. The proposed intervention is: Restore the supported systemd-resolved stub integration and configure per-link DNS through the proper owner. Which independent result BEST demonstrates a successful correction?
Explanation
Correct Answer
An internal split-DNS name and an external name both resolve through approved resolvers. Without that result, the finding resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes would remain unresolved.
Incorrect Answers
A separate test at Redridge Insurance could show: After a controlled reboot the route remains and traffic follows the approved next hop. That would not demonstrate closure of this condition. The needed proof is an internal split-DNS name and an external name both resolve through approved resolvers.
The independent acceptance evidence for Redridge Insurance is: A remote test subnet is reachable and local-subnet traffic remains on-link. That does not demonstrate the case-specific success condition: an internal split-DNS name and an external name both resolve through approved resolvers. A local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server.
The independent acceptance evidence for Redridge Insurance is: External authorized clients reach the published service but the private backend remains nonpublic. That result does not test the original problem, identified by resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. Recovery must show that an internal split-DNS name and an external name both resolve through approved resolvers.
Question 749
At fictional Redridge Insurance, the Linux network operations team is working while investigating an observed production-like support incident. The Linux scenario is: Operators see 127.0.0.53 in /etc/resolv.conf and replace it with a public resolver, breaking split-DNS domains. The relevant evidence is: resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. Which Linux administration principle MOST accurately explains the correct response?
Explanation
Correct Answer
A local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server. The diagnostic record, resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes, fits that mechanism rather than a separate system issue.
Incorrect Answers
At Redridge Insurance, another Linux system principle is: Transient iproute2 commands do not automatically write persistent NetworkManager connection configuration. The present evidence is resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes, which instead follows from a local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server.
A competing Linux principle for Redridge Insurance is: IP routing tables determine the path to remote addresses independently of DNS resolution. This describes another relationship, not the cause of operators see 127.0.0.53 in /etc/resolv.conf and replace it with a public resolver, breaking split-DNS domains. A local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server.
At Redridge Insurance, a different Linux system principle is: RFC1918 private ranges are not globally routed on the public internet does not account for resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. This case is governed by a local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server.
Question 750
At fictional Redridge Insurance, the Linux network operations team is working while investigating an observed production-like support incident. The Linux scenario is: Operators see 127.0.0.53 in /etc/resolv.conf and replace it with a public resolver, breaking split-DNS domains. The decisive evidence is: resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. Which paired action and independent proof BEST satisfies the requirement?
Explanation
Correct Answer
To close the incident, demonstrate that an internal split-DNS name and an external name both resolve through approved resolvers. That addresses resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes and reflects the rule that a local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server.
Incorrect Answers
A test that scoped correction: Add the intended route to the correct persistent NetworkManager connection profile and activate safely. Independent acceptance: After a controlled reboot the route remains and traffic follows the approved next hop would not demonstrate closure of this condition. The needed proof is an internal split-DNS name and an external name both resolve through approved resolvers.
Scoped correction: Install the correct scoped next hop or persistent default route after validating gateway reachability. Independent acceptance: A remote test subnet is reachable and local-subnet traffic remains on-link. That does not demonstrate the case-specific success condition: an internal split-DNS name and an external name both resolve through approved resolvers. A local DNS stub can forward requests according to per-link policies and is not itself a broken DNS server.
Scoped correction: Use an approved public endpoint and NAT or gateway architecture while keeping private hosts appropriately protected. Independent acceptance: External authorized clients reach the published service but the private backend remains nonpublic. That result does not test the original problem, identified by resolvectl reports healthy per-link internal DNS but clients bypassed its local stub after manual file changes. Recovery must show that an internal split-DNS name and an external name both resolve through approved resolvers.
LPI Level 1 (102-500) Practice Tests
- LPI 102-500 Practice Test 73 - 10 Questions (Last Reviewed 01-Nov-2026)
- LPI 102-500 Practice Test 74 - 10 Questions (Last Reviewed 31-Oct-2026)
- LPI 102-500 Practice Test 75 - 10 Questions (Last Reviewed 30-Oct-2026)
- LPI 102-500 Practice Test 76 - 10 Questions (Last Reviewed 29-Oct-2026)
- LPI 102-500 Practice Test 77 - 10 Questions (Last Reviewed 28-Oct-2026)
