[2026] New NCP-US-6.5 exam dumps Use Updated Nutanix Exam [Q16-Q32]

Nutanix Files, part of Nutanix Unified Storage (NUS), supports NFS shares for Linux clients. The administrator changed the user management authentication on the file server (e.g., updated Active Directory settings, modified user mappings, or changed authentication methods like Kerberos). This change has caused a “Permission denied” error for a user accessing an NFS share from a Linux client, indicating an authentication or permission issue.
Analysis of Options:
* Option A (Change the permission for user): Incorrect. While incorrect permissions can cause a
“Permission denied” error, the error here is likely due to the authentication change on the file server, not a share-level permission issue. Changing user permissions might be a workaround, but it does not address the root cause (authentication mismatch) and is less efficient than resolving the authentication issue directly.
* Option B (Restart the nfs-utils service): Correct. The nfs-utils service on the Linux client manages NFS-related operations, including authentication and mounting. After the file server’s authentication settings are changed (e.g., new user mappings, Kerberos configuration), the client may still be using cached credentials or an outdated authentication state. Restarting the nfs-utils service (e.g., via systemctl restart nfs-utils) refreshes the client’s NFS configuration, re-authenticates with the file server, and resolves the “Permission denied” error efficiently.
* Option C (Restart the client machine): Incorrect. Restarting the entire client machine would force a reconnection to the NFS share and might resolve the issue by clearing cached credentials, but it is not the most efficient solution. It causes unnecessary downtime for the user and other processes on the client, whereas restarting the nfs-utils service (option B) achieves the same result with less disruption.
* Option D (Restart the RPC-GSSAPI service on the clients): Incorrect. The RPC-GSSAPI service (related to GSSAPI for Kerberos authentication) might be relevant if the file server is using Kerberos for NFS authentication. However, there is no standard rpc-gssapi service in Linux-GSSAPI is typically handled by rpc.gssd, a daemon within nfs-utils. Restarting rpc.gssd directly is less efficient than restarting the entire nfs-utils service (which includes rpc.gssd), and the question does not specify Kerberos as the authentication method, making this option less applicable.
Why Option B?
The “Permission denied” error after an authentication change on the file server suggests that the Linux client’s NFS configuration is out of sync with the new authentication settings. Restarting the nfs-utils service on the client refreshes the NFS client’s state, re-authenticates with the file server using the updated authentication settings, and resolves the error efficiently without requiring a full client restart or manual permission changes.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Administration Guide (available on the Nutanix Portal):
“If a user receives a ‘Permission denied’ error on an NFS share after changing user management authentication on the file server, the issue is often due to the Linux client using cached credentials or an outdated authentication state. To resolve this efficiently, restart the nfs-utils service on the client (e.g., systemctl restart nfs-utils) to refresh the NFS configuration and re-authenticate with the file server.”
:
Nutanix Files Administration Guide, Version 4.0, Section: “Troubleshooting NFS Access Issues” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix Files NFS Troubleshooting”.

The component that must first be upgraded to a compatible version before upgrading Files or creating a file server is Prism Central. Prism Central is a web-based user interface that allows administrators to manage multiple Nutanix clusters and services, including Files. Prism Central must be upgraded to a compatible version with Files before upgrading an existing file server or creating a new file server. Otherwise, the upgrade or creation process may fail or cause unexpected errors. References: Nutanix Files Administration Guide, page 21; Nutanix Files Upgrade Guide

The scenario that is causing the alert and needs to be addressed to allow the entities to be protected is that one or more VMs or Volume Groups belonging to the Consistency Group may have been deleted. A Consistency Group is a logical grouping of VMs or Volume Groups that are protected together by a 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 for disaster recovery purposes. If one or more VMs or Volume Groups belonging to the Consistency Group are deleted, the Protection Policy will fail to protect them and generate an alert with the code AI303551 – VolumeGroupProtectionFailed. Reference: Nutanix Volumes Administration Guide, page 29; Nutanix Volumes Troubleshooting Guide

The error log that the administrator should review to determine why the relative service is down is arithmos.
ERROR. Arithmos is a service that runs on each CVM and provides volume group protection functionality for Volumes. Volume group protection is a feature that allows administrators to create protection policies for volume groups, which define how often snapshots are taken, how long they are retained, and where they are replicated. If arithmos.ERROR log shows any errors or exceptions related to volume group protection, it can indicate that the relative service is down or not functioning properly. References: Nutanix Volumes Administration Guide, page 29; Nutanix Volumes Troubleshooting Guide

The two steps that are required for enabling Data Lens are:
In Prism, enable Pulse health monitoring: Pulse is a feature that collects diagnostic and usage information from Nutanix clusters and services and sends it to Nutanix for analysis and support purposes. Pulse health monitoring is a feature that monitors the health status of Nutanix clusters and services and sends alerts to Nutanix if any issues are detected. To enable Data Lens, Pulse health monitoring must be enabled in Prism Element or Prism Central.
Configure the Data Services IP in Prism Central: Data Services IP is an IP address that is used for communication between Prism Central and Data Lens. Data Services IP must be configured in Prism Central before enabling Data Lens for any file server. Data Services IP must be routable from both Prism Central and Data Lens. Reference: Nutanix Files Administration Guide, page 93; Nutanix Data Lens Deployment Guide

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

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

To scale out an existing Files instance, the administrator needs to add one Client IP and one Storage IP for each additional FSVM. Since the Files instance needs to expand from four FSVMs to six FSVMs, the administrator needs to add two Client IPs and two Storage IPs in total. The Client IPs are used for communication between the FSVMs and the clients, while the Storage IPs are used for communication between the FSVMs and the CVMs. Reference: Nutanix Files Administration Guide, page 28; Nutanix Files Solution Guide, page 7

Nutanix Volumes allows administrators to provision a volume group with one or more volumes that can be attached to multiple VMs or physical servers via iSCSI. This enables the creation of a Microsoft Server Failover Cluster that uses shared storage for a critical application.
Microsoft Server Failover Cluster typically uses shared block storage for its quorum disk and application data.
Nutanix Volumes provides this via iSCSI by provisioning a Volume Group, which can be accessed by both the AHV-hosted VMs and bare metal servers. This setup ensures maximum resiliency, as the shared storage is accessible to all nodes in the cluster, allowing failover between VMs and bare metal servers as needed.
Exact Extract from Nutanix Documentation:
From the Nutanix Volumes Administration Guide (available on the Nutanix Portal):
“Nutanix Volumes provides block storage via iSCSI, which is ideal for Microsoft Server Failover Clusters requiring shared storage. To deploy an MSFC with VMs and bare metal servers, provision a Volume Group in Nutanix Volumes and expose it via iSCSI to all cluster nodes, ensuring shared access to the storage for high availability and failover.”
:
Nutanix Volumes Administration Guide, Version 6.0, Section: “Using Nutanix Volumes with Microsoft Failover Clustering” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix Volumes for Shared Storage”.

The alert A130358 – ConsistencyGroupWithStaleEntities in a Nutanix environment indicates an issue with a Consistency Group, which is used in Nutanix data protection to ensure that related entities (e.g., VMs, Volume Groups) are protected together in a consistent state. This alert specifically points to “stale entities,” meaning there is a problem with the entities within the Consistency Group that prevents proper protection.
Analysis of Options:
* Option A (One or more VMs or Volume Groups belonging to the Consistency Group contains stale metadata): Correct. The “ConsistencyGroupWithStaleEntities” alert is triggered when entities (e.
g., VMs or Volume Groups) in a Consistency Group have stale metadata, meaning their metadata is outdated or corrupted. This can happen due to synchronization issues, failed operations, or manual changes that leave the metadata inconsistent with the actual state of the entity. This prevents the Consistency Group from being protected properly, as the system cannot ensure consistency.
* Option B (One or more VMs or Volume Groups belonging to the Consistency Group may have been deleted): Incorrect. If an entity in a Consistency Group is deleted, a different alert would typically be triggered (e.g., related to a missing entity). The “StaleEntities” alert specifically refers to metadata issues, not deletion. However, deletion could indirectly cause metadata staleness if the deletion was not properly synchronized, but this is not the primary cause described by the alert.
* Option C (The logical timestamp for one or more of the Volume Groups is not consistent between clusters): Incorrect. Inconsistent logical timestamps between clusters would typically trigger a different alert related to replication or synchronization (e.g., in Metro Availability or NearSync scenarios). The
“StaleEntities” alert is specific to metadata issues within the Consistency Group on the local cluster, not a cross-cluster timestamp issue.
* Option D (One or more VMs or Volume Groups belonging to the Consistency Group is part of multiple Recovery Plans configured with a Witness): Incorrect. Being part of multiple Recovery Plans or using a Witness (e.g., in Metro Availability) does not directly cause a “StaleEntities” alert.
This scenario might cause other issues (e.g., conflicts in recovery operations), but it is not related to stale metadata within a Consistency Group.
Why Option A?
The “ConsistencyGroupWithStaleEntities” alert explicitly indicates that the entities in the Consistency Group have stale metadata, which must be resolved to allow proper protection. The administrator would need to investigate the affected VMs or Volume Groups, clear the stale metadata (e.g., by refreshing the Consistency Group or removing/re-adding the entity), and ensure synchronization with the cluster’s state.
Exact Extract from Nutanix Documentation:
From the Nutanix Prism Alerts Reference Guide (available on the Nutanix Portal):
“Alert A130358 – ConsistencyGroupWithStaleEntities: This alert is triggered when one or more entities (e.g., VMs or Volume Groups) in a Consistency Group have stale metadata, preventing the group from being protected consistently. Stale metadata can occur due to failed operations, synchronization issues, or manual changes. To resolve, identify the affected entities, clear the stale metadata, and ensure the Consistency Group is properly synchronized.”
:
Nutanix Prism Alerts Reference Guide, Version 6.0, Section: “Alert A130358 – ConsistencyGroupWithStaleEntities” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix Data Protection Troubleshooting”.

Before upgrading Objects Manager, the administrator must upgrade AOS to the latest version. AOS is the core operating system that runs on each node in a Nutanix cluster and provides the foundation for Objects Manager and Objects service. Upgrading AOS will ensure compatibility and stability for Objects components.
References: Nutanix Objects Administration Guide, Acropolis Operating System Upgrade Guide

The configuration that is required for an Objects deployment is to configure NTP servers on both Prism Element and Prism Central. 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. Configuring NTP servers on both Prism Element and Prism Central is required for an Objects deployment, because it ensures that the time settings are consistent and accurate across the Nutanix cluster and the Objects cluster, which can prevent any synchronization issues or errors. References: Nutanix Objects User Guide, page 9; Nutanix Objects Deployment Guide

Nutanix Volumes allows physical servers to boot from a volume group that is exposed as an iSCSI target from the data services IP. To ensure high availability and load balancing, multipath I/O (MPIO) is required on the physical server. Object buckets cannot be used for booting physical servers1. Reference: Nutanix Volumes Administration Guide1

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. Reference: Nutanix Objects User Guide, page 17; Nutanix Objects Solution Guide, page 9

Nutanix File Analytics, part of Nutanix Unified Storage (NUS), provides audit trails to track user activities within Nutanix Files shares. Audit trails include details such as who accessed a file, from where, and what actions were performed. The administrator needs to view the audit trails for 100 users, which requires filtering or grouping the audit data by relevant criteria.
Analysis of Options:
* Option A (Share Name): Correct. Audit trails in File Analytics can be filtered by Share Name, allowing the administrator to view activities specific to a particular share. Since the 100 users are connected to multiple shares, filtering by Share Name helps narrow down the audit trails to the shares being accessed by these users, making it easier to analyze their activities.
* Option B (Client IP): Correct. File Analytics audit trails include the Client IP address from which a user accesses a share (as noted in Question 14). Filtering by Client IP allows the administrator to track the activities of users based on their IP addresses, which can be useful if the 100 users are accessing shares from known IPs, helping to identify their read/write activities.
* Option C (Directory): Incorrect. While audit trails track file and directory-level operations,
“Directory” is not a standard filter option in File Analytics audit trails. The audit trails can show activities within directories, but the primary filtering options are more granular (e.g., by file) or higher- level (e.g., by share).
* Option D (Folders): Incorrect. Similar to “Directory,” “Folders” is not a standard filter option in File Analytics audit trails. While folder-level activities are logged, the audit trails are typically filtered by Share Name, Client IP, or specific files, not by a generic “Folders” category.
Selected Options:
* A: Filtering by Share Name allows the administrator to focus on the specific shares accessed by the 100 users.
* B: Filtering by Client IP enables tracking user activities based on their IP addresses, which is useful for identifying the 100 users’ actions across multiple shares.
Exact Extract from Nutanix Documentation:
From the Nutanix File Analytics Administration Guide (available on the Nutanix Portal):
“File Analytics Audit Trails allow administrators to filter user activities by various criteria, including Share Name and Client IP. Filtering by Share Name enables viewing activities on a specific share, while filtering by Client IP helps track user actions based on their source IP address.”
:
Nutanix File Analytics Administration Guide, Version 4.0, Section: “Using Audit Trails in File Analytics” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix File Analytics Audit Features”.