Free Practice Questions for the Nutanix Certified Professional (NCP) NCP-US-6.5 Exam (2026 Updated)

Smart Tiering in Nutanix Files, part of Nutanix Unified Storage (NUS), allows infrequently accessed (Cold) data to be tiered to external storage, such as a public cloud (e.g., AWS S3, Azure Blob), to free up space on the primary cluster (as noted in Question 34). Configuring Smart Tiering requires setting up a connection to the external storage target, which involves providing credentials and connectivity details.

Smart Tiering requires a connection to an external storage target, such as a cloud provider. The access key and secret key are mandatory to authenticate Nutanix Files with the target (e.g., an S3 bucket), enabling secure data tiering. Without these credentials, the tiering configuration cannot be completed, making them a mandatory criterion.

Exact Extract from Nutanix Documentation :

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

“To configure Smart Tiering in Nutanix Files, you must provide the access key and secret key for the external storage target (e.g., AWS S3, Azure Blob). These credentials are mandatory to authenticate with the cloud provider and enable data tiering to the specified target.”

The Nutanix-enabled technology that meets these requirements is Objects – WORM with versioning. WORM (Write-Once Read-Many) is a feature that prevents anyone from modifying or deleting data in a bucket while the policy is active. WORM policies help comply with strict data retention regulations that mandate how long specific data must be stored. Versioning is a feature that keeps multiple versions of an object in a bucket whenever it is overwritten or deleted. Versioning policies help preserve previous versions of an object for backup or recovery purposes. By enabling WORM and versioning for an Objects bucket, the administrator can ensure that data is kept for two years without being deleted or overwritten.  References:  Nutanix Objects User Guide, page 17; Nutanix Objects Solution Guide, page 9

The exhibit illustrates a data protection setup involving Nutanix Files, a component of Nutanix Unified Storage (NUS). It shows two sites: a Primary Site and a Remote Site, each with a File Server (FILE SVR1 and FILE SVR2, respectively). The Primary Site has shares (Share1, Share2, Share3, Share4) with a replication policy applied. Share1 and Share2 are marked as RW (read-write) on the Primary Site and RO (read-only) on the Remote Site, while Share3 has a replication policy with RW on both sites. Share4 is RO on the Primary Site and RW on the Remote Site. Clients access the shares on both sites, and the replication policy governs the data protection mechanism between the sites.

Analysis of the Exhibit:

Two Sites (Primary and Remote) : The setup involves replication between two sites, indicating a disaster recovery (DR) or high-availability scenario.

Replication Policy : The replication policy is applied to the shares, with specific shares being RW on one site and RO on the other (e.g., Share1 and Share2 are RW on Primary, RO on Remote). This suggests asynchronous replication, as synchronous replication would typically allow RW access on both sites with zero data loss.

Share3 (RW on Both Sites) : This indicates a special configuration, possibly for load balancing or specific workload requirements, but the primary focus is on the replication policy for DR.

Share4 (RO on Primary, RW on Remote) : This suggests a failover scenario where the Remote Site can take over as the primary for certain shares.

Analysis of Options:

Option A (Smart DR) : Incorrect. Smart DR is a Nutanix feature that simplifies disaster recovery by automating snapshot-based replication and recovery plans. While Smart DR can use replication policies, the exhibit specifically shows a replication setup between File Servers with RW/RO configurations, which aligns more directly with a replication mechanism like NearSync. Smart DR is more about the orchestration of recovery, not the replication mechanism itself.

Option B (Metro Availability) : Incorrect. Metro Availability provides synchronous replication between two sites with zero Recovery Point Objective (RPO), meaning no data loss. It typically allows RW access on both sites (with one site being primary) and requires low latency between sites (e.g., < 5 ms). The exhibit shows RW/RO configurations, indicating asynchronous replication, and does not suggest zero RPO, making Metro Availability an incorrect fit.

Option C (Availability Zones) : Incorrect. Availability Zones in Nutanix refer to distributing data across zones within a single cluster or cloud environment for high availability, not replication between two distinct sites. The exhibit clearly shows two separate sites with replication, not a single cluster with zones.

Option D (NearSync) : Correct. NearSync is a Nutanix data protection mechanism that provides near-synchronous replication with low RPOs (e.g., 1–15 minutes). It is commonly used for Nutanix Files to replicate shares between sites for disaster recovery. The exhibit’s RW/RO configuration aligns with NearSync, where the Primary Site is RW, and the Remote Site is RO for replicated shares, allowing failover to the Remote Site if needed. The replication policy shown in the exhibit matches NearSync’s behavior of replicating data asynchronously with a configurable RPO.

Why Option D?

NearSync is designed for disaster recovery scenarios where data is replicated between two sites with a low RPO, ensuring minimal data loss. The exhibit’s depiction of replication between FILE SVR1 and FILE SVR2, with RW/RO configurations for shares, is a hallmark of NearSync for Nutanix Files. The presence of a replication policy further supports this, as NearSync uses such policies to define replication schedules and RPOs. Metro Availability (option B) would require synchronous replication with zero RPO, which is not indicated by the RW/RO setup, and the other options (Smart DR, Availability Zones) do not fit the replication scenario shown.

Exact Extract from Nutanix Documentation :

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

“NearSync provides near-synchronous replication for Nutanix Files shares between two sites, enabling disaster recovery with low Recovery Point Objectives (RPOs) ranging from 1 to 15 minutes. Shares on the primary site are typically read-write (RW), while the remote site is read-only (RO) for replicated shares. A replication policy defines the replication schedule and RPO, allowing failover to the remote site in case of a disaster.”

Additional Notes :

The exhibit’s depiction of Share3 (RW on both sites) is a less common configuration but can be achieved with NearSync by allowing specific shares to be writable on both sites for load balancing or specific use cases. However, the overall setup (replication between sites with RW/RO for most shares) aligns with NearSync.

Metro Availability would typically show zero RPO and RW access on both sites for the same shares, which is not the case here.

The Files feature that the administrator should enable to ensure the sessions will auto-reconnect in such events is Durable File Handles. Durable File Handles is a feature that allows SMB clients to reconnect to a file server after a temporary network disruption or a client sleep state without losing the handle to the open file. Durable File Handles can improve the user experience and reduce the risk of data loss or corruption. Durable File Handles can be enabled for each share in the Files Console.  References:  Nutanix Files Administration Guide, page 76; Nutanix Files Solution Guide, page 10

The solution that meets the company’s requirements for their file storage needs is Files. Files is a feature that allows users to create and manage file server instances (FSIs) on a Nutanix cluster. FSIs can provide SMB and NFS access to file shares and exports for different types of clients. Files supports these requirements:

Distributed File System: Files uses a distributed file system that spans across multiple FSVMs (File Server VMs), which improves scalability, performance, and availability.

Active Directory integrated: Files can integrate with Active Directory for authentication and authorization of SMB clients and multiprotocol NFS clients.

Scale out architecture: Files can scale out by adding more FSVMs to an existing FSI or creating new FSIs on the same or different clusters.  References:  Nutanix Files Administration Guide, page 27; Nutanix Files Solution Guide, page 6

The number of configurable snapshots that are supported for SSR in a file server is 200. SSR (Snapshot-based Replication) is a feature that allows administrators to replicate snapshots of shares or exports from one file server to another file server on a different cluster or site for disaster recovery purposes. SSR can be configured with various parameters, such as replication frequency, replication status, replication mode, etc. SSR supports up to 200 configurable snapshots per share or export in a file server.  References:  Nutanix Files Administration Guide, page 81; Nutanix Files Solution Guide, page 9

The Files Console view in Prism Central is the primary interface for deploying and managing Files clusters. Administrators can use the Files Console to create a new instance of Files by providing the required information, such as cluster name, network configuration, storage capacity, and license key. References: Nutanix Files Administration Guide

Deploying a new instance of Nutanix Files is done through the Files Console view in Prism Central, where the administrator can create a new File Server, specify the number of FSVMs, configure networks (Client and Storage), and allocate storage. This is the standard and supported method for Files deployment, providing a centralized interface for managing Files instances.

Exact Extract from Nutanix Documentation :

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

“To deploy a new instance of Nutanix Files, use the Files Console view in Prism Central. Navigate to the Files Console, select the option to create a new File Server, and configure the settings, including the number of FSVMs, network configuration, and storage allocation.”

Data Lens is a feature that provides insights into the data stored in Files, such as file types, sizes, owners, permissions, and access patterns. Data Lens allows administrators to create reports on various aspects of their data and schedule them to run automatically on a weekly basis. References: Nutanix Data Lens Administration Guide

The tool that includes these features is File Analytics. File Analytics is a feature that provides insights into the usage and activity of file data stored on Files. File Analytics consists of a File Analytics VM (FAVM) that runs on a Nutanix cluster and communicates with the File Server VMs (FSVMs) that host the file shares. File Analytics can display various reports and dashboards that include these features:

Permission Denials: This report shows the number of permission denied events for file operations, such as read, write, delete, etc., along with the user, file, share, and server details.

Top 5 Active Users: This dashboard shows the top five users who performed the most file operations in a given time period, along with the number and type of operations.

Top 5 Accessed Files: This dashboard shows the top five files that were accessed the most in a given time period, along with the number of accesses and the file details.

File Distribution by Type: This dashboard shows the distribution of files by their type or extension, such as PDF, DOCX, JPG, etc., along with the number and size of files for each type.  References:  Nutanix Files Administration Guide, page 93; Nutanix File Analytics User Guide

Self-Service Restore (SSR) is a feature that allows individual users to restore files and folders hosted in Files without requiring administrator intervention.  SSR can be enabled on a per-share or per-export basis, and users can access the snapshots of their data through a web portal or a Windows client application 1 . References: Nutanix Files Administration Guide 1

https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e000000CvHICA0

Nutanix File Analytics, part of Nutanix Unified Storage (NUS), is a tool for monitoring and analyzing file data within Nutanix Files deployments. It is deployed as a virtual machine (VM) on the Nutanix cluster and requires network connectivity to communicate with the File Server Virtual Machines (FSVMs) and other components.

Analysis of Options:

Option A (Must use the CVM network) : Incorrect. The CVM (Controller VM) network is typically an internal network used for communication between CVMs and storage components (e.g., the Distributed Storage Fabric). File Analytics does not specifically require the CVM network; it needs to communicate with FSVMs over a network accessible to clients and management.

Option B (Must use the Client-side network) : Correct. File Analytics requires connectivity to the FSVMs to collect and analyze file data. The Client-side network (also called the external network) is the network used by FSVMs for client communication (e.g., SMB, NFS) and management traffic. File Analytics must be deployed on this network to access the FSVMs, as well as to allow administrators to access its UI.

Option C (Must use the Backplane network) : Incorrect. The Backplane network is an internal network used for high-speed communication between nodes in a Nutanix cluster (e.g., for data replication, cluster services). File Analytics does not use the Backplane network, as it needs to communicate externally with FSVMs and users.

Option D (Must use the Storage-side network) : Incorrect. The Storage-side network is used for internal communication between FSVMs and the Nutanix cluster’s storage pool. File Analytics does not directly interact with the storage pool; it communicates with FSVMs over the Client-side network to collect analytics data.

Why Option B?

File Analytics needs to communicate with FSVMs to collect file metadata and user activity data, and it also needs to be accessible by administrators for monitoring. The Client-side network (used by FSVMs for client access and management) is the appropriate network for File Analytics deployment, as it ensures connectivity to the FSVMs and allows external access to the File Analytics UI.

Exact Extract from Nutanix Documentation :

From the Nutanix File Analytics Deployment Guide (available on the Nutanix Portal):

“File Analytics must be deployed on the Client-side network, which is the external network used by FSVMs for client communication (e.g., SMB, NFS) and management traffic. This ensures that File Analytics can communicate with the FSVMs to collect analytics data and that administrators can access the File Analytics UI.”

Nutanix Files, part of Nutanix Unified Storage (NUS), provides file shares (e.g., SMB, NFS) that clients access. Intermittent server-side networking issues or FSVM High Availability (HA) events (e.g., an FSVM failover, as discussed in Question 40) can disrupt client connections. The administrator needs a feature to ensure automatic reconnection to shares during such events, minimizing disruption for users.

Analysis of Options:

Option A (Multi-Protocol Shares) : Incorrect. Multi-Protocol Shares allow a share to be accessed via both SMB and NFS (as in Questions 8 and 60), but this feature does not address client reconnection during networking issues or FSVM HA events—it focuses on protocol support, not connection resilience.

Option B (Connected Shares) : Incorrect. “Connected Shares” is not a recognized feature in Nutanix Files. It appears to be a made-up term and does not apply to automatic client reconnection.

Option C (Durable File Handles) : Correct. Durable File Handles is an SMB feature in Nutanix Files (as noted in Question 19) that ensures automatic client reconnection after temporary server-side disruptions, such as networking issues or FSVM HA events (e.g., failover when an FSVM’s IP is reassigned, as in Question 40). When enabled, Durable File Handles allow SMB clients to maintain their session state and automatically reconnect without user intervention, meeting the requirement.

Option D (Persistent File Handles) : Incorrect. “Persistent File Handles” is not a standard feature in Nutanix Files. It may be confused with Durable File Handles (option C), which is the correct term for this SMB capability. Persistent File Handles is not a recognized Nutanix feature.

Why Option C?

Durable File Handles is an SMB 2.1+ feature supported by Nutanix Files that ensures clients can automatically reconnect to shares after server-side disruptions, such as intermittent networking issues or FSVM HA events (e.g., failover). This feature maintains the client’s session state, allowing seamless reconnection without manual intervention, directly addressing the administrator’s requirement.

Exact Extract from Nutanix Documentation :

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

“Durable File Handles is an SMB feature in Nutanix Files that ensures automatic client reconnection to shares during server-side disruptions, such as intermittent networking issues or FSVM HA events. Enable Durable File Handles to maintain client session state and allow seamless reconnection without user intervention.”

Nutanix Files allows users to restore their files from the snapshots taken by the protection policy. A protection policy is a set of rules that defines how often snapshots are taken, how long they are retained, and where they are replicated. A protection policy can be applied to one or more file shares. To enable users to restore their files without administrator intervention, the administrator must enable the Self Service Restore option for each share in the Files Console. This option adds a hidden folder named .snapshot in each share, which contains all the snapshots taken by the protection policy. Users can access this folder and browse the snapshots to find and restore their files. The administrator can also configure the permissions and quota for the .snapshot folder.  References:  Nutanix Files Administration Guide, page 75; Nutanix Files Self-Service Restore Guide

Nutanix Files, part of Nutanix Unified Storage (NUS), provides a Self-Service Restore (SSR) feature that allows end users to recover their files without administrator intervention. This feature is particularly useful for SMB shares, enabling users to access previous versions of files or folders directly from their Windows clients (e.g., via the " Previous Versions " tab in File Explorer).

The most efficient way to enable Self-Service Restore for multiple Files shares is to configure it at the share level within the Files Console . According to the Nutanix Files Administration Guide, the Self-Service Restore option can be enabled for each share individually through the Shares tab in the Files Console. While this requires enabling the setting for each share, it is the most direct and supported method for enabling SSR across multiple shares, as it does not involve external tools like Data Lens or complex configurations like Protection Policies or Consistency Groups.

Option A : Correct. Enabling Self-Service Restore in the Edit wizard for each share via the Shares tab in the Files Console is the standard method. It allows users to restore files directly without administrator intervention. While it requires configuring each share individually, it is efficient for a small to moderate number of shares and aligns with Nutanix’s recommended approach.

Option B : Incorrect. Nutanix Data Lens is a service for data governance, analytics, and ransomware protection, not for managing Self-Service Restore settings. Data Lens focuses on scanning shares for anomalies and providing recovery points, but it does not have a direct option to enable SSR for shares.

Option C : Incorrect. Assigning Categories to FSVMs and linking them to a Protection Policy in Prism Central is related to VM or resource protection (e.g., snapshots or replication), not to enabling user-driven file restoration for Files shares.

Option D : Incorrect. Consistency Groups and Protection Domains in Prism Element are used for data protection and disaster recovery (e.g., asynchronous replication), not for enabling Self-Service Restore for end users.

Exact Extract from Nutanix Documentation :

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

“Self-Service Restore allows end users to recover files and folders from SMB shares without administrator intervention. To enable Self-Service Restore, navigate to the Shares tab in the Files Console, select a share, and click Edit. In the Edit wizard, check the ‘Enable Self Service Restore’ option. This must be configured for each share individually.”

Additional Notes :

While enabling SSR for each share individually (option A) may seem less efficient for a very large number of shares, Nutanix does not currently provide a bulk configuration option for SSR in the Files Console. Automation via APIs could be an alternative for large-scale deployments, but this is not mentioned in the question’s options.

The question emphasizes “most efficient,” and option A is the most straightforward and officially supported method per the documentation.

Nutanix Objects, part of Nutanix Unified Storage (NUS), is an S3-compatible object storage solution that can be deployed on AHV or ESXi hypervisors. Deploying Objects has specific prerequisites to ensure successful installation and operation.

Analysis of Options:

Option A (Prism Central version is 5.17.1 or later) : Incorrect. While Nutanix Objects requires Prism Central for deployment and management, the minimum version for Objects deployment is typically lower (e.g., Prism Central 5.15 or later, depending on the Objects version). Version 5.17.1 is not a specific requirement for Objects deployment on AHV or ESXi.

Option B (Port 9440 is accessible on both PE and PC) : Correct. Port 9440 is used for communication between Prism Element (PE) and Prism Central (PC), as well as for internal Nutanix services. When deploying Objects, Prism Central communicates with the cluster (via Prism Element) to deploy Object Store Service VMs. This communication requires port 9440 to be open between PE and PC, making it a key prerequisite.

Option C (Valid SSL Certificate) : Incorrect. While a valid SSL certificate is recommended for secure communication (e.g., for S3 API access), it is not a strict prerequisite for deploying Objects. Objects can be deployed with self-signed certificates, though Nutanix recommends replacing them with valid certificates for production use.

Option D (Nutanix STARTER License) : Incorrect. The Nutanix STARTER license is an entry-level license for basic cluster functionality (e.g., VMs, storage). However, Nutanix Objects requires a separate license (e.g., Objects license or a higher-tier AOS license like Pro or Ultimate). The STARTER license alone does not support Objects deployment.

Why Option B?

Port 9440 is critical for communication between Prism Element and Prism Central during the deployment of Objects. If this port is blocked, the deployment will fail, as Prism Central cannot communicate with the cluster to deploy the Object Store Service VMs.

Exact Extract from Nutanix Documentation :

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

“Before deploying Nutanix Objects on AHV or ESXi, ensure that port 9440 is accessible between Prism Element (PE) and Prism Central (PC). This port is required for communication during the deployment process, as Prism Central manages the deployment of Object Store Service VMs on the cluster.”

The user that is authorized to deploy File Analytics is Prism Central administrator. Prism Central is a web-based user interface that allows administrators to manage multiple Nutanix clusters and services, including Files and File Analytics. Prism Central administrator is a user role that has full access and control over all Prism Central features and functions. To deploy File Analytics, the user must log in to Prism Central as a Prism Central administrator and follow the steps in the File Analytics Deployment wizard.  References:  Nutanix Files Administration Guide, page 93; Nutanix File Analytics Deployment Guide

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.”

The protocols that are supported by Files are SMBv2, SMBv3, NFSv3, and NFSv4. SMB (Server Message Block) is a protocol that allows clients to access files, printers, and other resources on a network. NFS (Network File System) is a protocol that allows clients to access files on a remote server as if they were local. Files supports both SMB and NFS protocols for creating shares and exports that can be accessed by different types of clients.  References:  Nutanix Files Administration Guide, page 31; Nutanix Files Solution Guide, page 6

Nutanix Volumes, part of Nutanix Unified Storage (NUS), provides block storage via iSCSI to VMs and external hosts. A Volume Group (VG) in Nutanix Volumes is a collection of volumes that can be attached to VMs. For VMs with intensive I/O, performance can be improved by distributing the I/O load across multiple Controller VMs (CVMs) in the Nutanix cluster. The vg.update command in the Nutanix CLI (e.g., ncli) is used to modify Volume Group settings, including parameters that affect I/O distribution.

Analysis of Options:

Option A (flash_mode=enable) : Incorrect. The flash_mode parameter enables flash mode for a Volume Group, which prioritizes SSDs for I/O operations to improve performance. While this can help with intensive I/O, it does not distribute I/O across multiple CVMs—it focuses on storage tiering, not load balancing.

Option B (load_balance_vm_attachments=true) : Correct. The load_balance_vm_attachments=true parameter enables load balancing of VM attachments for a Volume Group. When enabled, this setting distributes the iSCSI connections from VMs to multiple CVMs in the cluster, balancing the I/O load across CVMs. This improves performance for VMs with intensive I/O by ensuring that no single CVM becomes a bottleneck.

Option C (load_balance_vm_attachments=enable) : Incorrect. While this option is close to the correct parameter, the syntax is incorrect. The load_balance_vm_attachments parameter uses true or false as its value, not enable. The correct syntax is load_balance_vm_attachments=true (option B).

Option D (flash_mode=true) : Incorrect. Similar to option A, flash_mode=true enables flash mode for the Volume Group, prioritizing SSDs for I/O. This does not distribute I/O across multiple CVMs, as it addresses storage tiering rather than load balancing.

Why Option B?

The load_balance_vm_attachments=true parameter in the vg.update command enables load balancing for VM attachments to a Volume Group, distributing iSCSI connections across multiple CVMs. This ensures that the I/O load from VMs with intensive I/O is balanced across the cluster’s CVMs, improving performance by preventing any single CVM from becoming a bottleneck. This directly addresses the requirement to distribute I/O for better performance.

Exact Extract from Nutanix Documentation :

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

“To improve performance for Volume Groups with intensive I/O, use the vg.update command to enable load balancing with the parameter load_balance_vm_attachments=true. This setting distributes iSCSI connections from VMs across multiple CVMs in the cluster, balancing the I/O load and preventing bottlenecks.”

Nutanix Data Lens, a service integrated with Nutanix Unified Storage (NUS), provides data governance and security features for Nutanix Files. One of its key features is Audit Trails, which tracks user activities and file operations. The audit trails include specific details that can be monitored and reported.

Analysis of Options:

Option A (User Emails) : Incorrect. Data Lens Audit Trails track user activities, but they do not specifically log user emails as an audit trail metric. User identities (e.g., usernames) are logged, but email addresses are not a standard audit trail field.

Option B (Client IPs) : Correct. Data Lens Audit Trails include the client IP addresses from which file operations are performed, allowing administrators to track the source of user actions (e.g., which IP accessed or modified a file).

Option C (Files) : Correct. Data Lens Audit Trails track file-level operations, such as access, modifications, deletions, and permission changes, making “Files” a key audit trail metric.

Option D (Anomalies) : Incorrect. While Data Lens does detect anomalies (e.g., ransomware activity, unusual file operations), anomalies are a separate feature, not an audit trail. Audit Trails focus on logging specific user and file activities, while anomalies are derived from analyzing those activities.

Selected Audit Trails:

B : Client IPs are logged in audit trails to identify the source of file operations.

C : Files are the primary entities tracked in audit trails, with details on operations performed on them.

Exact Extract from Nutanix Documentation :

From the Nutanix Data Lens Administration Guide (available on the Nutanix Portal):

“Data Lens Audit Trails provide detailed logging of file operations, including the files affected, the user performing the action, and the client IP address from which the operation was initiated. This allows administrators to monitor user activities and track access patterns.”

Workload optimization in Nutanix Files, part of Nutanix Unified Storage (NUS), involves tuning the Files deployment to handle specific workloads efficiently. This was previously discussed in Question 13, where workload optimization was based on FSVM quantity. The question now asks which entity workload optimization is configured on.

Analysis of Options:

Option A (Volume) : Incorrect. Volumes in Nutanix refer to block storage provided by Nutanix Volumes, not Nutanix Files. Workload optimization for Files does not involve Volumes, which are a separate entity for iSCSI-based storage.

Option B (Share) : Incorrect. Shares in Nutanix Files are the individual file shares (e.g., SMB, NFS) accessed by clients. While shares can be tuned (e.g., quotas, permissions), workload optimization in Files is not configured at the share level—it applies to the broader file server infrastructure.

Option C (Container) : Incorrect. Containers in Nutanix are logical storage pools managed by AOS, used to store data for VMs, Files, and other services. While Files data resides in a container, workload optimization is not configured at the container level—it is specific to the Files deployment.

Option D (File Server) : Correct. Workload optimization in Nutanix Files is configured at the File Server level, which consists of multiple FSVMs (as established in Question 13). The File Server is the entity that manages all FSVMs, shares, and resources, and optimization tasks (e.g., scaling FSVMs, adjusting resources) are applied at this level to handle workloads efficiently.

Why Option D?

Workload optimization in Nutanix Files involves adjusting resources and configurations at the File Server level, such as scaling the number of FSVMs (as in Question 13) or tuning memory and CPU for the File Server. The File Server encompasses all FSVMs and shares, making it the entity where optimization is configured to ensure the entire deployment can handle the workload effectively.

Exact Extract from Nutanix Documentation :

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

“Workload optimization in Nutanix Files is configured at the File Server level. This involves adjusting the number of FSVMs, allocating resources (e.g., CPU, memory), and tuning configurations to optimize the File Server for specific workloads.”

Nutanix Files, part of Nutanix Unified Storage (NUS), supports WORM (Write Once, Read Many) shares to enforce immutability for compliance and data retention. A WORM share prevents files from being modified or deleted for a specified retention period. The “cool-off interval” (or cool-off period) is the time after a file is written to a WORM share during which it can still be modified or deleted before becoming immutable. The default cool-off interval is typically 1 minute, and the administrator wants to update it to 5 minutes.

Analysis of Options:

Option A (Delete and re-create the WORM share) : Incorrect. Deleting and re-creating the WORM share would remove the existing share and its data, which is disruptive and unnecessary. The cool-off interval can be updated without deleting the share, making this an inefficient and incorrect approach.

Option B (Update the worm_cooloff_interval parameter using CLI) : Correct. The worm_cooloff_interval parameter controls the cool-off period for WORM shares in Nutanix Files. This parameter can be updated using the Nutanix CLI (e.g., ncli or afs commands) on the file server. The administrator can log into an FSVM, use the CLI to set the worm_cooloff_interval to 5 minutes (300 seconds), and apply the change without disrupting the share. This is the most direct and efficient method to update the cool-off interval.

Option C (Contact support to update the WORM share) : Incorrect. Contacting Nutanix support is unnecessary for this task, as updating the cool-off interval is a standard administrative action that can be performed using the CLI. Support is typically needed for complex issues, not for configurable parameters like this.

Option D (Use FSM to update the worm_cooloff_interval parameter) : Incorrect. FSM (File Server Manager) is not a standard Nutanix tool or interface for managing Files configurations. The correct method is to use the CLI (option B) to update the worm_cooloff_interval parameter. While the Files Console (FSM-like interface) can manage some share settings, the cool-off interval requires CLI access.

Why Option B?

The worm_cooloff_interval parameter is a configurable setting in Nutanix Files that controls the cool-off period for WORM shares. Updating this parameter via the CLI (e.g., using ncli or afs commands on an FSVM) allows the administrator to change the cool-off interval from the default (1 minute) to 5 minutes without disrupting the existing share. This is the recommended and most efficient method per Nutanix documentation.

Exact Extract from Nutanix Documentation :

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

“The cool-off interval for a WORM share, which determines the time after a file is written during which it can still be modified, is controlled by the worm_cooloff_interval parameter. To update this interval, use the CLI on an FSVM to set the parameter (e.g., to 300 seconds for 5 minutes) using commands like ncli or afs, then apply the change.”

Nutanix Files, part of Nutanix Unified Storage (NUS), provides a management interface called the Files Console, accessible via Prism Central. The administrator needs to review graphs related to resource usage on a file server, including Storage Used, Open Connections, Number of Files, Top Shares by Current Capacity, and Top Shares by Current Connections. These graphs provide insights into the file server’s performance and resource utilization, helping diagnose reported resource issues.

Analysis of Options:

Option A (Files Console Shares View) : Incorrect. The Shares View in the Files Console displays details about individual shares (e.g., capacity, permissions, quotas), but it does not provide high-level graphs like Storage Used, Open Connections, or Top Shares by Current Capacity/Connections. It focuses on share-specific settings, not overall file server metrics.

Option B (Files Console Monitoring View) : Incorrect. While “Monitoring View” sounds plausible, there is no specific “Monitoring View” tab in the Files Console. Monitoring-related data (e.g., graphs, metrics) is typically presented in the Dashboard View, not a separate Monitoring View.

Option C (Files Console Data Management View) : Incorrect. There is no “Data Management View” in the Files Console. Data management tasks (e.g., Smart Tiering, as in Question 58) are handled in other sections, but graphs like Storage Used and Top Shares are not part of a dedicated Data Management View.

Option D (Files Console Dashboard View) : Correct. The Dashboard View in the Files Console provides an overview of the file server’s performance and resource usage through various graphs and metrics. It includes graphs such as Storage Used (total storage consumption), Open Connections (active client connections), Number of Files (total files across shares), Top Shares by Current Capacity (shares consuming the most storage), and Top Shares by Current Connections (shares with the most active connections). This view is designed to help administrators monitor and troubleshoot resource issues, making it the correct location for reviewing these graphs.

Why Option D?

The Files Console Dashboard View is the central location for monitoring file server metrics through graphs like Storage Used, Open Connections, Number of Files, and Top Shares by Capacity/Connections. These graphs provide a high-level overview of resource utilization, allowing the administrator to diagnose reported resource issues effectively.

Exact Extract from Nutanix Documentation :

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

“The Files Console Dashboard View provides an overview of file server performance and resource usage through graphs, including Storage Used, Open Connections, Number of Files, Top Shares by Current Capacity, and Top Shares by Current Connections. Use the Dashboard View to monitor and troubleshoot resource issues on the file server.”

The correct task order for creating an object store is:

Select ObjectStore Service and click Enable

Click Create Object Store to start creating the first Object store

Click Download Creation Checklist to download the list of prerequisites for deploying an Object store

The first step is to enable the ObjectStore Service, which is a service that allows users to create and manage object storage clusters on a Nutanix cluster. The second step is to create an Object store, which is an object storage cluster that provides S3-compatible access to buckets and objects for various applications and users. The third step is to download the Creation Checklist, which is a document that lists the prerequisites and configurations that are required for deploying an Object store, such as cluster details, network details, storage details, etc. The administrator should review and complete the Creation Checklist before proceeding with the deployment of the Object store.

A distributed share is a type of SMB share or NFS export that distributes the hosting of top-level directories across multiple FSVMs, which improves load balancing and performance. A distributed share cannot be created on a single-node cluster, because there is only one FSVM available. A distributed share requires at least two nodes in the cluster to distribute the directories. Therefore, the task of creating a distributed share on a single-node cluster will fail.  References:  Nutanix Files Administration Guide, page 33; Nutanix Files Solution Guide, page 8

A distributed share in Nutanix Files, part of Nutanix Unified Storage (NUS), is a share that spans multiple File Server Virtual Machines (FSVMs) to provide scalability and high availability. Distributed shares are designed to handle large-scale workloads by distributing file operations across FSVMs.

Analysis of Options:

Option A (File server version should be greater than 3.8.0) : Incorrect. While Nutanix Files has version-specific features, distributed shares have been supported since earlier versions (e.g., Files 3.5). The failure to create a distributed share on a single-node cluster is not due to the Files version.

Option B (Distributed shares require multiple nodes) : Correct. Distributed shares in Nutanix Files require a minimum of three FSVMs for high availability and load balancing, which in turn requires a cluster with at least three nodes. A single-node cluster cannot support a distributed share because it lacks the necessary nodes to host multiple FSVMs, which are required for the distributed architecture.

Option C (AOS version should be greater than 6.0) : Incorrect. Nutanix AOS (Acropolis Operating System) version 6.0 or later is not a specific requirement for distributed shares. Distributed shares have been supported in earlier AOS versions (e.g., AOS 5.15 and later with compatible Files versions). The issue is related to the cluster’s node count, not the AOS version.

Option D (Number of distributed shares limit reached) : Incorrect. The question does not indicate that the administrator has reached a limit on the number of distributed shares. The failure is due to the single-node cluster limitation, not a share count limit.

Why Option B?

A single-node cluster cannot support a distributed share because Nutanix Files requires at least three FSVMs for a distributed share, and each FSVM typically runs on a separate node for high availability. A single-node cluster can support a non-distributed (standard) share, but not a distributed share, which is designed for scalability across multiple nodes.

Exact Extract from Nutanix Documentation :

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

“Distributed shares in Nutanix Files require a minimum of three FSVMs to ensure scalability and high availability. This requires a cluster with at least three nodes, as each FSVM is typically hosted on a separate node. Single-node clusters do not support distributed shares due to this requirement.”

The tool that can be used to report on a specific user’s activity within a Files environment is Data Lens Audit Trails. Data Lens Audit Trails is a feature that provides detailed logs of all file operations performed by users on Files shares and exports, such as create, read, write, delete, rename, move, copy, etc. Data Lens Audit Trails can help administrators track and audit user actions and identify any unauthorized or malicious activities. The administrator can use Data Lens Audit Trails to filter and search for a specific user’s activity based on various criteria, such as file name, file type, file size, file path, file share, file server, operation type, operation time, operation status, and so on.  References:  Nutanix Files Administration Guide, page 98; Nutanix Data Lens User Guide

Nutanix Files, part of Nutanix Unified Storage (NUS), supports monitoring and reporting on user activities to track file access, modifications, and other operations. To report on a specific user’s activity, a tool that provides detailed audit trails at the file level is required.

Analysis of Options:

Option A (Prism Element Alerts menu) : Incorrect. The Alerts menu in Prism Element provides cluster-level alerts (e.g., hardware failures, storage issues), but it does not offer detailed user activity reports for Files shares.

Option B (Files Console Usage) : Incorrect. The Files Console provides usage statistics for shares (e.g., storage consumption, share-level metrics), but it does not provide granular user activity reports or audit trails for specific users.

Option C (Data Lens Audit Trails) : Correct. Nutanix Data Lens, a service integrated with Nutanix Files, provides audit trails that track user activities at the file level. This includes details such as file access, modifications, deletions, and permission changes, allowing administrators to report on a specific user’s actions within the Files environment.

Option D (Prism Central Activity menu) : Incorrect. The Activity menu in Prism Central provides high-level activity logs for cluster operations (e.g., VM creation, policy updates), but it does not provide detailed file-level user activity reports for Nutanix Files.

Why Data Lens Audit Trails?

Nutanix Data Lens is designed for data governance and security, offering features like audit trails, anomaly detection, and ransomware protection. The Audit Trails feature specifically allows administrators to filter and report on user activities, such as which files a user accessed, modified, or deleted, making it the ideal tool for this task.

Exact Extract from Nutanix Documentation :

From the Nutanix Data Lens Administration Guide (available on the Nutanix Portal):

“Data Lens Audit Trails provide detailed tracking of user activities within Nutanix Files shares. Administrators can view and filter audit logs to report on specific user actions, including file access, modifications, deletions, and permission changes. This feature is accessible via the Data Lens dashboard.”

Nutanix File Analytics, part of Nutanix Unified Storage (NUS), provides reporting capabilities for monitoring file server activity, including space usage by owners. The administrator wants to generate a report listing the top owners by space consumed, which is a standard report in File Analytics. The available export formats for such reports determine how the data can be shared or analyzed.

Analysis of Options:

Option A (XML) : Incorrect. File Analytics does not support exporting reports in XML format. While XML is a common data format, Nutanix File Analytics focuses on more user-friendly formats like PDF and CSV for report exports.

Option B (PDF) : Correct. File Analytics allows reports, such as the top owners by space consumed, to be exported in PDF format. This format is useful for creating a formatted, printable report that can be shared with stakeholders or archived for documentation purposes.

Option C (CSV) : Correct. File Analytics also supports exporting reports in CSV (Comma-Separated Values) format. This format is ideal for further analysis, as the data can be imported into tools like Excel or other data processing software to manipulate the list of top owners and their space consumption.

Option D (JSON) : Incorrect. JSON is a data format often used for APIs or data interchange, but File Analytics does not support exporting reports in JSON format. The focus is on PDF for presentation and CSV for data analysis.

Selected Formats:

B : PDF format provides a formatted report suitable for sharing or printing.

C : CSV format allows for data export and further analysis in external tools.

Exact Extract from Nutanix Documentation :

From the Nutanix File Analytics Administration Guide (available on the Nutanix Portal):

“File Analytics reports, such as top owners by space consumed, can be exported in PDF format for presentation or CSV format for further analysis. These formats allow administrators to share reports with stakeholders or import the data into other tools for additional processing.”

The appropriate configuration to verify to allow successful Objects cluster deployment to this ESXi cluster is to ensure that vCenter in PE cluster is registered using FQDN (Fully Qualified Domain Name) and that vCenter details in Objects UI are using FQDN. FQDN is a domain name that specifies the exact location of a host in the domain hierarchy. For example, esxi01.nutanix.com is an FQDN for an ESXi host. Using FQDN instead of IP addresses can avoid certificate validation errors when deploying Objects clusters to ESXi clusters.  References:  Nutanix Objects User Guide, page 9; Nutanix Objects Troubleshooting Guide, page 5

The organization uses a Nutanix Files cluster, part of Nutanix Unified Storage (NUS), for back office data, with most data classified as Cold Data (infrequently accessed). They want to free up space on the Files cluster for future growth or newer data. They have added a new node with more storage to the cluster and are already using the Public Cloud for other storage needs. The goal is to migrate Cold Data to free up space while considering the best approach.

Analysis of Options:

Option A (Set up another cluster and replicate the data with Protection Domain) : Incorrect. Setting up another cluster and using a Protection Domain to replicate data is a disaster recovery (DR) strategy, not a solution for migrating Cold Data to free up space. Protection Domains are used to protect and replicate VMs or Volume Groups, not Files shares directly, and this approach would not address the goal of freeing up space on the existing Files cluster—it would simply create a copy on another cluster.

Option B (Enable Smart Tiering in Files within the Files Console) : Correct. Nutanix Files supports Smart Tiering, a feature that allows data to be tiered to external storage, such as the Public Cloud (e.g., AWS S3, Azure Blob), based on access patterns. Cold Data (infrequently accessed) can be automatically tiered to the cloud, freeing up space on the Files cluster while keeping the data accessible through the same share. Since the organization is already using the Public Cloud, Smart Tiering aligns perfectly with their infrastructure and requirements.

Option C (Migrate cold data from Files to tape storage) : Incorrect. Migrating data to tape storage is a manual and outdated process for archival. Nutanix Files does not have native integration with tape storage, and this approach would require significant manual effort, making it less efficient than Smart Tiering. Additionally, tape storage is not as easily accessible as cloud storage for future retrieval.

Option D (Back up the data using a third-party software and replicate to the cloud) : Incorrect. While backing up data with third-party software and replicating it to the cloud is feasible, it is not the best approach for this scenario. This method would create a backup copy rather than freeing up space on the Files cluster, and it requires additional software and management overhead. Smart Tiering is a native feature that achieves the goal more efficiently by moving Cold Data to the cloud while keeping it accessible.

Why Option B?

Smart Tiering in Nutanix Files is designed for exactly this use case: moving Cold Data to a lower-cost storage tier (e.g., Public Cloud) to free up space on the primary cluster while maintaining seamless access to the data. Since the organization is already using the Public Cloud and has added a new node (which increases local capacity but doesn’t address Cold Data directly), Smart Tiering leverages their existing cloud infrastructure to offload Cold Data, freeing up space for future growth or newer data. This can be configured in the Files Console by enabling Smart Tiering and setting policies to tier Cold Data to the cloud.

Exact Extract from Nutanix Documentation :

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

“Smart Tiering in Nutanix Files allows administrators to tier Cold Data to external storage, such as AWS S3 or Azure Blob, to free up space on the primary Files cluster. This feature can be enabled in the Files Console, where policies can be configured to identify and tier infrequently accessed data while keeping it accessible through the same share.”

 Nutanix Objects requires a Data Services IP to be configured on the Prism Infrastructure (PI) cluster, which is used to expose the S3 API endpoint for accessing buckets and objects.  Nutanix Objects also requires AHV IP Address Management (IPAM) to be disabled on the VLAN used for Objects, as Objects uses its own DHCP service to assign IP addresses to the Objects VMs 1 . References: Nutanix Objects Administration Guide 1