File Analytics is a centralized service that is deployed and managed through Nutanix Prism Central. To perform the initial deployment of the File Analytics virtual appliance, the user must have the highest level of permissions within the Prism Central environment. The built-in Prism Admin role, commonly referred to as the Prism Central administrator, is the only role with the necessary privileges to install and configure new services like File Analytics. This role grants unrestricted access to all features and settings within Prism Central, which is a prerequisite for the deployment workflow.

B. AD user mapped to a Prism admin role: While this user would have the necessary permissions, this option describes a specific implementation (an AD user) of the required role. Option A is the more fundamental and encompassing answer, as it defines the role itself.

C. Prism Element administrator: This role is scoped to a specific Nutanix cluster managed by Prism Element. It does not have the required permissions to deploy or manage services at the Prism Central level.

D. AD user mapped to a Cluster admin role: Similar to a Prism Element administrator, this user's permissions are limited to a specific cluster. They cannot perform administrative actions, such as deploying services, within Prism Central.

1. Nutanix File Analytics Deployment and User Guide v4.2

Chapter: Prerequisites

Page 10: "Log on to Prism Central with a user account that has the Prism Admin role." This statement explicitly requires the Prism Admin role for deployment.

2. Nutanix Security Guide v6.5

Chapter: Built-in Role Management

Section: Prism Admin

Page 101: "Prism Admin: Has full access to all entities and features in Prism Central. Can create

read

update

and delete all entities. Can also perform administrative tasks such as adding users

creating roles

and so on." This defines the scope of the Prism Central administrator role

confirming it has the authority to install new features.

3. Prism Central Guide v6.5

Chapter: Role-Based Access Control

Section: Built-in Roles

Page 218: This section details the permissions for built-in roles

distinguishing between the Prism Admin (Prism Central scope) and the Cluster Admin (Prism Element scope)

clarifying why C and D are incorrect.