NS0-161 practice question 10 of 15

Your customer has an NTFS volume that they want to access over both SMB and NFS. The client explains that SMB access works fine, but the clients are unable to NFS mount the volume. What are three reasons that would cause this issue? (Choose three.)

Full set: 60 questions
Answer options
A: There is no export-policy rule for the NFS clients. Correct answer
B: The NSF server is not configured. Correct answer
C: Multi-protocol is not licensed on the cluster.
D: The volume security style must be changed to UNIX.
E: The LIF data protocol does not allow NFS. Correct answer
Correct Answer:
A. There is no export-policy rule for the NFS clients.; B. The NSF server is not configured.; E. The LIF data protocol does not allow NFS.
Explanation

For an NFS client to mount a volume on a NetApp ONTAP system, three primary configuration layers must be correctly set up, especially in a multi-protocol environment where SMB is already functional.
1. NFS Service: The NFS protocol service must be enabled and running on the Storage Virtual Machine (SVM). If the NFS server is not configured or is stopped, all NFS requests will fail.
2. Network Path (LIF): The Logical Interface (LIF) that the NFS client is using to connect must be configured to allow the NFS protocol. A LIF can be restricted to specific protocols (e.g., cifs only).
3. Access Control (Export Policy): The volume must have an export policy attached, and that policy must contain a rule that grants the specific NFS client (or its subnet) the necessary access permissions (e.g., read-write, read-only) to mount the volume. Failure in any of these three distinct areas will prevent an NFS mount, even if other protocols like SMB are working correctly.

Why Incorrect

C. Multi-protocol is not licensed on the cluster. This phrasing is inaccurate. ONTAP does not have a single "multi-protocol" license. Protocols like NFS and CIFS are licensed individually. A missing NFS license would indeed cause this issue, but it manifests as the NFS server failing to start (Option B), making B a more direct answer.
D. The volume security style must be changed to UNIX. This is incorrect. ONTAP is designed for multi-protocol access and fully supports NFS clients accessing volumes with the NTFS security style. Changing the style to UNIX would break the existing, functional SMB access for Windows clients.

References

1. NetApp ONTAP 9.8 Documentation, "Create an NFS server on an SVM": "You must create and start an NFS server on the storage virtual machine (SVM) to allow NFS clients to access data on the SVM." This supports option B.

2. NetApp ONTAP 9.8 Documentation, "Create a data LIF": The network interface create command documentation specifies the -data-protocols parameter, stating, "You must specify the data protocols that the LIF will support. The supported protocols are nfs, cifs...". This supports option E.

3. NetApp ONTAP 9.8 Documentation, "How export policies work": "An export policy is a set of export rules that specifies access permissions to volumes... When an NFS client attempts to access a volume, ONTAP checks for a matching export rule in the export policy for that volume to determine which access rights to grant the client." This supports option A.

4. NetApp ONTAP 9.8 Documentation, "Considerations for choosing a security style": "NTFS security style... You can also configure this volume for multiprotocol access." This directly refutes option D.

Scroll to Top