Pass the Nutanix NCM-MCI NCP-MCI-6.10 Questions and answers with CertsForce

Nutanix capacity planning includes a feature called “Reserve Capacity for Failure,” which ensures that enough resources are preserved to sustain one or more node failures without impacting cluster functionality.

For RF3 clusters, the documentation states:

“Reserve Capacity for Failure should be set to Auto Detect, which calculates the required resources dynamically based on node count, RF policy, and data distribution.”

RF3 requires more resiliency than RF2, and manual settings such as fixed percentages do not accurately reflect the space needed during multi-node failure resiliency. “None” is never recommended because it eliminates failover protection. Memory reserve percentages do not impact storage resiliency. Storage reserve percentages are static and do not reflect the real RF3 overhead.

Auto Detect ensures Nutanix automatically calculates the resources needed to sustain the required failure domains.

The Nutanix ECA course addresses data protection mechanisms, including how to safeguard disaster recovery (DR) snapshots from inadvertent or malicious deletion. Ensuring that DR snapshots are protected while providing notification requires a policy-based approach to control and monitor deletion actions. The ECA course emphasizes the use ofApproval Policiesin Prism Central to enforce oversight on critical operations like snapshot deletion.

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

Module: Data Protection, Section: Approval Policies"Approval Policies in Prism Central allow administrators to enforce review and approval for operations such as snapshot deletion. By creating an Approval Policy for DR snapshots, administrators can ensure that deletion requests are reviewed by designated approvers, preventing unauthorized or accidental deletions and providing notifications to relevant stakeholders."

Module: Prism Central Management, Section: Policy Engine"To protect critical resources like DR snapshots, an Approval Policy can be applied to require approval for deletion actions. This ensures that no snapshot is deleted without explicit authorization, and notifications are sent to approvers to maintain oversight."

Explanation of Options:

A. Create and Apply an Approval PolicyThis is the correct answer. An Approval Policy in Prism Central is the best way to protect DR snapshots from inadvertent or malicious deletion. The policy requires designated approvers to review and authorize snapshot deletion requests, ensuring oversight and preventing unauthorized actions. Notifications are sent to approvers, meeting the requirement for awareness of deletion attempts. The ECA course highlights:"Approval Policies are ideal for protecting critical data assets, such as DR snapshots, by enforcing a mandatory review process before deletion."

B. Create and Apply an Alert PolicyThis is incorrect. Alert Policies in Nutanix are used to notify administrators of system events or thresholds (e.g., high CPU usage or disk failures) but do not prevent actions like snapshot deletion. While an Alert Policy could notify administrators after a deletion occurs, it does not provide proactive protection or require approval, failing to meet the question’s requirements. The ECA course states:"Alert Policies are reactive and designed to notify administrators of events, not to control or prevent actions like snapshot deletion."

C. Assign DR Admin Role to usersThis is incorrect. Assigning a DR Admin Role grants users permissions to manage DR operations, including snapshot deletion, but does not add protection or notification mechanisms. In fact, it could increase the risk of deletion by granting more users access. The ECA course notes:"The DR Admin Role provides administrative privileges for data protection tasks but does not enforce approval workflows or protect against unauthorized deletions."

D. Create a Playbook to alert on eventThis is incorrect. Playbooks in Nutanix Flow or Prism Central are used to automate responses to events (e.g., scaling resources or sending alerts), but they are not designed to prevent snapshot deletion or enforce approval workflows. A Playbook could alert administrators after a deletion event, but it lacks the proactive control provided by an Approval Policy. The ECA course clarifies:"Playbooks are suited for automated remediation or notifications but cannot enforce approval for actions like snapshot deletion."

Additional Context from ECA:

Approval Policy Workflow: In Prism Central, an Approval Policy can be created underPolicies > Approval Policies, specifying DR snapshots as the target resource and defining approvers. When a user attempts to delete a protected snapshot, the request is queued for approval, and notifications are sent to approvers via email or Prism Central’s interface.

Use Case: For DR snapshots, which are critical for recovery, Approval Policies ensure that only authorized personnel can approve deletions, reducing the risk of data loss.

Supporting Reference from Web Results:

The Nutanix Bible (https://www.nutanix.com/go/the-nutanix-bible) supports the ECA documentation: "Approval Policies in Prism Central provide granular control over operations like snapshot deletion, ensuring critical DR resources are protected through mandatory approval workflows."

In Nutanix Prism Central, user-generated reports in Intelligent Operations are stored for a limited time and then deleted automatically.

Option C (Reports are automatically deleted after 24 hours) is correct:

Reportsdo not persist indefinitelyunless they arescheduled reports.

One-time reports expire after 24 hours.

Option A (Cluster Viewer deleted the report) is incorrect:

Cluster Viewerdoes not have permissions to delete reports.

Option B (Report was archived) is incorrect:

Nutanixdoes not automatically archive reports.

Option D (Report stored in Prism Element) is incorrect:

Reportsare generated and stored only in Prism Central, not Prism Element.

Nutanix storage container configuration guidance specifies that “Advertised Capacity” is the setting used to define a maximum limit for the container. This value enforces a hard cap on space usage. Reserved Capacity, in contrast, defines a minimum guarantee of space for the container and does not limit growth.

Prism Element is the correct interface for creating storage containers with specific data reduction settings such as compression and deduplication, as the container-level storage policies are applied directly at the cluster’s storage layer.

The documentation further clarifies that RF1, inline compression, and deduplication settings are configured within Prism Element under container creation. Therefore, to enforce the 100 GiB limit, the administrator must create the container in Prism Element and set the Advertised Capacity to 100 GiB.

When a node is placed intoMaintenance Mode, Nutanix follows a structured process to ensureservice continuity and data integrity.

Option B (All eligible VMs on the host are migrated to other hosts) is correct:

Live Migration automatically moves VMs to other hoststo avoid downtime.

This ensures workloads remain operational during maintenance.

Option D (Non-migratable VMs are powered off) is correct:

Some VMs, such as those usingGPU pass-through or local storage dependencies,cannot be live-migrated.

These VMsmust be powered offbefore placing the host into Maintenance Mode.

Option A is incorrect:

Non-migratable VMs are not automatically restarted on other hosts—they remain powered off until manually restarted.

Option C is incorrect:

Eligible VMs are live-migrated, not powered off.

NutanixIntelligent Operations Reports(Option D) provideweekly summariesof cluster health, performance, and resource consumption.

These reports includerecommendations for optimization, alerts, and forecasted resource usage trends.

Option A (Admin Center LCM)managesfirmware and software upgradesbut does not generate weekly performance reports.

Option B (Prism Central Syslog)is used forlogging and event tracking, not performance summaries.

Option C (Infrastructure VMs List)provides astatic list of VMsbut does not generate periodic reports.

In a 12-node FT2 cluster, onlyonenode can be placed into maintenance mode at a time. This ensures that the cluster maintains data redundancy and protection (FT2 indicates 2-failure tolerance).

From theNutanix Enterprise Cloud Administration (ECA)course materials:

“For FT2 clusters, a maximum of one node can be placed in maintenance mode at a time to ensure the cluster’s ability to tolerate failures and maintain quorum.”