Nutanix Objects, part of Nutanix Unified Storage (NUS), supports replication rules to replicate bucket data to a destination Object Store for disaster recovery or data redundancy. When creating a replication rule, the administrator selects a destination Object Store from a drop-down list. If this list is empty, it indicates that the system cannot display any available Object Stores, which can be due to several reasons.

Analysis of Options:

Option A (The deployment of the Object Store is not in a running state): Correct. For an Object Store to appear in the drop-down list as a replication destination, it must be in a running state. If the destination Object Store is not running (e.g., due to a failure, maintenance, or incomplete deployment), it will not be listed as an available target for replication.

Option B (The Remote site has not been configured in the Protection Group): Incorrect. Nutanix Objects replication does not use Protection Groups, which are a concept associated with Nutanix Files or VMs in Prism Central for disaster recovery. Objects replication is configured directly between Object Stores, typically requiring a remote site configuration, but this is not tied to Protection Groups. The issue of an empty drop-down list is more directly related to the Object Store’s state or permissions.

Option C (The deployment of the Object Store is not in a Complete state): Incorrect. While an incomplete deployment might prevent an Object Store from being fully operational, Nutanix documentation typically uses “running state” to describe the operational status of an Object Store (as in option A). “Complete state” is not a standard term in Nutanix Objects documentation for this context, making this option less accurate.

Option D (The logged-in user does not have permissions to view the Object Store): Correct. Nutanix Objects uses role-based access control (RBAC). If the logged-in user lacks the necessary permissions to view or manage the destination Object Store, it will not appear in the drop-down list. For example, the user may need “Object Store Admin” privileges to see and select Object Stores for replication.

Selected Conditions:

A: An Object Store not in a running state (e.g., stopped, failed, or under maintenance) will not appear as a destination for replication.

D: If the user lacks permissions to view the Object Store, it will not be visible in the drop-down list, even if the Object Store is running.

Exact Extract from Nutanix Documentation:

From the Nutanix Objects Administration Guide (available on the Nutanix Portal):

“When configuring a replication rule, the destination Object Store must be in a running state to appear in the drop-down list. Additionally, the user configuring the replication rule must have sufficient permissions (e.g., Object Store Admin role) to view and manage the destination Object Store. If the Object Store is not running or the user lacks permissions, the drop-down list will appear empty.”

Nutanix Data Lens, part of Nutanix Unified Storage (NUS), provides data governance, analytics, and ransomware protection for Nutanix Files. Enabling Data Lens involves setting up access to the Data Lens service, which is a cloud-based service hosted by Nutanix, and integrating it with the on-premises file server.

Analysis of Options:

Option A (In Prism, enable Pulse health monitoring): Incorrect. Pulse is a Nutanix feature that collects telemetry data for health monitoring and support, sending it to Nutanix Insights. While Pulse is recommended for overall cluster health, it is not a required step for enabling Data Lens. Data Lens operates independently of Pulse and focuses on file server analytics, not cluster health monitoring.

Option B (Configure a MyNutanix account to access the Data Lens console): Correct. Data Lens is a cloud-based service, and accessing its console requires a MyNutanix account. The administrator must configure the MyNutanix account credentials in Prism Central to enable Data Lens and access its features, such as the Data Lens dashboard for monitoring file server activity. This is a mandatory step to integrate with the cloud service.

Option C (Configure the Data Services IP in Prism Central): Incorrect. The Data Services IP is used for iSCSI traffic in Nutanix Volumes (as noted in Questions 25 and 31), not for Data Lens. Data Lens communicates with the Nutanix cloud (insights.nutanix.com) over the internet and does not require a Data Services IP configuration.

Option D (Add File Services VM admin credentials to a MyNutanix account): Correct. To enable Data Lens for a file server, the administrator must provide the File Services VM (FSVM) admin credentials, which are used to authenticate and integrate the file server with the Data Lens service. These credentials are added via the MyNutanix account configuration in Prism Central, allowing Data Lens to access the file server for monitoring and analytics.

Selected Steps:

B: Configuring a MyNutanix account is required to access the Data Lens console and enable the service.

D: Adding FSVM admin credentials to the MyNutanix account ensures that Data Lens can authenticate and monitor the file server.

Exact Extract from Nutanix Documentation:From the Nutanix Data Lens Administration Guide (available on the Nutanix Portal):

“To enable Data Lens, configure a MyNutanix account in Prism Central to access the Data Lens console. Additionally, add the File Services VM admin credentials to the MyNutanix account to allow Data Lens to authenticate with the file server and enable monitoring and analytics features.”

Nutanix Files, part of Nutanix Unified Storage (NUS), can be upgraded to newer versions to gain access to new features, bug fixes, and improvements. Upgrading Files involves updating the File Server Virtual Machines (FSVMs) and can be performed using Nutanix’s management tools.

Analysis of Options:

Option A (Prism Element - LCM): Incorrect. Life Cycle Manager (LCM) in Prism Element is used to manage upgrades for AOS, hypervisors, and other cluster components, but it does not directly handle Nutanix Files upgrades. Files upgrades are managed through Prism Central, as Files is a distributed service that requires centralized management.

Option B (Prism Element - One-click): Incorrect. Prism Element does not have a “one-click” upgrade option for Nutanix Files. One-click upgrades are typically associated with hypervisor upgrades (e.g., ESXi, as in Question 47) or AOS upgrades, not Files. Files upgrades are performed via Prism Central.

Option C (Prism Central - LCM): Correct. Life Cycle Manager (LCM) in Prism Central can be used to upgrade Nutanix Files. LCM in Prism Central manages upgrades for Files by downloading the Files software bundle, distributing it to FSVMs, and performing a rolling upgrade to minimize downtime. This is a supported and recommended method for upgrading Files.

Option D (Prism Central - Files Manager): Correct. The Files Manager (or Files Console) in Prism Central provides a UI for managing Nutanix Files, including upgrades. The administrator can use the Files Manager to initiate an upgrade by uploading a Files software bundle or selecting an available version, and the upgrade process is managed through Prism Central, ensuring a coordinated update across all FSVMs.

Selected Methods:

C: LCM in Prism Central automates the Files upgrade process, making it a streamlined method.

D: The Files Manager in Prism Central provides a manual upgrade option through the UI, offering flexibility for administrators.

Exact Extract from Nutanix Documentation:

From the Nutanix Files Administration Guide (available on the Nutanix Portal):

“Nutanix Files can be upgraded using two methods in Prism Central: Life Cycle Manager (LCM) and the Files Manager. LCM in Prism Central automates the upgrade process by downloading and applying the Files software bundle, while the Files Manager allows administrators to manually initiate the upgrade by uploading a software bundle or selecting an available version.”

Nutanix Files, part of Nutanix Unified Storage (NUS), uses File Server Virtual Machines (FSVMs) to manage file services. A four-node FSVM deployment means four FSVMs are deployed, typically one per node in a four-node cluster. Nutanix Files requires two networks for FSVMs:

Client Network: Used for client-facing communication (e.g., SMB, NFS access).

Storage Network: Used for internal communication with the Nutanix cluster’s storage pool.

Each FSVM requires one IP address on each network, as established in Question 1.

Analysis of Options:

Option A (Four available IP addresses on the Client network): Correct. In a four-node FSVM deployment, each FSVM requires one IP address on the Client network for client communication (e.g., SMB, NFS). With four FSVMs, this means four IP addresses are needed on the Client network, one for each FSVM.

Option B (Four available IP addresses on the Storage network): Correct. Each FSVM also requires one IP address on the Storage network for internal communication with the Nutanix cluster’s storage pool. For four FSVMs, this means four IP addresses are needed on the Storage network, one for each FSVM.

Option C (Five available IP addresses on the Storage network): Incorrect. Only four IP addresses are needed on the Storage network for a four-node FSVM deployment—one per FSVM. A fifth IP address is not required, as there is no additional entity (e.g., a virtual IP) needed for the Storage network in this context.

Option D (Five available IP addresses on the Client network): Incorrect. Similarly, only four IP addresses are needed on the Client network for the four FSVMs. A fifth IP address might be needed in other scenarios (e.g., a virtual IP for load balancing in some configurations), but for a standard four-node FSVM deployment, four IPs suffice, as established in Question 1.

Selected Requirements:

A: Four IP addresses on the Client network are required, one for each of the four FSVMs.

B: Four IP addresses on the Storage network are required, one for each of the four FSVMs.

Why These Requirements?

Each FSVM in a Nutanix Files deployment requires one IP address on the Client network for client access and one on the Storage network for internal storage communication. For a four-node FSVM deployment, this translates to exactly four IP addresses on each network, matching the number of FSVMs.

Exact Extract from Nutanix Documentation:

From the Nutanix Files Deployment Guide (available on the Nutanix Portal):

“A Nutanix Files deployment with four FSVMs requires four available IP addresses on the Client network for client communication (SMB/NFS) and four available IP addresses on the Storage network for internal communication with the Nutanix cluster’s storage pool.”

The two minimum resources that are required for deploying Files instances are 8 GiB of memory per host and 4 vCPUs per host. Memory and vCPUs are resources that are allocated to VMs (Virtual Machines) to run applications and processes. Files instances are file server instances (FSIs) that run on FSVMs (File Server VMs) on a Nutanix cluster. FSVMs require at least 8 GiB of memory and 4 vCPUs per host to function properly and provide SMB and NFS access to file shares and exports. The administrator should ensure that there are enough memory and vCPUs available on each host before deploying Files instances. References: Nutanix Files Administration Guide, page 27; Nutanix Files Solution Guide, page 6

Self-Service Restore (SSR) in Nutanix Files, part of Nutanix Unified Storage (NUS), allows users to recover previous versions of files without administrator intervention. SSR is primarily designed for SMB shares, and it has specific limitations that restrict its functionality in certain scenarios.

Analysis of Options:

Option A (SSR is not supported at the root of distributed shares or exports): Correct. According to Nutanix documentation, SSR cannot be enabled at the root level of distributed shares or exports. Distributed shares in Nutanix Files are those that span multiple FSVMs for scalability, and the root of such shares does not support SSR due to the complexity of managing snapshots at that level.

Option B (SSR for SMB does not restore streams or attributes in directories): Incorrect. While SSR has limitations, this specific restriction is not documented in Nutanix Files documentation. SSR for SMB does restore file data and metadata, including attributes, though it may not support all advanced features like alternate data streams in some cases. However, this is not a primary limitation highlighted in the official documentation.

Option C (SSR does not support NFS shares): Correct. SSR is designed for SMB shares and relies on Windows Shadow Copy (VSS) integration to provide Previous Versions functionality. NFS shares do not support SSR, as NFS lacks a native equivalent to VSS for user-driven restores.

Option D (SSR does not support SMB shares): Incorrect. This is the opposite of the truth—SSR is specifically designed for SMB shares and is not supported for NFS shares, as noted in option C.

Selected Limitations:

A: SSR’s inability to function at the root of distributed shares or exports is a documented limitation, as it affects how snapshots are managed in distributed environments.

C: SSR’s lack of support for NFS shares is a fundamental limitation, as SSR relies on SMB-specific features.

Exact Extract from Nutanix Documentation:

From the Nutanix Files Administration Guide (available on the Nutanix Portal):

“Self-Service Restore (SSR) is supported only for SMB shares and is not available for NFS shares or exports. Additionally, SSR cannot be enabled at the root of distributed shares or exports due to limitations in snapshot management at the root level.”