Changing thename of a Nutanix Files clusterinvolves updating theDNS name resolutionfor its FSVMs and VIPs. When the cluster’s name changes:

The underlying IP addresses (CVMs, FSVMs, VIPs)do not change.

However,DNS entriesassociated with the old cluster namebecome outdated, causing clients (including management interfaces and file share connections) to fail to resolve the new name to the correct IP addresses.

From the NUSA course troubleshooting section:

“After renaming a Files cluster, update the DNS entries to reflect the new name. Otherwise, clients and administrators will be unable to reach the cluster resources.”

Restarting CVMs or FSVMs does not update DNS entries.

Deleting active user sessions won’t fix the DNS resolution problem.

Therefore, to resolve theunreachabilityissue, the administrator must:

????Delete old DNS entriesfor the previous cluster name.

????Add new DNS entriesmapping the new cluster name to the same IPs of the FSVMs and VIP.

This ensures that all systems can properly resolve the new cluster name and reach the Nutanix Files services.

For quarantined files in Nutanix Files (via antivirus integration), administrators can:

Rescan: Re-check the file for malware.

Unquarantine: Restore the file if falsely flagged.

Delete: Permanently remove infected files to prevent risks.

Options A/B/C are invalid:

Alert (A): Not a file action; part of notification settings.

Report (B): Generates summaries but doesn’t act on files.

Reset (C): No such quarantine function.

To monitor key information about a Nutanix Files deployment, such asMalicious Clients,Vulnerable Shares, and alist of potential ransomware attack attempts, the administrator must deploy theFile Analytics VMon-premises. Nutanix File Analytics is a dedicated virtual machine that provides advanced monitoring and analytics for Nutanix Files, offering insights into security-related activities, including malicious client behavior, share vulnerabilities, and ransomware detection.

TheNutanix Unified Storage Administration (NUSA)course states, “File Analytics is a VM that must be deployed on-premises to provide detailed monitoring of Nutanix Files, including identifying Malicious Clients, Vulnerable Shares, and potential ransomware attack attempts through its analytics and anomaly detection features.” File Analytics includes dashboards and widgets that specifically highlight security risks, such as the Malicious Clients list (clients exhibiting suspicious behavior), Vulnerable Shares (shares with overly permissive access), and ransomware detection (based on file activity patterns like mass encryption or renaming).

TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further elaborates that “deploying the File Analytics VM enables administrators to monitor Nutanix Files for security threats, providing visibility into Malicious Clients, Vulnerable Shares, and ransomware attempts through its integrated analytics engine.” File Analytics runs locally within the Nutanix cluster, making it suitable for on-premises deployments and capable of operating in isolated environments like dark sites.

The other options are incorrect:

LCM dark site webserver: An LCM dark site webserver is used to host software updates for LCM in air-gapped environments but does not provide monitoring or analytics for Nutanix Files.

Prism Central: Prism Central provides centralized management and monitoring for Nutanix clusters but does not offer the specific security-focused analytics (e.g., Malicious Clients, ransomware detection) that File Analytics provides for Nutanix Files.

Data Lens: Nutanix Data Lens is a cloud-based service for data lifecycle management and analytics, primarily for Nutanix Objects and Files, but it focuses on tiering and data placement, not security monitoring like ransomware detection or malicious clients.

The NUSA course documentation emphasizes that “the File Analytics VM is the essential on-premises component for monitoring Nutanix Files, providing critical security insights such as Malicious Clients, Vulnerable Shares, and ransomware attack attempts.”