Free Nutanix NCP-MCI-6.10 Practice Exam with Questions & Answers | Set: 4

The Nutanix data protection guide specifies that NearSync replication provides an RPO between 1 and 15 minutes, which is the lowest RPO available for standard asynchronous-based replication models. The documentation further states that NearSync is the supported method for achieving sub-hour RPO on one- and two-node clusters. Asynchronous replication has a minimum RPO of 60 minutes and therefore cannot be used for lowest RPO requirements. While scheduling intervals such as 1–15 minutes appear similar, Nutanix notes that these intervals are only achievable under the NearSync replication mode. Therefore, selecting NearSync is the required configuration to meet the goal of achieving the lowest RPO.

Nutanix performance troubleshooting guidelines emphasize the importance of adequate vCPU resources when diagnosing single-VM performance issues. The documentation states that “under-provisioned CPU is a primary cause of perceived storage latency and throughput limitations, as storage I/O processing and VirtIO-SCSI operations depend heavily on VM compute resources.”

Running a Windows Server VM with only one vCPU significantly constrains its ability to queue and process disk I/O, handle interrupts, and run kernel-level services. This is especially true when multiple disks are attached. Adding a second controller does not solve underlying CPU bottlenecks. Adjusting br0 TCP settings is not applicable to storage. Increasing CVM resources is unnecessary because the problem is isolated to a single VM while the cluster and other VMs perform normally.

Therefore, increasing vCPU allocation is the required corrective action.

When creating a storage container in Nutanix, the administrator must configure the correctcapacity settings:

Option A (Prism Element with Advertised Capacity of 100 GiB) is correct:

Advertised Capacitydefineslogical limitsfor the container (i.e., how much space it reports as available).

Inline Compressioncan be enabled directly in Prism Element.

Option B (Create in Prism Element without Advertised Capacity)is incorrect:

Without specifyingAdvertised Capacity, the container may consume unlimited storage.

Option C (Create in Prism Central with Reserved Capacity)is incorrect:

Reserved Capacityapplies toQuality of Service (QoS) policies, not storage limits.

Option D (Create in Prism Central without capacity limits)is incorrect:

Prism Central can manage storage but does not directly enforceRF1 and compression policies.

The requirement states:

• Custom apps use Volume Groups

• VM + VG must remain consistent together

• Lowest possible RPO is required (RPO → 0)

• Must survive cluster failure

Nutanix data protection documentation clearly states:

“Synchronous replication provides an RPO of zero by ensuring every write is committed on both sites before acknowledgement.”

Additionally:

“When protecting application VMs using Volume Groups, both the VM and the Volume Group must be placed in the same Consistency Group to ensure write-order fidelity and to preserve database or application integrity during failover.”

This is critical because Volume Groups operate at the block layer, and placing them in separate groups breaks atomic write-order correctness.

Option analysis:

A. Metro AHV provides HA-style zero RPO but is not the required mechanism here because the question specifically references protection policies and VGs, which Metro does not orchestrate in the same way.

B. Synchronous replication alone is not sufficient unless VMs and VGs are inside the same consistency group.

C. This is the correct and complete solution: synchronous replication + consistency grouping ensures RPO0 and atomic updates.

D. NearSync has RPO 1–15 minutes, not the lowest possible RPO.

Therefore, placing both VMs and VGs in the same consistency group under Synchronous Replication is the correct method.

Nutanix Life Cycle Manager (LCM) has built-in workflow controls that allow administrators to pause or stop active upgrade sessions. The documentation states:

“Administrators can use the Stop Update option in the LCM UI to halt further job progression. This safely stops the upgrade pipeline without disrupting already-applied updates.”

More internal behavior details:

Stop Update immediately prevents LCM from starting additional node or component upgrades.

It safely terminates queue execution while maintaining cluster consistency.

It does not require command-line interaction or service restarts.

Using .py scripts is not recommended and is reserved for engineering workflows. Restarting Genesis or canceling tasks via ecli may interrupt LCM activities but do not cleanly stop the scheduled upgrade workflow.

The supported and correct control method is the built-in Stop Update button.

A single vCPU is likely causing a bottleneck, limiting the VM’s ability to process I/O requests efficiently.

Option D (Increase the VM’s number of vCPUs) is correct:

Windowsrequires sufficient CPU resourcesto handle disk and network operations.

Adding more vCPUs allows the VM to process more I/O operations simultaneously, improving performance.

Option A is incorrect:

AdditionalvSCSI controllers are only useful for very high disk I/O workloads.

Option B is incorrect:

Balance-TCP applies to network traffic, not storage performance.

Option C is incorrect:

CVM resources do not directly affect individual VM performance.

Nutanix describes a special process for updating golden images or templates without modifying the original source object directly. The documentation states:

“Complete Guest OS Update creates a temporary, cloned instance of the template, boots it, and allows administrators to patch or update the operating system. Once updates are applied, the system recomposes the template with the modifications.”

This process ensures that templates remain clean and version-controlled while still allowing regular OS patching operations. Other options such as Create VM from Template merely instantiate running VMs and do not update the template source. Update Guest OS and Update Configuration refer to VM-level settings but do not create a temporary working copy for template lifecycle management.

Thus, Complete Guest OS Update is the correct feature.

Nutanix platform timing guidelines state that Prism Central requires accurate clock synchronization to ensure proper authentication, event logging, certificate validation, and cluster orchestration. The documentation details that “NTP must be configured to a reachable, reliable time source, and best practice is to configure Prism Central to use an external, independent, standards-based NTP server.”

Using a Domain Controller is acceptable only if the DC itself is properly synchronized with an authoritative external NTP source, but Nutanix strongly recommends specifying the external source directly in Prism Central for consistency across hypervisors and multi-cluster environments. Adding a DNS server IP is not time-related. Adding a hostname is valid only if it resolves to a functioning NTP server, but the question requires the correct method, not the acceptable syntax.

Therefore, selecting an external NTP server is the correct and recommended configuration.