Question 610
A Linux administrator evaluates: An application resolves the correct public address but should use a private hosts override for its approved service. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (An application resolves the correct public address but should use a private hosts override for its approved service), the acceptance evidence is: The intended domain resolves through the approved resolver and the client reaches the same service by its hostname. This verifies the action (Test numeric-IP reachability, local resolver configuration and DNS answers separately with getent, dig and suitable connection tools.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: A working route to a server cannot compensate for a stale hosts entry or unresponsive name server.
The observed Linux condition is: An application resolves the correct public address but should use a private hosts override for its approved service. The recommended direct administrative response is: Test numeric-IP reachability, local resolver configuration and DNS answers separately with getent, dig and suitable connection tools. The relevant failure or security risk is: A working route to a server cannot compensate for a stale hosts entry or unresponsive name server. Validate success with: The intended domain resolves through the approved resolver and the client reaches the same service by its hostname.
Incorrect Answers
SELinux denial versus traditional permission fault (5.4) addresses another technical failure: Turning SELinux off or using chmod 777 cannot reliably solve a labeling issue and can weaken host security. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: The intended domain resolves through the approved resolver and the client reaches the same service by its hostname.
SSH key and certificate failure diagnosis (5.4) would demonstrate or implement: Disabling strict host checks or accepting unknown certificates during an incident can mask a man-in-the-middle attack. This choice can be useful for that problem, but it does not establish the DNS versus connectivity diagnostic sequence control being assessed here.
Disk IO wait and throughput bottleneck diagnosis (5.5) would demonstrate or implement: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors. The required paired action and test concerns DNS versus connectivity diagnostic sequence; a passing result for this alternative could leave that requirement unresolved.