You are configuring NFS on a server. Select the two statements that are true.

Question

Options

• AResources listed in /etc/dfs/dfstab are automatically shared on boot up.
• BA directory cannot be shared if a subdirectory below it is already shared.
• CRenaming a share created with the zfs set share command is not supported.
• DNFS and SMB protocols cannot be used simultaneously to share the same directory.

• A
  8% (3)
• B
  74% (29)
• D
  18% (7)

Explanation

B is correct because Solaris NFS enforces a no-nested-export rule: if a subdirectory is already shared, its parent directory cannot also be shared, preventing overlapping export namespaces. C is correct because shares created via zfs set share are bound to the ZFS dataset's properties - renaming the share independently is not supported; you must destroy and recreate it.

A is a distractor because while /etc/dfs/dfstab is read by the shareall command, this file is legacy (deprecated in Solaris 11) and shares are not guaranteed to activate automatically at boot without the NFS server SMF service being explicitly enabled and configured. D is a distractor because Solaris does support multiprotocol sharing - the same directory can be exported over both NFS and SMB (CIFS) simultaneously using sharemgr or ZFS share properties.

Memory tip: For B, think "children go first, parents can't follow" - a parent directory is blocked once a child is already shared. For C, think "ZFS owns the name" - ZFS-managed shares are tied to the dataset and can't be freely renamed.

No community discussion yet for this question.