If you are talking about masking the "real" name/location of an SMB share on a NetApp by using a DFS target defined in Active Directory, that can be done successfully. The main problems I encountered with that approach usually revolved around "weird" old SMBv1 clients (like a multifunction printer/scanner that scans a document and ships it to the SMB share). Also, there were sometimes issues with various flavors of Apple OS, but typically by mapping with cifs://my.dfs.example.com/share/sharename instead of smb://, that got it working. My understanding is that cifs:// forces the Mac OS to autonegotiate down to SMBv1, which apparently is less problematic.
But the vast majority of clients, both Windows and Macs, worked just fine with a AD-based DFS target to a NetApp SMB share.
Yes we can. Once DFS is installed on an NT server, using the DFS Administrator tool, you need to make entries for the filer's Common Internet File System protocol (CIFS) shares in the DFS root tree. Refer the following Kb for more details.