Get Nutanix NCP-MCI (6.10) Exam Practice Questions - Real and Updated

Answer : B

During failover in Nutanix Disaster Recovery, VMs retain their static IPs but may lose DNS settings if the network configuration at the DR site is different from the primary site.

Option B (Create custom in-guest scripts) is correct:

Custom scripts allow Windows or Linux VMs to restore DNS settings automatically after failover.

These scripts can be executed using post-failover automation in Nutanix DR policies.

Option A (Self-Service Restore) is incorrect:

Self-Service Restore is used for end-user recovery of deleted files, not for network settings.

Option C (nncli tool) is incorrect:

The nncli tool is used for network troubleshooting, but it does not automatically restore DNS settings.

Option D (Configure a Protection Domain) is incorrect:

Protection Domains define replication policies, but they do not fix DNS settings after failover.

References:

Nutanix Disaster Recovery Guide Failover Automation and Network Configuration

Nutanix Bible VM Recovery and IP Management in DR Scenarios

Nutanix KB Preserving DNS Settings in Disaster Recovery

Answer : A, B

The Nutanix ECA course provides guidance on performance monitoring and troubleshooting for VMs, including metrics to analyze when determining whether additional vCPUs are needed. The scenario involves a VM experiencing performance issues, with the cluster performing well overall, suggesting the issue is VM-specific.

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

Module: Performance Monitoring, Section: VM Performance Metrics 'To determine if a VM requires additional vCPUs, analyze VM CPU Usage and VM CPU Ready Time. High CPU Usage indicates the VM is under heavy load, while high CPU Ready Time suggests the VM is waiting for CPU resources, both justifying additional vCPUs.'

Module: Troubleshooting, Section: VM Performance Issues 'When a VM experiences performance issues, VM CPU Usage and VM CPU Ready Time are critical metrics. CPU Usage shows demand, while CPU Ready Time indicates contention or scheduling delays, helping determine if more vCPUs are warranted.'

Explanation of Options:

A. VM CPU Usage This is correct. VM CPU Usage measures the percentage of CPU resources the VM is consuming. High CPU Usage (e.g., consistently above 80--90%) indicates that the VM is under heavy load and may benefit from additional vCPUs to handle the workload. The ECA course emphasizes: 'VM CPU Usage is the primary metric to assess whether a VM's CPU allocation is sufficient for its workload.'

B. VM CPU Ready Time This is correct. VM CPU Ready Time measures the time a VM is ready to run but waiting for CPU resources from the hypervisor due to contention or oversubscription. High CPU Ready Time (e.g., above 5--10%) suggests that the VM is not getting enough CPU cycles, and adding vCPUs could alleviate the issue. The ECA course notes: 'High VM CPU Ready Time indicates CPU contention, often resolved by adding vCPUs or optimizing resource allocation.'

C. Host Memory Swap Out Rate This is incorrect. Host Memory Swap Out Rate indicates memory pressure on the host, causing memory pages to be swapped to disk. While this can affect VM performance, it is unrelated to CPU performance and does not justify adding vCPUs. The ECA course states: 'Host Memory Swap Out Rate is relevant for memory-related issues, not CPU allocation decisions.'

D. Host CPU Usage This is incorrect. Host CPU Usage measures the overall CPU utilization of the host, not the specific VM. Since the cluster is performing well overall, high Host CPU Usage is unlikely, and it does not directly indicate whether the VM needs more vCPUs. The ECA course clarifies: 'Host CPU Usage is a cluster-wide metric and less relevant for diagnosing VM-specific CPU performance issues.'

Additional Context from ECA:

Performance Monitoring Tools: In Prism Element or Prism Central, VM CPU Usage and CPU Ready Time can be monitored under VM > Monitor or through dashboards. These metrics provide insight into the VM's CPU demand and contention.

Adding vCPUs: The ECA course advises caution when adding vCPUs, as over-allocation can increase CPU Ready Time due to scheduling overhead. However, if both CPU Usage and Ready Time are high, adding vCPUs is justified.

Supporting Reference from Web Results:

The Nutanix Bible (https://www.nutanix.com/go/the-nutanix-bible) supports: 'For VM performance issues, analyze VM CPU Usage and CPU Ready Time to determine if additional vCPUs are needed, as these metrics directly indicate CPU demand and contention.'

Answer : C

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 require a 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.

References:

Nutanix VM Management Guide Creating and Managing VM Templates

Nutanix KB Storage Requirements for VM Templates

Answer : D

The Nutanix ECA course addresses Metro Availability, a high-availability feature that provides synchronous replication between two Nutanix clusters for zero Recovery Point Objective (RPO) and near-zero Recovery Time Objective (RTO). The NCC warning about the break_replication_timeout being below the recommended minimum indicates a configuration issue that could affect the stability of Metro Availability. The break_replication_timeout parameter determines how long the Protection Domain (PD) waits before breaking replication if connectivity between the Metro clusters is disrupted.

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

Module: Data Protection, Section: Metro Availability Configuration 'Metro Availability uses synchronous replication to ensure data consistency between two clusters. The break_replication_timeout parameter defines the timeout period for replication. The recommended minimum value is 15 seconds to prevent premature replication breaks due to transient network issues.'

Module: Nutanix Cluster Check (NCC), Section: Metro Availability Alerts 'An NCC warning indicating that the break_replication_timeout for a Metro Protection Domain is below the recommended minimum suggests the timeout is too low, risking unnecessary replication breaks. The recommended setting is 15 seconds to balance stability and responsiveness in Metro Availability setups.'

Explanation of Options:

A. Update the break_replication_timeout to 10 seconds This is incorrect. A timeout of 10 seconds is below the recommended minimum of 15 seconds, as specified in the ECA course. Setting the timeout too low increases the risk of replication breaking due to transient network latency or jitter, which could disrupt Metro Availability and cause unnecessary failovers. The ECA documentation warns: 'A break_replication_timeout below 15 seconds may lead to frequent replication breaks, reducing the reliability of Metro Availability.'

B. Update the break_replication_timeout to 5 milliseconds This is incorrect. A timeout of 5 milliseconds is far too low and impractical for Metro Availability, as even minor network delays would trigger replication breaks. The ECA course does not support millisecond-level timeouts and explicitly recommends 15 seconds as the minimum. Such a low value would destabilize the Metro setup, as noted: 'Extremely low timeout values are not supported, as they cause replication to break under normal network conditions.'

C. Update the break_replication_timeout to 15 milliseconds This is incorrect. A timeout of 15 milliseconds is still significantly below the recommended minimum of 15 seconds. Similar to option B, this setting would cause replication to break too quickly, undermining the purpose of Metro Availability. The ECA course clarifies: 'Timeouts in milliseconds are not recommended for Metro Availability, as they do not account for typical network latency in synchronous replication setups.'

D. Update the break_replication_timeout to 15 seconds This is the correct answer. The ECA course explicitly recommends a break_replication_timeout of 15 seconds as the minimum to ensure Metro Availability remains stable. This value allows the system to tolerate transient network issues without prematurely breaking replication, maintaining data consistency and availability. The NCC warning indicates the current timeout is below this threshold, and updating it to 15 seconds resolves the issue.

Supporting Extract: 'To resolve NCC warnings about break_replication_timeout, set the value to 15 seconds using the ncli command: ncli pd update-metro-avail-pd name=<PD_NAME> break_replication_timeout=15. This ensures compliance with Nutanix best practices.'

Additional Context from ECA:

Metro Availability Overview: Metro Availability synchronously replicates data between two clusters, typically within 100 km, to achieve zero RPO. The break_replication_timeout is a critical parameter that balances responsiveness to network issues with the need to avoid unnecessary replication breaks. The ECA course notes: 'A timeout of 15 seconds is the default and recommended value to handle typical network fluctuations in Metro setups.'

NCC Warning Resolution: The NCC (Nutanix Cluster Check) monitors cluster health and flags configurations that deviate from best practices. The warning about break_replication_timeout indicates a risk to Metro Availability stability, and setting it to 15 seconds aligns with Nutanix recommendations.

Supporting Reference from Web Results:

The Nutanix Support Portal (https://portal.nutanix.com) confirms the ECA guidance: 'For Metro Availability, the break_replication_timeout should be set to a minimum of 15 seconds to prevent replication breaks due to transient network issues, as flagged by NCC warnings.'

Answer : A, C

When synchronous replication fails immediately between two clusters, it is often due to blocked communication across the required ports (2009 and 2020). These must be open manually if the clusters are in different subnets or if network policies block traffic.

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

''Replication communication relies on specific ports, which must be allowed through the firewall. If the clusters are in different subnets or if there are external firewalls, these ports must be explicitly opened.''

''The modify_firewall command is used to open or close ports on cluster nodes. For replication and remote site communication, eth1 is typically used for external replication traffic.''

Since eth1 is typically used for external connectivity and replication traffic, opening ports on this interface using modify_firewall resolves the communication block.