You can find this information out using Get-NaCommand with the ListAvailable switch. This compares the API from the help documentation with the APIs available on the controller to determine if a command can be executed. For example:
PS> Get-NaCommand -Category cifs -Verb Get, Set -ListAvailable
Name Category Api
---- -------- ---
Get-NaCifs cifs {cifs-list-config}
Get-NaCifsHomeDirectory cifs {cifs-homedir-paths-get, cifs-homedir-path-get-for-user}
Get-NaCifsNetBiosAlias cifs {cifs-nbalias-names-get}
Get-NaCifsOrganizationalUnit cifs {cifs-setup-ou-list-iter-start, cifs-setup-ou-list-iter-next, ci...
Get-NaCifsSession cifs {cifs-session-list-iter-start, cifs-session-list-iter-next, cifs...
Get-NaCifsShare cifs {cifs-share-list-iter-start, cifs-share-list-iter-next, cifs-sha...
Get-NaCifsSite cifs {cifs-setup-site-list-iter-start, cifs-setup-site-list-iter-next...
Get-NaCifsStatistics cifs {cifs-top-iter-start, cifs-top-iter-next, cifs-top-iter-end}
Set-NaCifs cifs {cifs-setup}
Set-NaCifsHomeDirectory cifs {cifs-homedir-paths-set}
Set-NaCifsNetBiosAlias cifs {cifs-nbalias-names-set}
Set-NaCifsShare cifs {cifs-share-change}
Conversely, you can use ListUnavailable to see cmdlets that exist but cannot be run on the current controller:
PS> Get-NaCommand -Category cifs -Verb Get, Set -ListUnavailable
Name Category Api
---- -------- ---
Get-NaCifsBranchCacheHashStatistics cifs {cifs-branchcache-hash-stat}
Get-NaCifsShareAcl cifs {cifs-share-acl-list-iter-start, cifs-share-acl-list-iter-next, ...
Set-NaCifsBranchCacheKey cifs {cifs-branchcache-set-key}
Set-NaCifsShareAcl cifs {cifs-share-ace-set}
-Steven