Exam SY0-601 topic 1 question 351 discussion

The most likely cause of the issue is that SSH was turned off instead of modifying the configuration file. SSH (Secure Shell) is a commonly used protocol for securely accessing and managing remote systems, including network-attached storage (NAS) devices. Disabling remote logins to the NAS would most likely involve modifying the configuration file for the SSH service (sshd.conf), not disabling SSH itself. If SSH was turned off, it would prevent users from accessing the NAS over the network, including using SCP (Secure Copy Protocol) to transfer files. This would result in the inability to use SCP to transfer files to the NAS, even though the data is still viewable from the users’ PCs.

SCP uses SSH port 22. Turn it off and its rip.

SSH. Secure Shell (SSH) encrypts traffic in transit and can be used to encrypt other protocols such as FTP. Secure Copy (SCP) is based on SSH and is used to copy encrypted files over a network. SSH can also encrypt TCP Wrappers, a type of access control list used on Linux systems to filter traffic. When SSH encrypts traffic, it uses TCP port 22.

if they can use SCP (Secure Copy) which is through the 22 port the SSH must has been disabled

This info extracted from perplexity AI, I’m convinced with explanation to the clarifying points. Hope this may helps others. SSH was turned off instead of modifying the configuration file. Disabling remote logins to the NAS by turning off SSH would prevent users from using SCP (Secure Copy Protocol) to transfer files to the NAS SCP relies on SSH for secure file transfer, so if SSH is turned off, SCP will not work. However, even if SSH is disabled, users may still be able to view the data on the NAS from their PCs because other protocols or services may be enabled for file access, such as SMB (Server Message Block) or NFS (Network File System)

The most likely cause of the issue described in the scenario is option B: SSH was turned off instead of modifying the configuration file. Secure Shell (SSH) is a network protocol that provides secure remote access to systems and enables secure file transfers using protocols such as SCP (Secure Copy). By disabling remote logins to the NAS without properly configuring the system, including SSH, it is possible that the SSH service was turned off entirely instead of modifying the configuration file to restrict remote access. As a result, users are unable to use SCP to transfer files to the NAS because the SSH service, which SCP relies on, is not running. However, the data on the NAS can still be viewed from the users' PCs because accessing the data locally does not require remote logins or SSH.

Believe it's C. It wouldn't be B as the question states it's viewable. If they didn't say this, then it would have been B.

SSH is used to securely transfer files to the remote server and is required for SCP to work. Disabling SSH will prevent users from being able to use SCP to transfer files to the server. To enable SSH, the security engineer should modify the SSH configuration file (sshd.conf) and make sure that SSH is enabled.

SCP uses SSH. So, if SCP can no longer be used, that must mean SSH was turned off. Answer is B.

Having reviewed the documemtation of networkd.conf, I don't think there are any setting there for enabling/disabling remote login. Please, correct me if I'm wrong.

I think people are missing the point of the question. the question indicates NAS data are still "viewable" yet SCP is not working which means SSH is not completely off if data is viewable. this is something that has to do with the configuration of files relating to the RA. remote logins can be enabled or disabled using sshd.config file using the following commands PermitRootLogin yes #enabled. PermitRootLogin no #disabled. therefore, the only logical answer is C

"disabling remote logins" Engineer just disabled SSH. SCP uses port 22 which is the same as SSH. Hence the reason why users were unable to use that protocol.

I think its B, ssh was turned off. SCP utilizes ssh for authentication and encryption of the connection. Without ssh, users will not be able to transfer the files.

I think the answer here is C.

I think this is C. If SSH was the issue, it would all stop working, not just the file transfers.

C. Remote Login was disabled in the networkd.config instead of using the sshd.conf