The Nutanix Certified Professional - Unified Storage (NCP-US) v6.10 (NCP-US-6.10)

Directory services integration (e.g., Active Directory)  is mandatory for SMB shares to:

Authenticate users.

Apply access controls (ACLs).

Enable Kerberos-based security. Without this, SMB shares cannot be accessed by domain-joined clients.

Option B : Prism Central registration enables central management but isn't a share prerequisite.

Option C : afs infra.start is an invalid command.

Option D : Password policies are enforced via directory services but not a standalone prerequisite.

Legal Hold in Nutanix Objects is a feature designed for compliance and regulatory use cases, ensuring that specific objects (files) cannot be deleted or modified for an indefinite period, even if WORM (Write Once Read Many) policies exist.

Here’s how it matches the scenario:

Indefinite Lock:

Legal Hold ensures that once applied, the object is locked indefinitely .

Unlike WORM retention, which is based on a fixed duration (like days/months) , Legal Hold has no expiration until an authorized administrator explicitly removes it.

Authorized Removal Only:

Only users with specific Legal Hold management permissions can remove the lock, maintaining compliance and governance integrity.

The NUSA course materials emphasize:

“Legal Hold is a compliance feature that prevents deletion or modification of specific objects. It can only be lifted by authorized administrators, ensuring that the data remains immutable as long as required by legal or regulatory processes.”

The other options:

WORM versioning — locks data for a fixed retention period ; it does not provide indefinite locking.

Data Lens Ransomware Protection — focuses on monitoring for anomalies, not explicit file locking.

Blocked File Types for Files — prevents certain files from being uploaded but does not lock already uploaded files.

Thus, to indefinitely lock a file in Nutanix Objects, the administrator should use Legal Hold .

To support workloads with small I/O operations in Nutanix Files, the share should be configured with the Random workload type. Small I/O operations, typically less than 64 KB, are characteristic of random I/O patterns, which are common in workloads like databases, virtual desktops, or applications with frequent small read/write operations. Nutanix Files allows administrators to optimize share performance by selecting a workload type that aligns with the I/O pattern.

The Nutanix Unified Storage Administration (NUSA) course states, “Nutanix Files supports configuring shares with a Random workload type to optimize performance for small I/O operations, which are typical of random access patterns.” The Random workload type adjusts internal optimizations, such as caching and data placement, to better handle the characteristics of small, non-sequential I/O operations, improving performance for such workloads.

The Nutanix Certified Professional - Unified Storage (NCP-US) study guide further elaborates that “the Random workload type in Nutanix Files is designed for shares hosting applications with small I/O sizes, ensuring efficient handling of random read and write operations.” This contrasts with sequential workloads, which involve larger, contiguous I/O operations, such as those seen in media streaming or backups.

The other options are incorrect:

Sequential : The Sequential workload type is optimized for large, contiguous I/O operations, not small I/O, making it unsuitable for this scenario.

Compression : Compression is a data reduction feature, not a workload type, and does not directly address I/O performance optimization.

Default : The Default workload type applies a balanced configuration but does not specifically optimize for small I/O operations like the Random type does.

The NUSA course documentation emphasizes that “configuring a share with the Random workload type ensures optimal performance for workloads with small I/O, aligning with the random access patterns of such applications.”

The Nutanix Files deployment process requires two logical networks for operational separation and performance:

Client Network:

“This is the network through which client devices (Windows, Linux) connect to the file shares hosted by the FSVMs. It ensures that user data access is isolated from management traffic.”

Management Network:

“This network is used for communication between FSVMs and Prism Central/Prism Element for administrative tasks, health monitoring, and management APIs.”

The Storage Network is not a separate network for Nutanix Files—it uses the cluster’s existing storage network (backed by the Nutanix DSF). The Overlay Network concept is specific to container environments, not Nutanix Files deployments.

To migrate physical SQL workloads from a legacy SAN platform where hosts boot from SAN to a Nutanix environment, the administrator can use Nutanix Volumes to enable booting over iSCSI . Nutanix Volumes is a block storage solution that provides iSCSI-based storage, allowing external hosts (such as physical servers) to access Nutanix storage as block devices. This is ideal for replacing SAN-based boot volumes, as it supports the same iSCSI protocol used in traditional SAN environments.

According to the Nutanix Unified Storage Administration (NUSA) course, Nutanix Volumes enables external hosts to connect to Nutanix storage via iSCSI, which can be used for boot volumes or data volumes. The course emphasizes that “Nutanix Volumes supports iSCSI boot for physical servers, making it a suitable solution for migrating workloads from legacy SAN environments to Nutanix.” This allows the administrator to configure the physical SQL servers to boot from iSCSI targets provisioned on Nutanix Volumes, leveraging the Nutanix cluster’s storage resources.

The Nutanix Certified Professional - Unified Storage (NCP-US) study guide further details that Nutanix Volumes can be configured to present iSCSI LUNs to physical hosts, which can be used for both operating system boot and application data storage. For the SQL workloads, the administrator can create iSCSI targets on Nutanix Volumes, configure the physical hosts’ iSCSI initiators to connect to these targets, and migrate the boot and data volumes from the legacy SAN to Nutanix.

The other options are not suitable for this task:

Boot using PXE protocol with Nutanix Files : Nutanix Files is a file storage solution that supports SMB and NFS protocols, not PXE (Preboot Execution Environment) booting. PXE is typically used for network-based OS installation, not for booting SQL workloads or replacing SAN-based boot volumes.

Boot using the NFS protocol with Nutanix Files : Nutanix Files supports NFS for file sharing, but NFS is not designed for booting physical servers. It is used for file-level access, not block-level access required for boot volumes.

Boot using Nutanix Object stores : Nutanix Objects is an object storage solution designed for S3-compatible APIs, not for block or file-based booting. It is unsuitable for hosting bootable volumes or SQL workloads.

The NUSA course documentation highlights that “Nutanix Volumes provides a seamless migration path for SAN-based workloads, including boot-from-SAN configurations, by leveraging iSCSI to present storage to physical hosts.” This makes it the only viable option for the described migration task.

Access Based-Enumeration (ABE) is a feature in Nutanix Files that controls whether users can see folders and files for which they do not have access permissions. When ABE is enabled:

Users will only see the folders/files they are authorized to access.

Items for which they have no permissions will be hidden from view.

The NUSA course describes this feature:

“Access Based-Enumeration (ABE) ensures that users browsing a share will only see folders and files that they have permission to access, improving security and minimizing confusion.”

Thus, ABE is the precise feature for controlling user visibility of SMB shares based on permissions.

When creating a new Nutanix Objects instance via Prism Central , Prism Central must have completed synchronization with the Prism Element cluster(s). This synchronization ensures that:

Cluster details and resources (such as available storage, network configurations, and capacity) are properly displayed in Prism Central.

Prism Central can create and manage Object Stores based on accurate data from the registered cluster.

From the NUSA deployment module:

“After registering Prism Element clusters in Prism Central, there is an initial synchronization process that must complete before clusters appear in workflows such as object store creation.”

The other options:

Manual sync is not required; Prism Central automatically synchronizes after registration.

CVM restarts are not part of the normal registration or synchronization process.

Object stores can indeed be added via Prism Central once the sync is complete.

Therefore, the administrator should wait for Prism Central and Prism Element to finish synchronizing before proceeding.

The most likely cause in this scenario is that the Windows VM’s iSCSI Initiator IQN (iSCSI Qualified Name) was not added to the client allowlist for the newly created Volume Group (VG) on the Nutanix cluster.

How this works in Nutanix Unified Storage:

When creating a VG, Nutanix requires you to define which iSCSI initiators (by IQN) are allowed to connect to it.

If the Windows VM’s IQN is not on the allowlist , Nutanix will not present the LUN (Volume Group) to that initiator, even though the target portal (DSIP) itself is reachable.

This is a common step emphasized in the NUSA and NCP-US materials:

“After creating a Volume Group, administrators must add the iSCSI initiator IQNs of client VMs to the client allowlist. Without this, the initiator can discover the target portal (via DSIP) but will not see the actual LUN (Volume Group).”

The other options:

B. Volume Group size too large : Windows Server 2022 fully supports 1TiB+ volumes if properly configured.

C. Rebooting the VM : This does not resolve missing allowlist entries.

D. iSCSI initiator service not started : If this were the case, the discovery portal itself would not be visible.

Thus, the administrator must:

???? Retrieve the IQN of the Windows VM (from the iSCSI Initiator Properties > Configuration tab).

???? Add that IQN to the Nutanix Volume Group’s client allowlist in Prism.

This will resolve the missing LUN (Volume Group) discovery.

In Nutanix Files, SMB load balancing across multiple File Server VMs (FSVMs) is achieved by enabling the Distributed configuration. When the distributed option is enabled for a share, the file service can actively balance the load across multiple FSVMs, optimizing performance and client access.

The NUSA course states:

“The Distributed option for SMB shares allows load balancing of client connections across multiple FSVMs. This improves performance and ensures more efficient use of resources.”

The other options (Disaster Recovery, Multiple Copies, High Availability) are related to resilience and data protection but not directly to load balancing of SMB shares.