Pass the Nutanix Nutanix Certified Professional (NCP) NCP-US-6.5 Questions and answers with CertsForce

The Nutanix-enabled technology that meets these requirements is Objects – WORM with versioning. WORM (Write-Once Read-Many) is a feature that prevents anyone from modifying or deleting data in a bucket while the policy is active. WORM policies help comply with strict data retention regulations that mandate how long specific data must be stored. Versioning is a feature that keeps multiple versions of an object in a bucket whenever it is overwritten or deleted. Versioning policies help preserve previous versions of an object for backup or recovery purposes. By enabling WORM and versioning for an Objects bucket, the administrator can ensure that data is kept for two years without being deleted or overwritten. References: Nutanix Objects User Guide, page 17; Nutanix Objects Solution Guide, page 9

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

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, part of Nutanix Unified Storage (NUS), supports distributed shares that span multiple File Server Virtual Machines (FSVMs) for scalability (as discussed in Questions 16 and 30). The administrator has created a distributed share, accessed it via Windows Explorer (implying SMB protocol), and created folders. However, the folders cannot be renamed to meet the company’s naming convention, indicating a permissions issue.

Understanding the Issue:

Distributed Share: A distributed share in Nutanix Files is accessible via SMB or NFS and spans multiple FSVMs.

Windows Explorer (SMB): The administrator is using Windows Explorer, indicating the share is accessed via SMB.

Cannot Rename Folders: The inability to rename folders suggests a permissions restriction, likely because the user account used to create the folders does not have sufficient permissions to modify them (e.g., rename).

Company Naming Convention: The requirement to rename folders to meet a naming convention implies the administrator needs full control over the folders, which may not be granted by the current permissions.

Analysis of Options:

Option A (Use the Microsoft Shared Folder MMC Snap-in): Incorrect. The Microsoft Shared Folder MMC Snap-in (e.g., via Computer Management) allows management of SMB shares on a Windows server, but Nutanix Files shares are managed through the Files Console or FSVMs, not a Windows server. While this tool can view shares, it does not provide a mechanism to resolve renaming issues caused by permissions on a Nutanix Files share.

Option B (Use the Files MMC Snap-in and rename the folders): Incorrect. There is no “Files MMC Snap-in” for Nutanix Files. Nutanix Files is managed via the Files Console in Prism Central or through CLI/FSVM access. This option appears to be a misnomer and does not provide a valid solution for renaming folders.

Option C (Modify the read/write permissions on the created folders): Correct. The inability to rename folders in an SMB share is typically due to insufficient permissions. When the administrator created the folders via Windows Explorer, the default permissions (inherited from the share or parent folder) may not grant the necessary rights (e.g., “Modify” or “Full Control”) to rename them. The administrator should modify the permissions on the created folders to grant the required rights (e.g., Full Control) to the user account or group, allowing renaming to meet the company naming convention. This can be done via Windows Explorer (Properties > Security tab) or through the Files Console by adjusting share/folder permissions.

Option D (Modify the Files shares to use the NFS protocol): Incorrect. Switching the share to use NFS instead of SMB would require reconfiguring the share and client access, which is unnecessary and disruptive. The issue is with permissions, not the protocol, and SMB supports folder renaming if the correct permissions are set. Additionally, NFS may introduce other complexities (e.g., Unix permissions) that do not address the core issue.

Why Option C?

The inability to rename folders in an SMB share is a permissions issue. Modifying the read/write permissions on the created folders to grant the administrator (or relevant user/group) the necessary rights (e.g., Modify or Full Control) allows renaming, resolving the issue and enabling compliance with the company naming convention. This can be done directly in Windows Explorer or via the Files Console.

Exact Extract from Nutanix Documentation:

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

“If users cannot rename folders in an SMB share on Nutanix Files, this is typically due to insufficient permissions. Modify the read/write permissions on the affected folders to grant the necessary rights (e.g., Modify or Full Control) to the user or group. Permissions can be adjusted via Windows Explorer (Properties > Security) or through the Files Console by editing share or folder permissions.”