NCP-MCI-6-10 Sample Questions & Answers

This is True. The Witness is designed to handle this specific split-brain scenario. If the secondary site can reach the Witness but the primary site cannot (due to a primary site failure), the Witness will instruct the secondary site to take ownership of the protected container. This ensures business continuity even during a complete primary site outage.

This is the most comprehensive and flexible solution. By categorizing the VMs and applying a QoS policy in Prism Central, the administrator can set a guaranteed number of CPU cycles (using CPU reservation) and a minimum IOPS value for the database VMs. This prevents resource starvation from 'bully' VMs without statically assigning them to hosts, thus maintaining cluster flexibility. Flash Mode is already active on an all-flash cluster, and reserving storage capacity doesn't guarantee performance. VM-Host affinity is too rigid and violates the 'not pinning VMs' requirement.

The Life Cycle Manager (LCM) framework is designed to automate the entire upgrade process in a non-disruptive, rolling fashion. When an administrator initiates a firmware update through LCM, the framework automatically handles putting the node into maintenance mode, live-migrating VMs, shutting down the CVM if necessary, applying the updates, restarting services, and exiting maintenance mode before moving to the next node. Manual intervention as described in the other options is not required and circumvents the built-in safety and automation of LCM.

The correct and recommended approach for creating a logically and potentially physically separate network is to create a new virtual bridge (e.g., br1). This new bridge will then have its own bond (e.g., bond1) composed of the 1GbE physical NICs. VMs that require access to the backup network can then have a vNIC attached to a virtual network created on br1. This ensures complete separation from the primary br0 network. Adding NICs of different speeds to the same bond is not recommended, and adding a second bond to the same bridge does not provide the desired logical separation.

A 'Test Failover' creates a temporary, isolated network bubble for the recovered VMs. The administrator must specify a test network (VLAN) in the recovery plan's network mappings. If this specified VLAN does not exist or is not configured on the hosts at the recovery site, the VMs cannot be attached to a network and will fail to power on. While replication issues can cause failures, a missing test network is a very common and specific cause for this symptom during a test failover.

The Nutanix Oplog is a persistent write buffer that resides in the CVM's DRAM and is backed by the SSD tier. 'Oplog Write IOPS' represents the total number of write I/O operations being sent to the Oplog. 'Extent Store Write IOPS' represents the I/O operations that have been de-staged from the Oplog to the persistent SSD storage (the Extent Store). Comparing these two metrics shows how much write I/O is being absorbed by the fast Oplog versus being written to the slower (but still fast) SSD tier.

Nutanix cloning and snapshot technology is based on a Redirect-on-Write (ROW) algorithm. When a VM is cloned, it is essentially a writable snapshot. The clone initially shares all the same data blocks as the parent image and consumes no extra physical space. Only when new data is written to the clone are new blocks allocated, and metadata pointers are updated to point to these new blocks. This makes cloning extremely fast and space-efficient, which is ideal for VDI deployments.

The correct and secure method for backing up native KMS keys is through the Prism Element UI. Under the Key Management settings, there is a dedicated 'Backup' workflow. This process requires a quorum of KMS leaders to authorize the backup and generates encrypted key files that must be stored in a secure, external location. This is a critical administrative task to prevent data loss if the cluster becomes irrecoverable.

With a Replication Factor of 3, every piece of data and metadata is stored in three distinct copies across the cluster. The failure of two disks on two different nodes means that for the affected data/metadata, one copy remains. The cluster is designed to handle this F=2 scenario, so it remains fully operational. The Curator service will immediately start a background process to restore the data to three copies using the remaining healthy disks.

Nutanix Guest Tools (NGT) provides the communication channel between the Nutanix cluster (specifically the CVM) and the guest operating system. This channel is used for multiple features, including application-consistent snapshots. The NGT service inside the VM coordinates with the Volume Shadow Copy Service (VSS) on Windows or runs pre-freeze/post-thaw scripts on Linux to ensure applications are in a consistent state before the snapshot is taken.