Tag NCP-US-6.5 test registration

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 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 two steps that the administrator should perform to resolve the connectivity issues with the domain controller servers are:
* Verify the DNS settings in Prism Element: DNS (Domain Name System) is a system that translates domain names into IP addresses. DNS settings are configurations that specify which DNS servers to use for resolving domain names. Verifying the DNS settings in Prism Element is a step that the administrator should perform, because it can help identify and correct any incorrect or outdated DNS server addresses or domain names that may cause connectivity issues with the domain controller servers.
* Verify the DNS entries for the given domain name: DNS entries are records that map domain names to IP addresses or other information. Verifying the DNS entries for the given domain name is another step that the administrator should perform, because it can help check and update any incorrect or outdated IP addresses or other information that may cause connectivity issues with the domain controller servers.
References: Nutanix Files Administration Guide, page 32; Nutanix Files Troubleshooting Guide

Smart DR in Nutanix Files, part of Nutanix Unified Storage (NUS), automates disaster recovery (DR) by replicating shares between primary and recovery file servers (e.g., using NearSync, as in Question 24). The administrator is using Smart DR to protect a Files share and needs seamless client redirection in the event of a failure, meaning clients should automatically connect to the recovery site without manual intervention.
Understanding the Requirement:
* Smart DR Protection: Smart DR replicates the Files share from the primary site to the recovery site, typically with the primary site in read-write (RW) mode and the recovery site in read-only (RO) mode (as seen in the exhibit for Question 24).
* Seamless Client Redirection: In a failure scenario (e.g., primary site down), clients should automatically redirect to the recovery site without needing to reconfigure their connections (e.g., changing the share path or IP address).
* Files Share Context: Clients typically access Files shares via SMB or NFS, using a hostname or IP address (e.g., \fileserver\share for SMB or fileserver:/share for NFS).
Analysis of Options:
* Option A (Create a reverse replication policy): Incorrect. A reverse replication policy would replicate data from the recovery site back to the primary site, typically used after failover to prepare for failback. This does not address seamless client redirection during a failure-it focuses on data replication direction, not client connectivity.
* Option B (Enable redirection in the protection policy): Incorrect. Smart DR protection policies define replication settings (e.g., RPO, schedule), but there is no “redirection” setting in the policy itself.
Client redirection in Nutanix Files DR scenarios is managed through external mechanisms like DNS, not within the protection policy.
* Option C (Update the AD and DNS entries): Correct. Seamless client redirection in Nutanix Files DR scenarios requires that clients can automatically connect to the recovery site without changing their share paths. This is achieved by updating Active Directory (AD) and DNS entries:
* DNS Update: The hostname of the file server (e.g., fileserver.company.com) should resolve to the IP address of the primary site’s File Server under normal conditions. During a failure, DNS is updated to point to the recovery site’s File Server IP address (e.g., the Client network IP of the recovery FSVMs). This ensures clients automatically connect to the recovery site without changing the share path (e.g., \fileserver.company.com\share continues to work).
* AD Update: For SMB shares, the Service Principal Name (SPN) in AD must be updated to reflect the recovery site’s File Server, ensuring Kerberos authentication works seamlessly after failover.This approach ensures clients are redirected without manual intervention, meeting the
“seamless” requirement.
* Option D (Activate protected shares on the recovery site): Incorrect. Activating protected shares on the recovery site (e.g., making them RW during failover) is a necessary step for failover, but it does not ensure seamless client redirection. Without updating DNS/AD, clients will not know to connect to the recovery site-they will continue trying to access the primary site’s IP address, requiring manual reconfiguration (e.g., changing the share path), which is not seamless.
Why Option C?
Seamless client redirection in a Nutanix Files DR scenario requires that clients can connect to the recovery site without changing their share paths. Updating AD and DNS entries ensures that the file server’s hostname resolves to the recovery site’s IP address after failover, and AD authentication (e.g., Kerberos for SMB) continues to work. This allows clients to automatically redirect to the recovery site without manual intervention, fulfilling the requirement for seamlessness.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Administration Guide (available on the Nutanix Portal):
“To ensure seamless client redirection during a Smart DR failover, update Active Directory (AD) and DNS entries. Configure DNS to resolve the file server’s hostname to the recovery site’s File Server IP address after failover, and update the Service Principal Name (SPN) in AD to ensure Kerberos authentication works for SMB clients. This allows clients to automatically connect to the recovery site without manual reconfiguration.”
:
Nutanix Files Administration Guide, Version 4.0, Section: “Smart DR Failover and Client Redirection” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix Files Disaster Recovery”.

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. References: Nutanix Files Administration Guide, page 28; Nutanix Files Solution Guide, page 7

The service that the administrator should investigate for this issue is Minerva-nvm. Minerva-nvm is a service that runs on each CVM and provides communication between Prism Central and Files services. Minerva-nvm also monitors the health of Files services and reports any failures or alerts to Prism Central. If Minerva-nvm is down on any CVM, it can affect the availability and functionality of Files services on that cluster. References: Nutanix Files Administration Guide, page 23; Nutanix Files Troubleshooting Guide The minerva_nvm service is the core service on FSVMs that manages Nutanix Files operations. If File server services are down, this service is the most likely culprit, as it handles all file system activities (e.g., share access, data I/O). Investigating minerva_nvm (e.g., checking its status, logs, or restarting it) is the first step to diagnose and resolve the issue.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Administration Guide (available on the Nutanix Portal):
“The minerva_nvm service is a critical component of Nutanix Files, running on each FSVM. It manages file system operations, including share access and data management. If File server services are down on a cluster, investigate the minerva_nvm service on the FSVMs, as its failure will cause shares to become inaccessible.”
:
Nutanix Files Administration Guide, Version 4.0, Section: “Troubleshooting Files Services” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix Files Service Troubleshooting”.

This metric indicates the number of active clients that are accessing the Files cluster via SMB protocol, which affects the performance of the Files cluster. NFS concurrent connections is also a relevant metric, but it is not the best answer, as it only applies to NFS protocol, not SMB. The quantity of SMB shares or NFS exports does not directly affect the performance of the Files cluster, as they are logical entities that do not consume resources. References: Nutanix Files Sizing Guide

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

Nutanix Objects supports directory services integration, which allows administrators to configure access keys based on directory and email-based users. This enables granular access control and security for buckets and objects. The administrator can configure directory services under the Access Keys section in Prism Central, and then generate access keys for internal users from the directory service and for the consultant from an email address2. References: Nutanix Objects Administration Guide2

The administrator can achieve this request by deleting and recreating a new Objects store with the updated name. Objects is a feature that allows users to create and manage object storage clusters on a Nutanix cluster.
Objects clusters can provide S3-compatible access to buckets and objects for various applications and users.
Objects clusters can be created and configured in Prism Central. However, once an Objects cluster is created, its name cannot be changed or edited. Therefore, the only way to change the name of an Objects cluster is to delete the existing cluster and create a new cluster with the updated name. References: Nutanix Objects User Guide, page 9; Nutanix Objects Solution Guide, page 8

The Minerva_cvm.log file contains information about the Minerva service, which is responsible for managing the FSVMs and their communication with Prism Central. The Minerva_cvm.log file can be used to troubleshoot issues related to Nutanix Files, such as duplicate IP address detection. The log file can be found in /home/nutanix/data/logs/minerva on any CVM in the cluster. Reference: Nutanix Support Portal – Troubleshooting Nutanix Files

The error log that the administrator should review to determine why the relay service is down is Cerebro.
ERROR. Cerebro is a service that runs on each FSVM and provides relay functionality for Data Lens. Relay service is responsible for collecting metadata and statistics from FSVMs and sending them to Data Lens via HTTPS. If Cerebro.ERROR log shows any errors or exceptions related to relay service, it can indicate that relay service is down or not functioning properly. References: Nutanix Files Administration Guide, page 23; Nutanix Data Lens User 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

Nutanix Files instances are deployed using File Server Virtual Machines (FSVMs) that run on the Nutanix cluster’s hypervisor (AHV, ESXi, or Hyper-V). The minimum resource requirements for deploying FSVMs are specified in the Nutanix Files documentation to ensure proper performance. These requirements are typically defined per FSVM, not per host, as FSVMs are virtual machines distributed across the cluster’s hosts.
According to the official Nutanix documentation:
* vCPUs: Each FSVM requires a minimum of 4 vCPUs to operate effectively.
* Memory: Each FSVM requires a minimum of 12 GiB of memory (RAM).
The question asks for the “minimum resources” required for deploying Files instances, and the options are framed as “per host.” However, in the context of Nutanix Files, resource requirements are specified per FSVM, as FSVMs are the entities consuming these resources. The options likely reflect a misunderstanding in the original question phrasing, but based on the standard Nutanix Files deployment requirements:
* 4 vCPUs per FSVM (option D) is correct, as this is the minimum vCPU requirement.
* 12 GiB of memory per FSVM (option C) is correct, as this is the minimum memory requirement.
Options A (8 vCPUs per host) and B (8 GiB of memory per host) do not align with the documented minimum requirements for FSVMs:
* 8 vCPUs is higher than the minimum requirement of 4 vCPUs per FSVM.
* 8 GiB of memory is lower than the minimum requirement of 12 GiB per FSVM.
Exact Extract from Nutanix Documentation:
“For a Nutanix Files deployment, each File Server Virtual Machine (FSVM) requires the following minimum resources:
* 4 vCPUs
* 12 GiB of RAMThese resources ensure that the FSVM can handle file service operations efficiently.”- Nutanix Files Deployment Guide, Version 4.0, Section: “System Requirements for Nutanix Files”
:
Nutanix Files Deployment Guide, Version 4.0, Section: “System Requirements for Nutanix Files” (Nutanix Portal).
Nutanix Certified Professional – Unified Storage (NCP-US) Study Guide, Section: “Nutanix Files Resource Requirements”.

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 application1. References:
Nutanix Files Administration Guide1