Nutanix NCP-MCI-6.10 Nutanix Certified Professional - Multicloud Infrastructure v6.10 Exam Practice Test

Answer : D

High SSD utilization in a hybrid cluster can lead to increased I/O latency as new writes may spill over to HDDs, reducing overall performance.

Option D (Average I/O latency in the cluster may increase) is correct:

If SSD usage is above 75%, data tiering shifts to slower HDDs, increasing latency.

Option A is incorrect:

SSD failures are managed via redundancy policies (RF2/RF3), and high utilization does not impact failure handling.

Option B is incorrect:

Metadata is stored separately, and high SSD usage does not mean metadata is at risk.

Option C is incorrect:

Clusters do not go into read-only mode due to high SSD utilization---they simply experience performance degradation.

Nutanix Storage Performance Guide SSD Tiering and Performance Management

Nutanix KB Managing High SSD Utilization in Hybrid Clusters

Answer : B, D

When a node is placed into Maintenance Mode, Nutanix follows a structured process to ensure service 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 hosts to avoid downtime.

This ensures workloads remain operational during maintenance.

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

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

These VMs must be powered off before 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.

Nutanix AHV Best Practices Understanding Maintenance Mode Behavior

Nutanix KB VM Migration and Power-Off Scenarios in Maintenance Mode

Answer : B

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.

Nutanix Storage Best Practices Configuring Reserved and Advertised Capacity

Nutanix KB Troubleshooting Storage Container Out-of-Space Alerts

Answer : D

For cross-hypervisor DR failover (e.g., ESXi to AHV), Nutanix Guest Tools (NGT) must be installed on VMs to ensure proper configuration and recovery.

Option D (NGT must be installed on source guest VMs) is correct:

NGT ensures correct reconfiguration of VM devices and networking settings during failover.

It handles disk and driver reassignments between ESXi and AHV.

Option A (Utilize delta disks) is incorrect:

Delta disks are used in snapshot optimization, not DR failover.

Option B (Deploy Legacy BIOS boot) is incorrect:

AHV prefers UEFI boot mode, and Legacy BIOS is not a requirement.

Option C (Use raw device mappings) is incorrect:

RDMs are VMware-specific and are not used in AHV failover scenarios.

Nutanix Disaster Recovery Guide Cross-Hypervisor Failover Best Practices

Nutanix KB Ensuring VM Compatibility During ESXi to AHV DR

Answer : B

Entity Charts in Nutanix Prism Central allow multiple metrics from a single entity (e.g., VM, storage container) to be displayed on a single graph.

Option B (Entity Chart) is correct:

This allows the administrator to track multiple performance metrics (e.g., read/write bandwidth, IOPS) for a specific VM.

Option A (Metric Chart) is incorrect:

Metric Charts track a single metric across multiple entities, which does not meet the requirement of displaying multiple metrics for a single VM.

Option C (Hypervisor Performance Chart) is incorrect:

Hypervisor Performance Charts track host-level metrics, not VM-specific bandwidth metrics.

Option D (VM Summary Chart) is incorrect:

VM Summary Charts only provide an overview and do not support custom multi-metric tracking.

Nutanix Prism Central Guide Entity vs. Metric Charts for Performance Analysis

Nutanix KB Creating Custom Charts in Prism Central

Answer : A

When creating a storage container in Nutanix, the administrator must configure the correct capacity settings:

Option A (Prism Element with Advertised Capacity of 100 GiB) is correct:

Advertised Capacity defines logical limits for the container (i.e., how much space it reports as available).

Inline Compression can be enabled directly in Prism Element.

Option B (Create in Prism Element without Advertised Capacity) is incorrect:

Without specifying Advertised Capacity, the container may consume unlimited storage.

Option C (Create in Prism Central with Reserved Capacity) is incorrect:

Reserved Capacity applies to Quality of Service (QoS) policies, not storage limits.

Option D (Create in Prism Central without capacity limits) is incorrect:

Prism Central can manage storage but does not directly enforce RF1 and compression policies.

Nutanix Storage Management Guide Creating and Managing Storage Containers

Nutanix Bible Replication Factor (RF) and Data Optimization

Nutanix KB Inline Compression Best Practices in Nutanix AOS

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.

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