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 74
Question 730
At fictional Northshore Engineering, the Linux network operations team is working while investigating an observed production-like support incident. The Linux scenario is: A host keeps resolving a retired internal server address despite updated DNS records. The decisive evidence is: /etc/nsswitch.conf checks files before dns and /etc/hosts retains an obsolete entry. Which paired action and independent proof BEST satisfies the requirement?
Explanation
Correct Answer
Getent hosts returns the approved endpoint and a direct DNS query agrees with policy. Without that result, the finding /etc/nsswitch.conf checks files before dns and /etc/hosts retains an obsolete entry would remain unresolved.
Incorrect Answers
A test that scoped correction: Apply the approved CIDR prefix consistently and verify routing for nonlocal addresses. Independent acceptance: Hosts on the intended subnet communicate directly and external destinations use the gateway would not demonstrate closure of this condition. The needed proof is getent hosts returns the approved endpoint and a direct DNS query agrees with policy.
Scoped correction: Activate the correct approved profile and disable or prioritize conflicting profiles appropriately. Independent acceptance: The interface reports the intended address on reconnect and an authorized service remains reachable. That does not demonstrate the case-specific success condition: getent hosts returns the approved endpoint and a direct DNS query agrees with policy. Name service switch order controls which name sources are consulted before DNS.
Scoped correction: Calculate the correct network prefix and allocate an address within the approved subnet, with a matching gateway. Independent acceptance: Two endpoints in the same intended prefix communicate and the host route table shows the expected subnet. That result does not test the original problem, identified by /etc/nsswitch.conf checks files before dns and /etc/hosts retains an obsolete entry. Recovery must show that getent hosts returns the approved endpoint and a direct DNS query agrees with policy.
Question 731
At fictional Meadowcrest Energy, the Linux network operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: A troubleshooting script sees a valid dig response but applications still report an unknown hostname. The diagnostic evidence is: dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. Which bounded step BEST resolves the described problem?
Explanation
Correct Answer
The case reveals dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. That matters because direct DNS queries and system library hostname resolution may take different paths. The corrective step is to compare dig, getent and effective nsswitch sources; fix the actual NSS or resolver configuration. Preserve this constraint during the change: Do not assume a successful dig query proves a specific application's resolver behavior.
Incorrect Answers
Another possible response is to permit the required approved DNS transport paths and validate both UDP and TCP resolution behavior. The case evidence instead shows that dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. Direct DNS queries and system library hostname resolution may take different paths.
Select one intended network configuration manager for that interface and remove the conflicting configuration. This does not address the reported incident: a troubleshooting script sees a valid dig response but applications still report an unknown hostname. Dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. The case-specific correction is to compare dig, getent and effective nsswitch sources; fix the actual NSS or resolver configuration.
One alternative would be to configure the approved transport protocol and port combination needed for the service. The observed evidence instead shows that dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. The more relevant correction is to compare dig, getent and effective nsswitch sources; fix the actual NSS or resolver configuration.
Question 732
At fictional Meadowcrest Energy, the Linux network operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: A troubleshooting script sees a valid dig response but applications still report an unknown hostname. Which observation MOST directly supports the underlying diagnosis before any changes are made?
Explanation
Correct Answer
Dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. It identifies the problem behind a troubleshooting script sees a valid dig response but applications still report an unknown hostname. Direct DNS queries and system library hostname resolution may take different paths.
Incorrect Answers
A competing Linux diagnostic finding for Meadowcrest Energy is: Diagnostics show UDP port 53 access is permitted while required large responses fall back to TCP and TCP 53 is blocked. It does not account for the observation dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration in the reported situation.
At Meadowcrest Energy, another diagnostic finding is: Service state and configuration files show overlapping ownership of the interface. This would indicate another failure; here dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. Direct DNS queries and system library hostname resolution may take different paths.
At Meadowcrest Energy, a different observation is: Packet inspection shows TCP SYN packets blocked while only a UDP 443 rule exists. It concerns another dependency. This incident is distinguished by dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. Direct DNS queries and system library hostname resolution may take different paths.
Question 733
At fictional Meadowcrest Energy, the Linux network operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: A troubleshooting script sees a valid dig response but applications still report an unknown hostname. The proposed intervention is: Compare dig, getent and effective nsswitch sources; fix the actual NSS or resolver configuration. Which independent result BEST demonstrates a successful correction?
Explanation
Correct Answer
Success requires the application's standard name lookup and an appropriate DNS check both resolve the expected host. That result tests the previously observed condition: dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. Direct DNS queries and system library hostname resolution may take different paths.
Incorrect Answers
At Meadowcrest Energy, another acceptance finding might be: A standard and a larger DNS response succeed through the intended IPv6 resolver. That would still leave the reported failure unproven. An acceptance test must show that the application's standard name lookup and an appropriate DNS check both resolve the expected host.
At Meadowcrest Energy, a different acceptance result would be: After two controlled reboots the interface keeps one consistent address, route and DNS configuration. It may validate a separate setting, but not the required action: compare dig, getent and effective nsswitch sources; fix the actual NSS or resolver configuration. The required observation is the application's standard name lookup and an appropriate DNS check both resolve the expected host.
The independent acceptance evidence for Meadowcrest Energy is: An authorized TCP connection to the service establishes while unrelated ports remain closed. The evidence relevant to this incident is dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. Confirm the corresponding recovery result: The application's standard name lookup and an appropriate DNS check both resolve the expected host.
Question 734
At fictional Meadowcrest Energy, the Linux network operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: A troubleshooting script sees a valid dig response but applications still report an unknown hostname. The relevant evidence is: dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. Which Linux administration principle MOST accurately explains the correct response?
Explanation
Correct Answer
The governing distinction is that direct DNS queries and system library hostname resolution may take different paths. Here, dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. Compare dig, getent and effective nsswitch sources; fix the actual NSS or resolver configuration.
Incorrect Answers
A competing Linux principle for Meadowcrest Energy is: DNS can use both UDP and TCP on port 53; IPv6 changes addressing but not that general requirement. The decisive observation, dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration, requires a different explanation: Direct DNS queries and system library hostname resolution may take different paths.
A different principle is: the relevant Linux system principle for Meadowcrest Energy is: Persistent network configuration needs a clear owning daemon per interface. The causal link actually supported by dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration is direct DNS queries and system library hostname resolution may take different paths.
A competing Linux principle for Meadowcrest Energy is: TCP and UDP use separate transport protocol namespaces even when port numbers match. However, it does not explain dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. The applicable principle is that direct DNS queries and system library hostname resolution may take different paths.
Question 735
At fictional Meadowcrest Energy, the Linux network operations team is working during a controlled system-configuration acceptance test. 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
Verify the change by checking that the application's standard name lookup and an appropriate DNS check both resolve the expected host. The original clue was dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. The test is meaningful because direct DNS queries and system library hostname resolution may take different paths.
Incorrect Answers
Even verifying 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 leaves the reported failure unproven. An acceptance test must show that the application's standard name lookup and an appropriate DNS check both resolve the expected host.
The alternative outcome is 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. It may validate a separate setting, but not the required action: compare dig, getent and effective nsswitch sources; fix the actual NSS or resolver configuration. The required observation is the application's standard name lookup and an appropriate DNS check both resolve the expected host.
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. The evidence relevant to this incident is dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. Confirm the corresponding recovery result: The application's standard name lookup and an appropriate DNS check both resolve the expected host.
Question 736
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 diagnostic evidence is: dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. Which bounded step BEST resolves the described problem?
Explanation
Correct Answer
Dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. Instead of unrelated changes, compare dig, getent and effective nsswitch sources; fix the actual NSS or resolver configuration. The expected result is the application's standard name lookup and an appropriate DNS check both resolve the expected host. Preserve this constraint during the change: Do not assume a successful dig query proves a specific application's resolver behavior.
Incorrect Answers
Permit the required approved DNS transport paths and validate both UDP and TCP resolution behavior. It could be useful for another problem, but it does not change dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. The response needs to compare dig, getent and effective nsswitch sources; fix the actual NSS or resolver configuration.
An alternative action is select one intended network configuration manager for that interface and remove the conflicting configuration. This incident instead involves dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. Confirm the scoped change through the application's standard name lookup and an appropriate DNS check both resolve the expected host.
Configure the approved transport protocol and port combination needed for the service. That would not correct the reported dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. The supported response is to compare dig, getent and effective nsswitch sources; fix the actual NSS or resolver configuration.
Question 737
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. Which observation MOST directly supports the underlying diagnosis before any changes are made?
Explanation
Correct Answer
Look for the recorded condition: Dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. That is decisive because direct DNS queries and system library hostname resolution may take different paths. Correction should target compare dig, getent and effective nsswitch sources; fix the actual NSS or resolver configuration.
Incorrect Answers
A competing Linux diagnostic finding for Clearwater Logistics is: Diagnostics show UDP port 53 access is permitted while required large responses fall back to TCP and TCP 53 is blocked. That finding does not isolate the reported issue: a troubleshooting script sees a valid dig response but applications still report an unknown hostname. The determining evidence is dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration.
At Clearwater Logistics, that alternative suggests: Service state and configuration files show overlapping ownership of the interface. The actual diagnostic record shows dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration instead. The difference matters because direct DNS queries and system library hostname resolution may take different paths.
At Clearwater Logistics, another potential finding is: Packet inspection shows TCP SYN packets blocked while only a UDP 443 rule exists. That would not establish the cause here. Dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. The case-specific correction is to compare dig, getent and effective nsswitch sources; fix the actual NSS or resolver configuration.
Question 738
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 proposed intervention is: Compare dig, getent and effective nsswitch sources; fix the actual NSS or resolver configuration. Which independent result BEST demonstrates a successful correction?
Explanation
Correct Answer
To close the incident, demonstrate that the application's standard name lookup and an appropriate DNS check both resolve the expected host. That addresses dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration and reflects the rule that direct DNS queries and system library hostname resolution may take different paths.
Incorrect Answers
A separate test at Clearwater Logistics could show: A standard and a larger DNS response succeed through the intended IPv6 resolver. That 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.
The independent acceptance evidence for Clearwater Logistics is: 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.
The independent acceptance evidence for Clearwater Logistics is: 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 739
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 relevant evidence is: dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. Which Linux administration principle MOST accurately explains the correct response?
Explanation
Correct Answer
Direct DNS queries and system library hostname resolution may take different paths. That explains the observed condition: dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. The scoped response is to compare dig, getent and effective nsswitch sources; fix the actual NSS or resolver configuration.
Incorrect Answers
At Clearwater Logistics, another Linux system principle is: DNS can use both UDP and TCP on port 53; IPv6 changes addressing but not that general requirement. The present evidence is dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration, which instead follows from direct DNS queries and system library hostname resolution may take different paths.
A competing Linux principle for Clearwater Logistics is: Persistent network configuration needs a clear owning daemon per interface. This describes another relationship, not the cause of a troubleshooting script sees a valid dig response but applications still report an unknown hostname. Direct DNS queries and system library hostname resolution may take different paths.
At Clearwater Logistics, a different Linux system principle is: TCP and UDP use separate transport protocol namespaces even when port numbers match does not account for dig queries DNS directly while getent hosts follows NSS rules and local resolution configuration. This case is governed by direct DNS queries and system library hostname resolution may take different paths.
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.
LPI Level 1 (102-500) Practice Tests
- LPI 102-500 Practice Test 72 - 10 Questions (Last Reviewed 02-Nov-2026)
- 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)
