2025 Updated Verified NCP-US-6.5 Q&As – Pass Guarantee or Full Refund [Q36-Q52]

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 File Analytics Deployment Guide, Version 4.0, Section: “Network Requirements for File Analytics” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix File Analytics Deployment”.

Nutanix Volumes uses IQN-based authorization to control access to volumes. The administrator must specify the IQN of the host that needs to access the volume when creating or editing the volume. If the host’s IQN is not authorized, it will not be able to see the target in the MS iSCSI Initiator3. References: Nutanix Volumes Administration Guide3

Nutanix Objects, part of Nutanix Unified Storage (NUS), provides S3-compatible object storage and is deployed as a set of Object Store Service VMs on a Nutanix cluster running AHV (or ESXi). The minimum number of nodes required for an Objects deployment ensures high availability and fault tolerance.
Analysis of Options:
* Option A (1): Incorrect. A single-node cluster does not meet the minimum requirements for Nutanix Objects, as it cannot provide the necessary fault tolerance and high availability. Objects requires at least three nodes to distribute Object Store Service VMs and ensure data redundancy.
* Option B (2): Incorrect. A two-node cluster also does not meet the minimum requirements for Objects.
Nutanix requires at least three nodes to ensure that the Object Store Service VMs can be distributed across nodes and maintain availability in case of a node failure.
* Option C (3): Correct. Nutanix Objects requires a minimum of three AHV nodes in a cluster to deploy and operate. This ensures that the Object Store Service VMs (typically three or more) can be distributed across nodes, providing high availability and fault tolerance. A three-node cluster is the minimum configuration for Objects to ensure data redundancy and resilience.
* Option D (5): Incorrect. While a five-node cluster can certainly support Objects, it exceeds the minimum requirement. Nutanix specifies that three nodes are sufficient for a basic Objects deployment, making five nodes unnecessary for the minimum requirement.
Why Option C?
Nutanix Objects requires at least three nodes to ensure high availability, fault tolerance, and data redundancy.
This allows the Object Store Service VMs to be distributed across nodes, ensuring that the service remains available even if a node fails. Three nodes is the minimum cluster size specified by Nutanix for deploying Objects.
Exact Extract from Nutanix Documentation:
From the Nutanix Objects Deployment Guide (available on the Nutanix Portal):
“Nutanix Objects requires a minimum of three AHV nodes in a cluster to ensure high availability and fault tolerance. This allows the Object Store Service VMs to be distributed across nodes, providing redundancy and ensuring service availability in case of a node failure.”
:
Nutanix Objects Deployment Guide, Version 4.0, Section: “Minimum Requirements for Objects Deployment” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix Objects Deployment Requirements”.

The company is using Nutanix Objects 3.2, a component of Nutanix Unified Storage (NUS), which provides S3-compatible object storage. Due to an S3 protocol compatibility issue with their backup application, they need to switch to an NFS repository. The solution must be the fastest and consume the least compute capacity (CPU and memory) on their Nutanix infrastructure.
Analysis of Options:
* Option A (Delete the existing bucket, create a new bucket, and enable NFS v3 access): Incorrect.
Nutanix Objects does support NFS access for buckets starting with version 3.5 (as per Nutanix documentation), but Objects 3.2 does not have this capability. Since the company is using Objects 3.2, this option is not feasible without upgrading or redeploying Objects, which is not mentioned in this option. Even if NFS were supported, deleting and recreating buckets does not address the compatibility issue directly and may still consume compute resources for bucket operations.
* Option B (Deploy Files and create a new Share with multi-protocol access enabled): Correct.
Nutanix Files, another component of NUS, supports NFS natively and can be deployed to create an NFS share quickly. Multi-protocol access (e.g., NFS and SMB) can be enabled on a Files share, allowing the backup application to use NFS as a repository. Deploying a Files instance with a minimal configuration (e.g., 3 FSVMs) consumes relatively low compute resources compared to redeploying or upgrading Objects, and it is the fastest way to provide an NFS repository without modifying the existing Objects deployment.
* Option C (Redeploy Objects using the latest version, create a new bucket, and enable NFS v3 access): Incorrect. Redeploying Objects with the latest version (e.g., 4.0 or later) would allow NFS v3 access, as this feature was introduced in Objects 3.5. However, redeployment is a time-consuming process that involves uninstalling the existing Object Store, redeploying a new instance, and reconfiguring buckets. This also consumes significant compute resources during the redeployment process, making it neither the fastest nor the least resource-intensive solution.
* Option D (Upgrade Objects to the latest version, create a new bucket, and enable NFS v3 access):
Incorrect. Upgrading Objects from 3.2 to a version that supports NFS (e.g., 3.5 or later) is a viable solution, as it would allow enabling NFS v3 access on a new bucket. However, upgrading Objects involves downtime, validation, and potential resource overhead during the upgrade process, which does not align with the requirement for the fastest solution with minimal compute capacity usage.
Why Option B is the Fastest and Least Resource-Intensive:
* Nutanix Files Deployment: Deploying a new Nutanix Files instance is a straightforward process that can be completed in minutes via Prism Central or the Files Console. A minimal Files deployment (e.g.,
3 FSVMs) requires 4 vCPUs and 12 GiB of RAM per FSVM (as noted in Question 2), totaling 12 vCPUs and 36 GiB of RAM. This is a relatively low resource footprint compared to redeploying or upgrading an Objects instance, which may require more compute resources during the process.
* NFS Support: Nutanix Files natively supports NFS, and enabling multi-protocol access (NFS and SMB) on a share is a simple configuration step that does not require modifying the existing Objects deployment.
* Speed: Deploying Files and creating a share can be done without downtime to the existing Objects setup, making it faster than upgrading or redeploying Objects.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Deployment Guide (available on the Nutanix Portal):
“Nutanix Files supports multi-protocol access, allowing shares to be accessed via both NFS and SMB protocols. To enable NFS access, deploy a Files instance and create a share with multi-protocol access enabled. A minimal Files deployment requires 3 FSVMs, each with 4 vCPUs and 12 GiB of RAM, ensuring efficient resource usage.” From the Nutanix Objects Administration Guide (available on the Nutanix Portal):
“Starting with Objects 3.5, NFS v3 access is supported for buckets, allowing them to be mounted as NFS file systems. This feature is not available in earlier versions, such as Objects 3.2.”
:
Nutanix Files Deployment Guide, Version 4.0, Section: “Deploying Nutanix Files and Configuring Shares” (Nutanix Portal).
Nutanix Objects Administration Guide, Version 4.0, Section: “NFS Access for Buckets” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix Files and Objects Comparison”.

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.”
:
Nutanix Data Lens Administration Guide, Version 4.0, Section: “Audit Trails in Data Lens” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix Data Lens Audit Features”.

Smart DR in Nutanix Files, part of Nutanix Unified Storage (NUS), is a disaster recovery (DR) solution that simplifies the setup of replication policies between file servers (e.g., using NearSync, as seen in Question 24).
After configuring a Smart DR policy, the administrator expects to see it in the Policies tab in Prism Central, but it is not visible despite confirmed connectivity between FSVMs and Prism Central via port 9440 (used for Prism communication, as noted in Question 21). This indicates a potential mismatch or configuration issue.
Analysis of Options:
* Option A (The primary and recovery file servers do not have the same version): Correct. Smart DR requires that the primary and recovery file servers (source and target) run the same version of Nutanix Files to ensure compatibility. If the versions differ (e.g., primary on Files 4.0, recovery on Files 3.8), the Smart DR policy may fail to register properly in Prism Central, resulting in it not appearing in the Policies tab. This is a common issue in mixed-version environments, as Smart DR relies on consistent features and APIs across both file servers.
* Option B (Port 7515 should be open for all External/Client IPs of FSVMs on the Source and Target cluster): Incorrect. Port 7515 is not a standard port for Nutanix Files or Smart DR communication. The External/Client network of FSVMs (used for SMB/NFS traffic) communicates with clients, not between FSVMs or with Prism Central for policy management. Smart DR communication between FSVMs and Prism Central uses port 9440 (already confirmed open), and replication traffic between FSVMs typically uses other ports (e.g., 2009, 2020), but not 7515.
* Option C (The primary and recovery file servers do not have the same protocols): Incorrect.
Nutanix Files shares can support multiple protocols (e.g., SMB, NFS), but Smart DR operates at the file server level, not the protocol level. The replication policy in Smart DR replicates share data regardless of the protocol, and a protocol mismatch would not prevent the policy from appearing in the Policies tab-it might affect client access, but not policy visibility.
* Option D (Port 7515 should be open for all Internal/Storage IPs of FSVMs on the Source and Target cluster): Incorrect. Similar to option B, port 7515 is not relevant for Smart DR or Nutanix Files communication. The Internal/Storage network of FSVMs is used for communication with the Nutanix cluster’s storage pool, but Smart DR policy management and replication traffic do not rely on port
7515. The key ports for replication (e.g., 2009, 2020) are typically already open, and the issue here is policy visibility, not replication traffic.
Why Option A?
Smart DR requires compatibility between the primary and recovery file servers, including running the same version of Nutanix Files. A version mismatch can cause the Smart DR policy to fail registration in Prism Central, preventing it from appearing in the Policies tab. Since port 9440 connectivity is already confirmed, the most likely issue is a version mismatch, which is a common cause of such problems in Nutanix Files DR setups.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Administration Guide (available on the Nutanix Portal):
“Smart DR requires that the primary and recovery file servers run the same version of Nutanix Files to ensure compatibility. A version mismatch between the source and target file servers can prevent the Smart DR policy from registering properly in Prism Central, resulting in the policy not appearing in the Policies tab.”
:
Nutanix Files Administration Guide, Version 4.0, Section: “Smart DR Configuration Requirements” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix Files Disaster Recovery”.===========

Nutanix File Analytics is a feature that provides insights into the usage and activity of file data stored on Nutanix 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. The FAVM collects metadata and statistics from the FSVMs and displays them in a graphical user interface (GUI). The FAVM must be deployed on the same network as the FSVMs, which is the Client-side network. This network is used for communication between File Analytics and FSVMs, as well as for accessing the File Analytics UI from a web browser. The Client-side network must have DHCP enabled and must be routable from the external hosts that access the file shares and File Analytics UI. Reference: Nutanix Files Administration Guide, page 93; Nutanix File Analytics Deployment Guide

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. Reference: 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 two platforms that are currently supported for Smart Tiering are AWS Standard and Azure Blob. Smart Tiering is a feature that allows administrators to tier data from Files to cloud storage based on file age, file size, and file type. Smart Tiering can help reduce the storage cost and optimize the performance of Files.
Smart Tiering currently supports AWS Standard and Azure Blob as the cloud storage platforms, and more platforms will be added in the future. References: Nutanix Files Administration Guide, page 99; Nutanix Files Solution Guide, page 11

The administrator should prevent the Files environment and the AD Server from having such a time difference in future by using the same NTP Servers for the File environment and the AD Server. NTP (Network Time Protocol) is a protocol that synchronizes the clocks of devices on a network with a reliable time source. NTP Servers are devices that provide accurate time information to other devices on a network. By using the same NTP Servers for the File environment and the AD Server, the administrator can ensure that they have consistent and accurate time settings and avoid any synchronization issues or errors. Reference: Nutanix Files Administration Guide, page 32; Nutanix Files Troubleshooting Guide

The administrator can meet this requirement by configuring data protection policies in the Files view in Prism Central. Data protection policies are policies that define how file data is protected by taking snapshots, replicating them to another site, or tiering them to cloud storage. Data protection policies can be configured for each share or export in a file server in the Files view in Prism Central. The administrator can create different data protection policies for different shares or exports based on their protection needs and requirements. References: Nutanix Files Administration Guide, page 79; Nutanix Files Solution Guide, page 9

The Files Console Dashboard View provides an overview of the Files cluster performance and usage, including the following graphs:
Storage Used: Shows the total storage used by the Files cluster, including data, metadata, and snapshots.
Open Connections: Shows the number of active SMB and NFS connections to the Files cluster.
Number of Files: Shows the number of files stored in the Files cluster, excluding snapshots.
Top Shares by Current Capacity: Shows the top five shares by current capacity usage in the Files cluster.
Top Shares by Current Connections: Shows the top five shares by current connection count in the Files cluster2. Reference: Nutanix Files Administration Guide2

Data Lens is a SaaS that provides file analytics and reporting, anomaly detection, audit trails, ransomware protection features, and tiering management for Nutanix Files. To configure Data Lens, one of the network requirements is to allow HTTPS (port 443) traffic between a CVM or Prism Central to insights.nutanix.com.
This allows Data Lens to collect metadata and statistics from the FSVMs and display them in a graphical user interface. References: Nutanix Files Administration Guide, page 93; Nutanix Data Lens User Guide Data Lens is a cloud-based service hosted at insights.nutanix.com, and Nutanix requires secure communication over HTTPS (port 443) for configuration and operation. The CVMs or Prism Central must have outbound access to insights.nutanix.com on port 443 to enable Data Lens, authenticate with the service, and send/receive analytics data.
Exact Extract from Nutanix Documentation:
From the Nutanix Data Lens Administration Guide (available on the Nutanix Portal):
“Data Lens requires outbound connectivity from the Nutanix cluster (CVMs or Prism Central) to insights.
nutanix.com over port 443 (HTTPS). Ensure that this port is open for secure communication to enable Data Lens configuration and operation.”
:
Nutanix Data Lens Administration Guide, Version 4.0, Section: “Network Requirements for Data Lens” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix Data Lens Network Configuration”.

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

Data Lens can provide a centralized management solution for Files deployments in multiple sites, including different geographical locations. Data Lens can also automate archiving tier policies for compliance purposes, by allowing administrators to create policies based on file attributes, such as age, size, type, or owner, and move files to a lower-cost tier or delete them after a specified period. Data Lens can also protect the data against ransomware, by allowing administrators to block malicious file signatures from being written to the file system. References: Nutanix Data Lens Administration Guide

Volumes is a feature that allows users to create and manage block storage devices (volume groups) on a Nutanix cluster. Volume groups can be accessed by external hosts using the iSCSI protocol. To ensure maximum performance, throughput, and redundancy for Oracle RAC on Linux implementation, while using the native method for securing workloads, the recommended configuration is to use Volumes with MPIO (Multipath I/O) and a single vDisk (virtual disk). MPIO is a technique that allows multiple paths between an iSCSI initiator and an iSCSI target, which improves performance and availability. A single vDisk is a logical unit number (LUN) that can be assigned to multiple hosts in a volume group, which simplifies management and reduces overhead. References: Nutanix Volumes Administration Guide, page 13; Nutanix Volumes Best Practices Guide