Important Nutanix NCP-MCI-6.10 Exam Questions

Answer: A

Explanation:

Nutanix requires that all cluster components synchronize time using an external NTP (Network Time Protocol) server.

Option A (Adding an external NTP server) is correct because Nutanix best practices recommend using an external time source to prevent clock drift between cluster nodes.

Option B (DNS server IP) is incorrect: A DNS server does not provide NTP services.

Option C (Server with DNS hostname) is incorrect unless the DNS hostname resolves to an NTP server.

Option D (IP of the Domain Controller) is incorrect because not all domain controllers provide NTP services unless explicitly configured.

References:

Nutanix Best Practices: NTP Configuration for Hyper-V Clusters

Nutanix KB: Ensuring Proper Time Synchronization Across Cluster Nodes

Nutanix Documentation: Prism Central NTP Settings Configuration

Answer: B

Explanation:

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 the CriticalApps:Alerts category 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 trigger This 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 trigger This 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 the CriticalApps:Alerts category. 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 trigger This 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 trigger This is incorrect. The term ''Alert-based trigger'' is not a standard option in Nutanix Playbooks. The correct terminology is Alert 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 under Operations > Playbooks > Create Playbook. Select the Alert Matching Criteria trigger, specify the VM Protection Failed alert, and filter by the CriticalApps:Alerts category. 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.'

Answer: B, D

Explanation:

When synchronous replication has been configured and a planned failover is required for datacenter maintenance, Nutanix recommends performing a planned failover to ensure data consistency and a clean transition of services.

From the Nutanix Enterprise Cloud Administration (ECA) course materials:

''A planned failover ensures that data replication is complete and consistent between the primary and standby sites before the workload is migrated. This prevents data loss and ensures seamless recovery.''

Additionally:

''A planned failover can be initiated either from the primary site or from the standby site. This provides flexibility depending on operational preferences and site availability during maintenance windows.''

''Unplanned failovers should only be used in the event of unexpected site outages or catastrophic failures, as they may involve data loss or incomplete synchronization.''

Therefore, the correct approaches are to conduct a planned failover either from the standby site (B) or from the primary site (D). This ensures seamless workload transition during the datacenter maintenance event.

Answer: B

Explanation:

Reserved Capacity settings define how much storage is exclusively allocated for a specific container.

Option B (Reserved Capacity is too high) is correct:

If too much space is reserved for a container, it can report 'out of space' while the cluster still has free capacity.

Options A, C, and D are incorrect:

Advertised Capacity, Compression, and RF settings do not directly cause storage exhaustion unless misconfigured with Reserved Capacity.

References:

Nutanix Storage Best Practices Configuring Reserved and Advertised Capacity

Nutanix KB Troubleshooting Storage Container Out-of-Space Alerts

Answer: A