NCP-MCI-6.10 Exam Dumps - Nutanix NCM-MCI Questions and Answers

After a Prism Central upgrade, IAM authentication settings may require reconfiguration.

Option D (Log in with a local admin account) is correct:

If IAM authentication fails, thelocal admin account must be usedto check domain settings.

Option A (Ping the Domain Controller) is incorrect:

Network connectivity is important, but theissue is likely related to IAM settings, not network reachability.

Option B (Check firewall port 9441) is incorrect:

Port 9441 is used forSSO authentication, butport issues usually result in login delays, not complete failures.

Option C (Validate signing certificate) is incorrect:

While certificates can cause issues,local admin login should always work.

Question 155 [Manage Nutanix clusters]

Which Nutanix feature allows administrators to expand a cluster by adding new nodes without downtime?

A. AHV Protection Domains

B. Prism Central

C. Scale-out Architecture

D. Metro Availability

Answer: C

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."

Within Nutanix Recovery Plans, IP address transformations are handled through an automated mechanism known asIP Address Mapping. The documentation describes two methods: fixed mappings and offset-based mappings.

Offset-based mapping allows administrators to maintain consistent host identity attributes such as the last octet while shifting only the subnet portion during DR failover. The internal guidance states, “Offset-based mapping enables automatic recalculation of target IP addresses using offsets applied to source subnets, allowing preservation of host-specific octets across networks.”

Custom scripts are possible but not recommended because Nutanix already provides a built-in, automated IP transformation system. Editing IPs inside VMs after failover is operationally expensive and defeats the purpose of an orchestrated DR workflow. IPAM is useful for dynamic IP assignment but does not preserve the last octet mapping requirement.

Thus, Offset-based IP mapping is the correct mechanism for this requirement.

Nutanix LCM architecture supports firmware, BIOS, BMC, disk controller, and drive updates only when the environment includes multiple nodes that can provide redundancy during the upgrade process. The LCM documentation specifies that firmware upgrades require node evacuation and rolling upgrade sequencing so that workloads remain available. A single-node cluster does not have node-level redundancy and therefore cannot support firmware upgrade operations that require putting a node into maintenance automatically. The guidance clearly states that “firmware upgrades are not supported for single-node clusters because the host cannot be safely placed into a maintenance mode during the LCM workflow.” LCM is supported for software inventory, but not for firmware activation on single-node clusters. This explains why no firmware updates appear in the LCM interface.

Nutanix Prism Central uses Role-Based Access Control (RBAC) combined with Projects to segment access to workloads. Documentation describes Projects as:

“Projects provide a scalable method to group VMs and assign user or group permissions so that access is restricted to only the resources belonging to that project.”

When VMs are added to a project, Prism Central automatically handles:

scoping of administrative permissions

allowed actions (power, console, modify)

limiting visibility only to VMs inside that project

isolation between different teams or business units

Role mapping alone does not limit scope; it only assigns permissions. Without projects, users may see more VMs than intended. VPCs relate to Flow Virtual Networking and network segmentation, not Prism RBAC or VM-level access control. Security Policies isolate network traffic, not administrative visibility.

Thus, creating a project for each team lead and assigning VM access is the most efficient and intended Nutanix mechanism.

RF3 (Replication Factor 3) clusters require sufficient reserved capacity to tolerate failures without data loss.

Option C (Set Reserve Capacity for Failure to Auto Detect) is correct:

Auto Detect dynamically calculates the necessary reserved spacebased on cluster size and RF settings.

It ensures thatenough storage remains available in case of a node failure.

Option A (Set Reserve Storage Capacity to 20%) is incorrect:

The required storage reservationdepends on the number of nodes and RF level, not a fixed percentage.

Option B (Set Reserve Capacity for Failure to None) is incorrect:

Without reserved capacity,a node failure could lead to data unavailability.

Option D (Set Reserve Memory Capacity to 20%) is incorrect:

This setting applies toRAM, notstorage resiliency.

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.