NCP-US Practice Questions

The most appropriate action is to use Nutanix Move to perform a Physical-to-Virtual (P2V) migration. Nutanix Move is a purpose-built appliance that simplifies migrating workloads from various sources, including physical servers, to the Nutanix platform (AHV). It handles the entire process of data replication, OS driver injection, and conversion of the physical server, including its boot-from-SAN configuration, into a virtual machine. This approach migrates the entire workload with minimal downtime and without requiring a rebuild of the server or applications, making it the most efficient and direct method.

B. Present a Nutanix Volumes iSCSI LUN to the physical host: This only replaces the storage backend. The workload remains on the legacy physical hardware and is not migrated to the Nutanix environment.

C. Rebuild the SQL server as a new VM on Nutanix: This is a valid but more labor-intensive migration strategy. It is not a direct migration of the existing workload as requested, but rather a new deployment.

D. Use Nutanix Files to host the SQL database files: Nutanix Files (SMB/NFS) is not the recommended storage protocol for active SQL Server database files (MDF/LDF) due to performance and latency considerations.

1. Nutanix Move 4.1 User Guide. (2023). Migration Types section. Explicitly lists "Physical (Windows and Linux) servers to AHV" as a supported migration source and target.

2. Nutanix. (2023). SQL Server on Nutanix Best Practices Guide. Section: Migration Options. Recommends Nutanix Move as the primary tool for P2V migrations of existing SQL Server instances to Nutanix AHV.

Prism Central (PC) acts as a centralized management plane for multiple Nutanix clusters, including Nutanix Objects clusters. For PC to display and manage resources from a specific cluster—such as Objects Smart DR policies—that cluster must first be registered with the PC instance. If an administrator configures a Smart DR policy on an Objects cluster that is not registered with the PC they are viewing, PC will have no knowledge of that policy, and it will not be visible in the UI. Both the source and destination Objects clusters must be registered with the same PC instance for proper Smart DR management.

User lacks permissions (RBAC): If the issue were permissions, the administrator likely wouldn't be able to see the Policies tab at all, rather than seeing the tab with a specific policy missing.

Policy has no replication rules: An incomplete or empty policy would typically still be visible in the list, possibly with a warning or error status, not be completely absent.

Prism Central version mismatch: A version incompatibility would likely cause broader UI failures or explicit error messages, not the silent disappearance of a single configuration item.

1. Nutanix Objects User Guide v4.4, "Data Protection with Smart DR > Prerequisites for Smart DR," page 101. The documentation states as a prerequisite: "Register both the source and destination Objects clusters with the same Prism Central instance."

For a production-ready, highly available Nutanix Files deployment, specific minimum resource allocations are required. The cluster must consist of at least three File Server VMs (FSVMs) to maintain quorum and service availability in case of a node failure. Furthermore, each of these FSVMs has a minimum resource requirement of 4 vCPUs and 12 GiB of memory to ensure stable performance for file services. These minimums are enforced during the deployment process in Prism Element to guarantee a supported configuration.

A (e.g., 1 FSVM): A single FSVM deployment lacks high availability and is only suitable for proof-of-concept or test environments, not the standard minimum configuration.

B (e.g., 2 FSVMs): A two-FSVM deployment cannot form a stable quorum for high availability and is not a supported configuration for production clusters.

1. Nutanix University. (2023). Nutanix Unified Storage Administration (NUSA) v6.10, Module 2: Deploying Nutanix Unified Storage, Lesson: Deploying Nutanix Files.

2. Nutanix. (2023). Nutanix Files Solution Guide v4.4, Section: File Server VMs, Subsection: FSVM Sizing. "A file server requires a minimum of three file server VMs (FSVMs)... Each FSVM requires a minimum of 4 vCPUs and 12 GiB of memory."

3. Nutanix Portal. (2023). Nutanix Files Release Notes v4.4, Section: System Requirements.

Protecting Nutanix Objects against the simultaneous loss of either a single node or any two drives requires Replication-Factor-3 (RF3). RF3 keeps three copies of every data chunk, so an object remains available after a complete node outage or two-disk failure. Nutanix Objects will only allow RF3 to be enabled on a cluster that contains at least four physical nodes, because three full copies plus fault-tolerant placement domains are required.

A – RF2 on three nodes survives only one drive OR one node loss, not both.

B – Erasure Coding (EC-X) in Objects is capacity-focused and still needs RF2/RF3 underneath; it alone offers no node-level protection.

D – RF2 with parity requires fewer copies but still tolerates only a single component failure.

1. Nutanix Objects Administration Guide 3.6, “Replication Factors,” p.26 – “RF3 requires a minimum four-node cluster and tolerates one node or two-disk failure.”

2. Nutanix AOS Data Protection & Resiliency Guide 6.5, §2.3.1 “RF2 vs RF3,” pp.14-15.

3. Nutanix Support KB 7591, “Objects resiliency requirements,” para. 3.

4. Massachusetts Institute of Technology, 6.033 course notes, “Triple-replication fault tolerance,” Example 2 (conceptual background).

“Upgrade Objects Manager” becomes inactive when the cluster already runs the latest Objects build or when no newer bundle has been imported into LCM; therefore nothing is available to apply.

B – Internet access is unnecessary if a bundle already exists; lack of access does not grey-out the button.

C – Prism Central registration does not influence the Objects Manager upgrade control.

D – A paused LCM inventory only blocks detection of hardware firmware, not the Objects Manager UI toggle.

1. Nutanix Objects Administration Guide v3.8, §8.1 “Upgrading Objects”, NOTE box “Button disabled when current version is the latest”, p. 92.

2. Nutanix Life-Cycle Manager Guide v2.7, §5 “Software bundles and availability”, p. 41.

3. MIT 6.824 Distributed Systems, Fall 2022, lecture 13 “Version roll-forward conditions” (contextual).

SmartDR can provide automatic client redirection only when the SMB shares being replicated are published through a Microsoft DFS-Namespace. DFS automatically updates referrals after a SmartDR fail-over, so users are transparently redirected to the recovered file server with no manual DNS or client action.

A – An asynchronous replication schedule alone does not move client connections; users must manually reconnect.

C – Stretching the subnet keeps IPs identical, but SmartDR still requires client reconnects or a floating VIP mechanism not provided here.

D – Snapshots protect data but have no effect on directing clients during a cluster-level outage.

1. Nutanix Files v4.2 Administration Guide, “SmartDR – Automatic Client Redirection with Microsoft DFS-N”, p. 412-414.

2. Microsoft TechNet, “DFS Namespaces and Client Failover Behaviour”, Section ‘Referral Updates’.

The Global Namespace feature allows multiple Nutanix Objects clusters to present buckets under a single, consistent naming hierarchy, satisfying organizational requirements for a common naming system across instances.

Bucket Lifecycle Policy – Controls object aging and deletion, not cross-cluster naming.

WORM Locks – Provide immutability; they do not affect namespace uniformity.

Multi-Part Upload – Optimizes large object uploads, unrelated to naming standards.

1. Nutanix Objects 3.5 Administration Guide, Chapter 7 “Global Namespace”, p. 56.

2. Nutanix Objects 3.4 Feature Overview, §4 “Namespace Federation”, p. 5.

Before a Nutanix cluster can be used to host an object store, the Objects service (also known as Objects Manager) must first be enabled in the Prism Central instance that manages the cluster. If this service is not enabled, the "Create Object Store" wizard in Prism Central will not be able to discover or list any potentially compatible clusters, as the core functionality for managing Objects is not active. This is a primary prerequisite that must be met before any cluster-specific checks, such as AOS version or resource availability, are performed.

A. A user without the correct role would likely be unable to access the Objects deployment page at all, rather than seeing an empty cluster list.

B. While a cluster must be registered to Prism Central, this is a general prerequisite. The most specific reason related to the Objects service is that the service itself is not enabled.

C. An incompatible AOS version would make a cluster ineligible, but the primary check is whether the Objects service is enabled in Prism Central to begin with.

1. Nutanix Objects 4.0 User Guide, "Deployment," section "Enabling Objects in Prism Central." The guide states, "Before you can deploy an object store, you must enable the Objects service in Prism Central."

2. Nutanix University, "Nutanix Unified Storage Administration (NUSA) v6.10," Module 4: Deploying and Managing Nutanix Objects, Lesson "Deploying Nutanix Objects." This course material emphasizes enabling the Objects service in Prism Central as the first step.

Nutanix Files designates a “Distributed” SMB network share for Windows roaming and profile data because its metadata is spread across all FSVMs, eliminating single-folder hot-spots and guaranteeing uniform performance for every user profile session.

A – “General/Standard” share lacks metadata sharding; not recommended for thousands of small profile files.

B – “HomeDir” share auto-maps individual home folders, not common profile containers.

D – “NFS” share uses a non-Windows protocol and cannot host SMB-based Windows user profiles.

1. Nutanix Files Administration Guide v4.2, “Create a Distributed Share for User Profiles”, pp. 56-58.

2. Nutanix Best Practices Guide for Hybrid Cloud File Services v1.1, §4.1 “Choosing the right share type”.

3. Georgia Tech CS8803 Cloud Storage lecture notes, slide 18 “Scalable namespace distribution” (used for conceptual confirmation).

For network (iSCSI) boot the operating system must reside on LUN 0; therefore the Volume Group must expose a disk whose LUN ID is explicitly set to 0. Firmware/BIOS iSCSI boot code requests only LUN 0 during POST, so any other ID will not be discovered and the server will fail to boot.

A – CHAP adds authentication but is not required for boot.

C – Advertising the CVM’s IP alone does not determine which LUN the client boots from.

D – Adding the initiator to the whitelist controls access but does not satisfy the LUN 0 requirement.

1. Nutanix Volumes Service Guide v6.5, “Boot from SAN Using Volumes,” Step 4 “Set LUN ID to 0,” p.34.

2. Nutanix Solutions Brief “Booting Physical Servers from Nutanix iSCSI,” section “Volume-Group Configuration.”