How can quotas be used to enforce per-tenant storage limits?

• A. By assigning quotas to user/group accounts in each SVM, forcing usage to stay within defined limits.
• B. By setting global quotas that apply to all SVMs with a single policy.
• C. By enforcing quotas only on NFS protocol traffic.
• D. By using per-volume quotas that do not consider user accounts.

Answer: (A)

Quotas control how much storage a specific entity can use. In NetApp ONTAP, you define quotas inside an SVM and attach them to a user or group, so each tenant’s usage is tracked under their identity. This means giving a tenant a quota tied to their user/group in each SVM enforces their storage limit, and ONTAP will stop them from writing more once they reach it (hard vs soft limit behavior depending on configuration). Global quotas across all SVMs aren’t how ONTAP applies limits, quotas aren’t restricted to NFS traffic, and per-volume quotas that ignore user identities wouldn’t enforce per-tenant limits.