NS0-157 · Question #420
You have created a storage virtual machine named SVM1 with a NetBIOS name of FILES1 and you have successfully joined the Active Directory domain. You have created a CIFS share called SHARE1 and have…
The correct answer is B. \\FILES1\SHARE1. When mapping to a CIFS/SMB share on a NetApp SVM, users connect using the SVM's NetBIOS name as the server component and the share name as the second component of the UNC path.
Question
You have created a storage virtual machine named SVM1 with a NetBIOS name of FILES1 and you have successfully joined the Active Directory domain. You have created a CIFS share called SHARE1 and have given read/write access to all users. Network connectivity has been verified. To which path should the users be mapping?
Options
- A\SHARE1\FILES1
- B\FILES1\SHARE1
- C\SVM1\FILES1
- D\FILES1\SVM1
How the community answered
(26 responses)- B88% (23)
- C8% (2)
- D4% (1)
Why each option
When mapping to a CIFS/SMB share on a NetApp SVM, users connect using the SVM's NetBIOS name as the server component and the share name as the second component of the UNC path.
This reverses the UNC path components, placing the share name before the server name, which is not valid SMB syntax.
The UNC path format for SMB is \\server\share, where the server is identified by its NetBIOS name as registered in Active Directory. FILES1 is the NetBIOS name assigned to SVM1 during CIFS configuration, and SHARE1 is the defined share, so \\FILES1\SHARE1 is the correct path clients use to access the share.
SVM1 is the internal administrative name of the storage virtual machine, not the NetBIOS name registered in AD - users cannot resolve or connect using the SVM admin name directly.
SVM1 is the administrative SVM name, not the share name or the resolvable NetBIOS name, making this path both structurally incorrect and unresolvable on the network.
Concept tested: NetApp CIFS share UNC path using NetBIOS name
Source: https://docs.netapp.com/us-en/ontap/smb-admin/configure-ntfs-windows-security-tab-task.html
Topics
Community Discussion
No community discussion yet for this question.