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

Nutanix Files, part of Nutanix Unified Storage (NUS), allows administrators to manage file shares through the Files Console, which is accessible via Prism Central. A share in Nutanix Files can have a maximum capacity (quota) defined to limit its storage usage. To increase this capacity, the administrator must modify the share's settings.
Analysis of Options:
* Option A (Select the Settings tab, Click Change): Incorrect. The Settings tab in the Files Console is used for general file server settings (e.g., AD integration, global configurations), not for modifying individual share properties like capacity.
* Option B (Select the Shares tab, Click Modify): Correct. To increase the maximum capacity of a share, the administrator should navigate to the Shares tab in the Files Console, select the share, and click Modify (or Edit, depending on the version). This opens a dialog where the share's quota (maximum capacity) can be adjusted.
* Option C (Select the Settings tab, Click Rename): Incorrect. Renaming a share under the Settings tab does not affect its capacity. The Settings tab is not the correct location for share-specific changes like capacity adjustments.
* Option D (Select the Shares tab, Click Update): Incorrect. While the Shares tab is the correct location, "Update" is not a standard action in the Files Console for modifying share properties. The correct action is "Modify" or "Edit," as in option B.
Why Option B?
The Shares tab in the Files Console is where administrators manage individual shares, including their properties like maximum capacity (quota). The Modify (or Edit) action allows the administrator to adjust the share's quota, increasing its maximum capacity as requested.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Administration Guide (available on the Nutanix Portal):
"To modify the maximum capacity (quota) of a share, navigate to the Shares tab in the Files Console. Select the share you want to modify, and click Modify. In the dialog, adjust the quota settings to increase the maximum capacity as needed, then save the changes."
:
Nutanix Files Administration Guide, Version 4.0, Section: "Managing Shares in Files Console" (Nutanix Portal).
Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Section: "Nutanix Files Share Management".

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

Nutanix Files, part of Nutanix Unified Storage (NUS), uses File Server Virtual Machines (FSVMs) to manage file services (e.g., SMB, NFS). Each FSVM runs on a node in the Nutanix cluster, and the number of connections per node impacts the resource requirements, particularly memory (RAM), for the FSVMs. The administrator needs to size the memory for a Files instance where each node will handle an average of 4,000 connections.
Sizing Guidelines:
Nutanix provides sizing guidelines for Files deployments based on the number of connections per FSVM (and thus per node, assuming one FSVM per node, which is the default configuration). The memory requirements scale with the number of connections to ensure performance and stability:
* The minimum memory per FSVM is 12 GiB (as noted in Question 2), which supports up to 1,000 connections.
* For higher connection counts, Nutanix recommends increasing the memory proportionally.
According to Nutanix documentation:
* Up to 1,000 connections: 12 GiB RAM per FSVM.
* 1,000 to 2,000 connections: 24 GiB RAM per FSVM.
* 2,000 to 4,000 connections: 48 GiB RAM per FSVM.
* 4,000 to 8,000 connections: 96 GiB RAM per FSVM.
Since the question specifies 4,000 connections per node, and assuming one FSVM per node (standard deployment), the FSVM on each node needs to handle 4,000 connections. Based on the sizing guidelines:
* 4,000 connections fall into the 4,000 to 8,000 range, requiring 96 GiB RAM per FSVM.
* Since each node hosts one FSVM, this translates to 96 GiB RAM per node dedicated to the FSVM.
Analysis of Options:
* Option A (32 GiB RAM per node): Incorrect. 32 GiB RAM per node is sufficient for up to 2,000 connections (24 GiB for the FSVM, plus some overhead), but it is insufficient for 4,000 connections, which require 96 GiB.
* Option B (40 GiB RAM per node): Incorrect. 40 GiB RAM per node is still too low for 4,000 connections, as it falls short of the 96 GiB recommended for this connection range.
* Option C (96 GiB RAM per node): Correct. 96 GiB RAM per node aligns with Nutanix's sizing guidelines for an FSVM handling 4,000 to 8,000 connections, ensuring the Files instance can manage the expected load efficiently.
* Option D (128 GiB RAM per node): Incorrect. While 128 GiB RAM per node would work, it exceeds the recommended sizing for 4,000 connections. Nutanix recommends 96 GiB for up to 8,000 connections, and 128 GiB is typically reserved for even higher connection counts (e.g., >8,000) or additional workloads on the node. The question asks for the "proper" sizing, which is the minimum recommended for the given load, making 96 GiB the correct choice.
Why Option C?
For 4,000 connections per node, Nutanix recommends 96 GiB RAM per FSVM (one FSVM per node), which translates to 96 GiB RAM per node dedicated to the FSVM. This ensures the Files instance can handle the connection load without performance degradation, aligning with Nutanix's sizing guidelines.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Sizing Guide (available on the Nutanix Portal):
"For Nutanix Files deployments, memory sizing depends on the number of connections per FSVM. For 4,000 to 8,000 connections, allocate 96 GiB of RAM per FSVM. Assuming one FSVM per node, this translates to
96 GiB RAM per node dedicated to the FSVM to ensure optimal performance." Additional Notes:
* The question assumes one FSVM per node, which is the default configuration for Nutanix Files unless otherwise specified. If multiple FSVMs were on a single node, the total RAM would need to be adjusted, but the question's phrasing ("per node") aligns with the standard one-FSVM-per-node deployment.
* The 96 GiB RAM is for the FSVM itself; the node may require additional RAM for other workloads (e.
g., CVM, VMs), but the question focuses on the Files instance's memory sizing, making 96 GiB the correct answer.
:
Nutanix Files Sizing Guide, Version 4.0, Section: "Memory Sizing for Nutanix Files" (Nutanix Portal).
Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Section: "Nutanix Files Sizing and Performance".

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