Question 660
At Northgate Telecom, the Linux platform reliability team maintains multi-region Linux gateways and monitoring servers under requirements for stable network connectivity and verified change records. The acceptance reviewer must validate: A Linux service administrator cannot connect over SSH after a hardening change because sshd was configured with an invalid directive. Which observed result BEST demonstrates that the correction works?
Explanation
Correct Answer
The daemon starts with the corrected policy and an allowed key-based login works while disallowed methods remain blocked. This measurable outcome verifies correction of: A Linux service administrator cannot connect over SSH after a hardening change because sshd was configured with an invalid directive. The associated technical action is: Validate the SSH daemon configuration with the supported syntax check and repair the erroneous directive using a recovery session. The Northgate Telecom review checks actual behavior rather than an untested change claim.
Incorrect Answers
The device-level errors are addressed and a verified read-write mount accepts controlled writes without new I/O faults. This evidence pertains to an unrelated remediation: Inspect kernel and storage error logs, assess the underlying device health and perform a backed-up supported filesystem recovery. The alternative issue is: A database filesystem suddenly becomes read-only after repeated I/O errors, but the administrator tries to fix it with chmod. The current Northgate Telecom problem is: A Linux service administrator cannot connect over SSH after a hardening change because sshd was configured with an invalid directive. The decisive expected evidence is instead: The daemon starts with the corrected policy and an allowed key-based login works while disallowed methods remain blocked.
A representative load stays within the intended memory limit and no new OOM kill occurs during the test window. This evidence pertains to an unrelated remediation: Inspect free and process RSS/cgroup memory metrics and OOM logs, then correct the identified process or memory limit. The alternative issue is: A service uses excessive memory and the kernel begins killing processes, while the incident handler misreads cached pages as unreclaimable application RAM. The current Northgate Telecom problem is: A Linux service administrator cannot connect over SSH after a hardening change because sshd was configured with an invalid directive. The decisive expected evidence is instead: The daemon starts with the corrected policy and an allowed key-based login works while disallowed methods remain blocked.
The approved subnet connects and a separate untrusted client still cannot reach the service port. This evidence pertains to an unrelated remediation: Review the active firewall rules and add a narrowly scoped service/source allow rule under the configured filtering backend. The alternative issue is: A Linux host shows its web service listening but its local firewall silently drops permitted inbound requests from the business subnet. The current Northgate Telecom problem is: A Linux service administrator cannot connect over SSH after a hardening change because sshd was configured with an invalid directive. The decisive expected evidence is instead: The daemon starts with the corrected policy and an allowed key-based login works while disallowed methods remain blocked.