Which export policy rule modification will resolve this issue?

An administrator is troubleshooting a Cloud Data Sense deep scan that failed on a Cloud Volumes ONTAP (CVO) NFS export. The scan worked a day ago with no errors. The administrator notices that the NFS export is on a volume with a recently modified export policy rule.

Which export policy rule modification will resolve this issue?
A . superuser
B . krb
C . read
D . anon

View Answer

Answer: C

Explanation:

If a Cloud Data Sense deep scan of an NFS export fails after a recent modification to the export policy rule, the most critical setting to check and adjust is the read permission. Here’s how to resolve the issue:

Review the Modified Export Policy: Access the export policy settings for the NFS volume that Cloud Data Sense is attempting to scan. Check for recent changes that might have restricted read access. Modify Export Policy to Allow Read Access: Ensure that the export policy rule specifically permits read access. This permission is essential for Cloud Data Sense to read the data stored on the NFS export and perform the scan effectively.

Apply Changes and Re-test the Scan: After adjusting the export policy to ensure read access, re-run the Cloud Data Sense scan to confirm that the issue is resolved and that the scan completes successfully.

For detailed instructions on configuring NFS export policies in Cloud Volumes ONTAP, consult the NetApp documentation: NetApp NFS Export Policy Documentation.