Which step is NOT part of configuring a Windows SMB share on ONTAP?

Which step is NOT part of configuring a Windows SMB share on ONTAP?

• A. Enable SMB on the SVM.
• B. Create a Windows share (CIFS) on a volume.
• C. Assign permissions and integrate with AD if required.
• D. Enable SMB on the SVM and configure an NFS export.

Answer: (D)

Setting up a Windows SMB share on ONTAP involves enabling the SMB service on the SVM, creating a Windows share (CIFS) on a volume, and controlling access with permissions, optionally integrated with Active Directory for authentication. Enabling SMB on the SVM is necessary so that SMB clients can connect to the Share Virtual Server. Creating the actual share on a volume defines the path that Windows clients will access. Assigning permissions and AD integration ensure that only authorized users can access the share and with the appropriate rights. The step that would not be part of configuring a Windows SMB share is configuring an NFS export, since NFS is a separate protocol used for UNIX/Linux clients and has its own export settings. While ONTAP can support both protocols, the NFS export configuration belongs to NFS shares, not SMB shares.

Setting up a Windows SMB share on ONTAP involves enabling the SMB service on the SVM, creating a Windows share (CIFS) on a volume, and controlling access with permissions, optionally integrated with Active Directory for authentication. Enabling SMB on the SVM is necessary so that SMB clients can connect to the Share Virtual Server. Creating the actual share on a volume defines the path that Windows clients will access. Assigning permissions and AD integration ensure that only authorized users can access the share and with the appropriate rights. The step that would not be part of configuring a Windows SMB share is configuring an NFS export, since NFS is a separate protocol used for UNIX/Linux clients and has its own export settings. While ONTAP can support both protocols, the NFS export configuration belongs to NFS shares, not SMB shares.