Free Practice Questions for Nutanix NCP-MCI-6.10 Exam

When diagnosing CPU performance issues, CPU Ready Time and CPU Usage are the key indicators of whether more vCPUs are needed.

Option A (VM CPU Ready Time) is correct:

High CPU Ready Time means the VM is waiting for CPU resources, indicatingCPU contention.

Option B (VM CPU Usage) is correct:

If CPU usage isconsistently high, adding more vCPUsmay improve performance.

Option C (Host CPU Usage) is incorrect:

Host-wide CPU usage does not indicate whether a specific VM needs more vCPUs.

Option D (Host Memory Swap Out Rate) is incorrect:

Memory swappingaffects RAM performance, not CPU allocation.

A cluster runway below 365 days does not necessarily indicate an issue if Intelligent Operations determines that workloads are sustainable.

Option B (Because new workloads are sustainable) is correct:

Nutanixanalyzes resource trendsand marks clusters as healthyif new workloads are within projected capacity.

Option A (Storage Runway is still good) is incorrect:

Storage isone component, butCPU and memoryalso affect runway calculations.

Option C (Recommended resources) is incorrect:

Recommendations help optimize capacity, butdo not define cluster health.

Option D (Target is 1 month) is incorrect:

The scenario’s target window does not impact the actual runway calculation.

In a Nutanix cluster, Replication Factor 2 (RF2) means that each piece of data has two copies: a primary and a replica. To safely remove a node while ensuring data redundancy and cluster health, the system must have enough nodes to maintain the RF2 protection and complete the removal.

From the Nutanix Enterprise Cloud Administration (ECA) documentation:

“The minimum number of nodes required for a safe host removal in an RF2 cluster is four. This ensures that even after removing a node, there are enough remaining nodes to continue hosting the primary and replica data copies, meeting the RF2 requirement.”

The logic is:

In a 3-node RF2 cluster, there isn’t enough redundancy to safely remove a node without impacting data availability.

A 4-node RF2 cluster allows safe removal of one node while still ensuring two copies of all data remain.

Thus, the minimum number of nodes required for a safe host removal in an RF2 cluster is 4

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.

The Nutanix ECA course covers the use of Playbooks in Prism Central to automate responses to specific events or conditions, such as VM protection failures. The task requires creating an alert for VMs in theCriticalApps:Alertscategory when a VM Protection Failed Alert is triggered, with notifications sent to on-call personnel.

Extract from Nutanix Enterprise Cloud Administration (ECA) Course Documents:

Module: Automation, Section: Playbooks"Playbooks in Prism Central can be configured with an Alert Matching Criteria trigger to respond to specific alerts, such as VM protection failures. This trigger allows filtering by entity categories, ensuring the Playbook only acts on VMs matching the specified category, and can send notifications to designated personnel."

Module: Intelligent Operations, Section: Alert Management"To create an alert for specific VMs based on a category, use a Playbook with an Alert Matching Criteria trigger. This allows precise targeting of alerts (e.g., VM Protection Failed) for VMs in a category like CriticalApps:Alerts, with actions such as sending email notifications to on-call teams."

Explanation of Options:

A. Create a Playbook with a Manual triggerThis is incorrect. A Manual trigger requires an administrator to manually initiate the Playbook, which does not meet the requirement for automatic alerting when a VM Protection Failed Alert is triggered. The ECA course states:"Manual triggers are used for ad-hoc Playbook execution, not for automated responses to alerts."

B. Create a Playbook with an Alert Matching Criteria triggerThis is the correct answer. An Alert Matching Criteria trigger allows the Playbook to respond automatically to specific alerts, such as VM Protection Failed, and can be filtered to apply only to VMs in theCriticalApps:Alertscategory. The Playbook can then execute an action, such as sending an email notification to on-call personnel. The ECA course highlights this as the most precise method for alert-based automation.

Supporting Extract:"The Alert Matching Criteria trigger enables Playbooks to filter alerts by type and entity category, ensuring targeted responses, such as notifying on-call personnel for VM protection failures in specific categories."

C. Create a Playbook with an Event-based triggerThis is incorrect. Event-based triggers respond to system events (e.g., VM power-on or cluster events) rather than specific alerts like VM Protection Failed. They are less precise for this use case, as they do not allow filtering by alert type or category. The ECA course notes:"Event-based triggers are suited for general system events, not for targeted alert responses like VM protection failures."

D. Create a Playbook with an Alert-based triggerThis is incorrect. The term “Alert-based trigger” is not a standard option in Nutanix Playbooks. The correct terminology isAlert Matching Criteria trigger, which is specifically designed for alert-driven automation. The ECA course does not reference a generic “Alert-based trigger” option.

Additional Context from ECA:

Playbook Configuration: In Prism Central, a Playbook is created underOperations > Playbooks > Create Playbook. Select theAlert Matching Criteriatrigger, specify theVM Protection Failedalert, and filter by theCriticalApps:Alertscategory. Add an action to send an email notification to the on-call team.

Category Filtering: Categories (e.g., CriticalApps:Alerts) are key-value pairs assigned to VMs for organization and policy enforcement, making them ideal for targeting specific VMs in Playbooks.

Supporting Reference from Web Results:

The Nutanix Bible (https://www.nutanix.com/go/the-nutanix-bible) supports: "Playbooks with Alert Matching Criteria triggers allow precise automation for alerts, such as VM protection failures, filtered by VM categories, with actions like sending notifications."

VM templates in Nutanix are supported only when the VM’s disks reside on storage containers configured with Replication Factor 2 (RF2) or higher.

Option C (VM has disks on RF2 containers) is correct:

VM templates requirea minimum RF2 for fault tolerance.

RF1 containers do not meet Nutanix best practices for VM templates.

Option A is incorrect:

VMs protected by Protection Domains can be cloned, but this is different from creating a VM template.

Option B is incorrect:

Agent VMs (e.g., Witness VMs) or Prism Central cannot be used as VM templates.

Option D is incorrect:

Nutanix VM templates are natively supported on AHV, not ESXi.

https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Security-Guide-v6_10:mul-configure-data-in-transit-encryption-pc-t.html

"Ensure that port 2009 is open between the Prism Central instances for the KMS cluster to communicate."This is explicitly stated in the "Firewall rules for Data-in-Transit Encryption" section for Prism Central.

Technical Context:

Port 2009 is used by ZooKeeper (the coordination service for the KMS cluster) in Scale-Out Prism Central deployments.

DiTE in Prism Central relies on a dedicated KMS cluster that synchronizes encryption keys across PC instances using this port.

Firewall blocks on port 2009 break KMS quorum, preventing key exchange and causing DiTE to fail.

Active-Active bonding allows multiple network interfaces to be used simultaneously, improving bandwidth and redundancy.

Option B (Active-Active) is correct:

This mode enablesload balancing across all available adapters, providinghigher throughput and fault tolerance.

Option A (No Uplink Bond) is incorrect:

Without a bond, VMscannot benefit from multiple adapters.

Option C (Active-Active with MAC pinning) is incorrect:

MAC pinningbinds traffic to a single NIC, limiting bandwidth distribution.

Option D (Active-Backup) is incorrect:

This modeonly provides failover, not increased bandwidth.

Protection Domains (PDs) in Nutanix ensure that entire applications and their associated data are protected during failover.However,Volume Groups (VGs) are not automatically includedunless explicitly configured.

Option A (Select "Auto protect related entities") is correct:

This setting ensures thatassociated Volume Groups, networks, and other dependencies are included in the Protection Domainautomatically.

Without enabling this, only the VM itself would be protected, leading tomissing application data upon failover.

Option B (Manually add Volume Groups to Protected Entities) is correct:

If"Auto protect related entities" is not enabled, the administrator mustmanually add Volume Groups to the Protection Domain.

This ensures that bothVMs and their attached Volume Groupsare replicated and recovered together.

Option C (Place Volume Groups in a separate Protection Domain) is incorrect:

Separating Volume Groups into a different PDdoes not guarantee they failover together with VMs.

It is best practice tokeep related VMs and Volume Groups in the same PD.

Option D (Use application-consistent snapshots) is incorrect:

Whileapplication-consistent snapshots improve data integrity, theydo not fix missing Volume Groups in failover scenarios.