Question 670
A Linux administrator evaluates: A Linux application times out only after an expired intermediate certificate breaks its secure API connection. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (A Linux application times out only after an expired intermediate certificate breaks its secure API connection), the acceptance evidence is: The approved client authenticates to the verified host with a valid key or certificate and rejects an untrusted identity. This verifies the action (Differentiate SSH host key verification, user authorized-key permissions and TLS endpoint certificate errors using targeted client and server evidence.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Disabling strict host checks or accepting unknown certificates during an incident can mask a man-in-the-middle attack.
The observed Linux condition is: A Linux application times out only after an expired intermediate certificate breaks its secure API connection. The recommended direct administrative response is: Differentiate SSH host key verification, user authorized-key permissions and TLS endpoint certificate errors using targeted client and server evidence. The relevant failure or security risk is: Disabling strict host checks or accepting unknown certificates during an incident can mask a man-in-the-middle attack. Validate success with: The approved client authenticates to the verified host with a valid key or certificate and rejects an untrusted identity.
Incorrect Answers
Listener and firewall differentiation on Linux (5.3) would demonstrate or implement: Opening a port cannot help if the daemon only binds loopback or is stopped, and a listening socket alone cannot prove external access. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: The approved client authenticates to the verified host with a valid key or certificate and rejects an untrusted identity.
Memory pressure OOM killer and swapping (5.5) addresses another technical failure: Treating file cache as unavailable RAM or blindly disabling swap can obscure the application responsible for OOM kills. This case instead tests SSH key and certificate failure diagnosis; the choice measures or changes another part of the system.
DNS versus connectivity diagnostic sequence (5.3) would demonstrate or implement: The intended domain resolves through the approved resolver and the client reaches the same service by its hostname. The required paired action and test concerns SSH key and certificate failure diagnosis; a passing result for this alternative could leave that requirement unresolved.