Nutanix NCP-US-6.5 Practice Test - Questions Answers

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. Reference: Nutanix Files Administration Guide, page 93; Nutanix File Analytics Deployment Guide

The prerequisite that must be performed before performing one-click hypervisor upgrades is to disable the anti-affinity rules on all FSVMs. Anti-affinity rules are rules that prevent two or more VMs from running on the same host at the same time. Anti-affinity rules can improve the availability and performance of FSVMs by distributing them across different hosts in a cluster. However, anti-affinity rules can interfere with one-click hypervisor upgrades, which require all VMs on a host to be migrated to another host before upgrading the host. Therefore, the administrator must disable the anti-affinity rules on all FSVMs before performing one-click hypervisor upgrades, and re-enable them after the upgrades are completed. Reference: Nutanix Files Administration Guide, page 22; Nutanix Files Upgrade Guide

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. Reference: Nutanix Files Administration Guide, page 23; Nutanix Files Troubleshooting Guide

The most likely cause of this issue is that the file server has been cloned. Cloning a file server is not a supported operation and can cause various problems, such as Data Lens not being able to enable or disable for the cloned file server. To avoid this issue, the administrator should use the scale-out feature to add more FSVMs to an existing file server, or create a new file server from scratch. Reference: Nutanix Files Administration Guide, page 28; Nutanix Files Troubleshooting Guide, page 11

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. Reference: Nutanix Files Administration Guide, page 31; Nutanix Files Solution Guide, page 6

The administrator should resolve this issue by using the Files MMC Snap-in and renaming the folders. The Files MMC Snap-in is a tool that allows administrators to manage Files shares and exports from a Windows machine. The administrator can use the Files MMC Snap-in to connect to a distributed share or export and rename the top-level directories that are hosted by different FSVMs. Renaming the directories from Windows Explorer will not work because Windows Explorer does not recognize the distributed nature of the share or export and will try to rename all directories on the same FSVM, which will fail. Reference: Nutanix Files Administration Guide, page 35; Nutanix Files MMC Snap-in User Guide

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. Reference: Nutanix Files Administration Guide, page 21; Nutanix Files Upgrade Guide

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

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. Reference: Nutanix Files Administration Guide, page 76; Nutanix Files Solution Guide, page 10