Nutanix NCP-US-6.5 Exam With Confidence Using Practice Dumps

Nutanix Files provides a built-in ransomware prevention feature that allows administrators to block malicious file signatures from being written to the file system. However, this feature has a limit of 300 signatures per share or export. If the list of malicious file signatures to block is greater than 300, a third-party solution is recommended2

Neither File Analytics nor Data Lens supports signature-based ransomware prevention with a large list of malicious file signatures (300+). Signature-based blocking requires a dedicated security solution with a robust signature database, which third-party tools are designed to handle. Nutanix Files supports integration with such tools, making a third-party solution the best choice for this requirement.

Exact Extract from Nutanix Documentation:

From the Nutanix Files Administration Guide (available on the Nutanix Portal):

“For advanced ransomware prevention requiring signature-based blocking, such as when the list of malicious file signatures exceeds 300, Nutanix Files supports integration with third-party security solutions. These solutions can handle large signature databases and perform file scanning/blocking at scale, complementing the behavioral detection capabilities of File Analytics and Data Lens.”

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 Objects, part of Nutanix Unified Storage (NUS), is deployed and managed through Prism Central (PC), which provides a centralized interface for managing multiple Prism Element (PE) clusters. When deploying Objects or adding multi-cluster support to an Object Store, the administrator selects a PE cluster and associated subnets from drop-down lists in the Prism Central UI. If these drop-down lists are empty or show an error, it indicates an issue with visibility or access to the clusters or subnets.

Analysis of Options:

Option A (The logged-in user does not have access to any Prism Central): Correct. Prism Central is required to manage Nutanix Objects deployments and multi-cluster configurations. If the logged-in user does not have access to any Prism Central instance (e.g., due to RBAC restrictions or no PC being deployed), they cannot see any PE clusters or subnets in the UI, as Prism Central is the interface that aggregates this information. This would result in empty drop-down lists for clusters and subnets, as well as during multi-cluster addition for the Object Store.

Option B (The logged-in user does not have access to any subnets on the allowed Prism Central): Incorrect. While subnet access restrictions could prevent subnets from appearing in the Subnets drop-down, this does not explain why the Cluster drop-down is empty or why no clusters are listed during multi-cluster addition. The issue is broader—likely related to Prism Central access itself—rather than subnet-specific permissions.

Option C (The administrator has just created an access policy granting user access to Prism Element): Incorrect. Granting access to Prism Element directly does not affect visibility in Prism Central’s UI. Objects deployment and multi-cluster management are performed through Prism Central, not Prism Element. Even if the user has PE access, they need PC access to see clusters and subnets in the Objects deployment workflow.

Option D (The administrator has just created an access policy denying user access to a subnet in Prism Element): Incorrect. Denying access to a subnet in Prism Element might affect subnet visibility in the Subnets drop-down, but it does not explain the empty Cluster drop-down or the inability to see clusters during multi-cluster addition. Subnet access policies are secondary to the broader issue of Prism Central access.

Why Option A?

The core issue is that Prism Central is required to display PE clusters and subnets in the UI for Objects deployment and multi-cluster management. If the logged-in user does not have access to any Prism Central instance (e.g., they are not assigned the necessary role, such as Prism Central Admin, or no PC is registered), the UI cannot display any clusters or subnets, resulting in empty drop-down lists. This also explains why no clusters are listed during multi-cluster addition for the Object Store, as Prism Central is the central management point for such operations.

Exact Extract from Nutanix Documentation:

From the Nutanix Objects Deployment Guide (available on the Nutanix Portal):

“Nutanix Objects deployment and multi-cluster management are performed through Prism Central. The logged-in user must have access to Prism Central with appropriate permissions (e.g., Prism Central Admin role) to view Prism Element clusters and subnets in the deployment UI. If the user does not have access to Prism Central, the Cluster and Subnets drop-down lists will be empty, and multi-cluster addition will fail to list available clusters.”