Nutanix Updated NCP-MCI-6.10 Exam Questions and Answers by karim

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.

For optimal Disaster Recovery performance, new nodes must match or exceed the storage performance of existing nodes.

Option A (New node must have at least 2 SSDs) is correct:

Since the G7 nodes havetwo SSDs, replacing G5 nodes withat least 2 SSDsensuresconsistent SSD cache and performance.

Option B is incorrect:

G7 or G8 nodes may help, but storage performance is more critical for DR.

Option C is incorrect:

CPU core count does not impact DR storage performance as much as SSD capacity.

Option D is incorrect:

Hybrid nodes are already in use, but SSDs must match for performance balance.

Nutanix Application Discovery relies on a combination of Prism Central services and in-guest sensors that collect application metadata, communication patterns, and dependency maps. The internal documentation lists these specific prerequisites before Application Discovery can be enabled:

“Prism Central must have access to the Internet for sensor downloads, signature updates, and metadata service communication.”Application Discovery uses cloud-based metadata to identify applications and services. Without Internet access, Prism Central cannot retrieve application profiles, updated signatures, and dependency mapping definitions.

“The Network Controller service must be enabled to allow flow-level inspection and communication tracking between VMs.”Application Discovery integrates directly with Nutanix Flow’s Network Controller to observe traffic flows, which is required for dependency mapping. Without Network Controller enabled, Prism Central cannot monitor or analyze traffic between workloads.

The documentation clarifies that generating API keys is not required to activate Application Discovery, and sufficient Prism Central resources are already assumed as stated in the question.

Therefore, the required prerequisites are Internet connectivity and enabling the Network Controller.