300-300 · Question #87
What is the purpose of the smbclient command scopy? (Choose two.)
The correct answer is C. It copies a file from one remote share to another remote share on the same SMB server. D. It creates a copy of an existing file on the connected SMB share.. scopy is an smbclient subcommand that performs a server-side copy operation, meaning it instructs the remote SMB server to duplicate a file. C is correct because scopy can copy a file from one share to another share hosted on the same SMB server. D is correct because at its most
Question
Options
- AIf server functionality is available, the affected file is not transferred over the network.
- BIt copies a file on the local file system and does not change the content of the connected SMB
- CIt copies a file from one remote share to another remote share on the same SMB server.
- DIt creates a copy of an existing file on the connected SMB share.
- EIf the SMB server supports shadow file systems, a copy-on-write link is created instead of a real
How the community answered
(39 responses)- A5% (2)
- B3% (1)
- C90% (35)
- E3% (1)
Explanation
scopy is an smbclient subcommand that performs a server-side copy operation, meaning it instructs the remote SMB server to duplicate a file. C is correct because scopy can copy a file from one share to another share hosted on the same SMB server. D is correct because at its most basic, it creates a copy of a file that already exists on the connected SMB share - the file is duplicated on the server side.
A is wrong because while some SMB server-side copy implementations do avoid sending data over the network, that describes an optional implementation detail of the protocol, not the stated purpose of scopy itself. B is wrong because scopy operates entirely on the remote SMB server, not the local file system. E is wrong because copy-on-write or shadow filesystem links are not what scopy creates - that conflates SMB server-side copy with Linux VFS concepts like reflinks.
Memory tip: Think of scopy as "server copy" - both the source and destination live on the server, not your local machine. If you remember that the operation happens entirely on the remote side (D) and can span shares on that same server (C), you can immediately eliminate anything mentioning local files (B) or local filesystem features.
Topics
Community Discussion
No community discussion yet for this question.