Which step is specifically required to map AD identities to ONTAP permissions?

Which step is specifically required to map AD identities to ONTAP permissions?

• A. Enable Kerberos
• B. Join the SVM to the AD domain
• C. Configure user/group mapping
• D. Assign RBAC

Answer: (C)

Mapping AD identities to ONTAP permissions is about translating Active Directory users and groups into ONTAP identities that carry defined privileges. ONTAP makes authorization decisions based on its own understood identities and the RBAC roles attached to them. Without a clear mapping, an AD user who authenticates cannot be linked to a specific ONTAP account and therefore cannot be granted the appropriate access rights. Configuring how users and groups from AD correspond to ONTAP users or roles establishes this bridge, enabling precise permission control. Enabling Kerberos is an authentication method, which can help with securely verifying identities but does not establish how those identities map to ONTAP accounts. Joining the AD domain lets ONTAP recognize AD principals, but the explicit mapping step is what ties those principals to concrete ONTAP identities and their permissions. Assigning RBAC relies on having a mapped identity to attach the proper privileges to; the mapping step is what makes that possible in the first place.

Mapping AD identities to ONTAP permissions is about translating Active Directory users and groups into ONTAP identities that carry defined privileges. ONTAP makes authorization decisions based on its own understood identities and the RBAC roles attached to them. Without a clear mapping, an AD user who authenticates cannot be linked to a specific ONTAP account and therefore cannot be granted the appropriate access rights. Configuring how users and groups from AD correspond to ONTAP users or roles establishes this bridge, enabling precise permission control.

Enabling Kerberos is an authentication method, which can help with securely verifying identities but does not establish how those identities map to ONTAP accounts. Joining the AD domain lets ONTAP recognize AD principals, but the explicit mapping step is what ties those principals to concrete ONTAP identities and their permissions. Assigning RBAC relies on having a mapped identity to attach the proper privileges to; the mapping step is what makes that possible in the first place.