NCP-MCI-6.10 Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI v6.10) Questions and Answers

When connectivity between Metro clusters is lost, Nutanix Metro Availability ensures data integrity using Witness for automatic failover.

Option A (Guest VM I/O operations pause until connectivity is restored) is correct:

Metro Availability enforces data consistency, so I/O operationspauseuntil failover is confirmed.

Option C (Guest VMs failover automatically to the recovery cluster) is correct:

TheWitness VM detects the failureand initiates anautomatic failoverto the secondary cluster.

Option B is incorrect:

Prism Centraldoes not control VM failover in Metro Availability.

Option D is incorrect:

The primary cluster isunreachable, so VMs cannot continue running there.

To ensureVM high availability (HA) in the event of a node failure, the administrator mustenable HA Reservation (Option B)in Prism Element.

High Availability (HA) in Nutanix ensures that VMs restart on another available node if the host they are running on fails.

Option A (Redundancy Factor 3)affectsstorage redundancy, not VM failover.

Option C (Protection Domains)is related todisaster recovery (DR), not local HA failover.

Option D (RF1 Storage Container)would reduce fault tolerance and is not recommended for production environments.

Nutanix Data Protection enforces strict snapshot lifecycle controls to ensure recovery integrity. The system prevents deletion of any snapshot that is actively referenced by a running operation. The documentation states:

“Snapshots that are part of an active recovery or restore workflow cannot be deleted until the operation completes, as they are required to maintain data consistency and restore points.”

This includes DR failover tests, restorations, or live recovery workflows. Corrupted snapshots do not cause deletion failure; the system can still delete a corrupted snapshot unless it’s attached to an active workflow. Ransomware affects guest data, not the snapshot metadata in Prism. Approval policies do not block snapshot deletion unless tied to automation policies, which is rare and would produce a different error.

Therefore, active recovery operations are the most common and most accurate cause when deletion is blocked.

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 totrack multiple performance metrics(e.g., read/write bandwidth, IOPS) for aspecific VM.

Option A (Metric Chart) is incorrect:

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

Option C (Hypervisor Performance Chart) is incorrect:

Hypervisor Performance Chartstrack host-level metrics, notVM-specific bandwidth metrics.

Option D (VM Summary Chart) is incorrect:

VM Summary Chartsonly provide an overviewand do not supportcustom multi-metric tracking.

Moving vDisks to a storage container with compression enabled ensures better data efficiency without downtime.

Option A (Migrate vDisks) is correct:

vDisk migration is non-disruptiveand allows compression settings to be applied dynamically.

Option B (Recreate the VM) is incorrect:

Rebuilding the VM is unnecessaryand would causedowntime.

Option C (Migrate the VM) is incorrect:

VM migration does not guarantee that only vDisks move, and it may disrupt performance.

Option D (Recreate vDisk) is incorrect:

This method ismanual and time-consuming, while Nutanix provides anautomated approach.

The Nutanix data protection guide specifies that NearSync replication provides an RPO between 1 and 15 minutes, which is the lowest RPO available for standard asynchronous-based replication models. The documentation further states that NearSync is the supported method for achieving sub-hour RPO on one- and two-node clusters. Asynchronous replication has a minimum RPO of 60 minutes and therefore cannot be used for lowest RPO requirements. While scheduling intervals such as 1–15 minutes appear similar, Nutanix notes that these intervals are only achievable under the NearSync replication mode. Therefore, selecting NearSync is the required configuration to meet the goal of achieving the lowest RPO.

A cluster runway below 365 days does not necessarily indicate an issue if Intelligent Operations determines that workloads are sustainable.

Option B (Because new workloads are sustainable) is correct:

Nutanixanalyzes resource trendsand marks clusters as healthyif new workloads are within projected capacity.

Option A (Storage Runway is still good) is incorrect:

Storage isone component, butCPU and memoryalso affect runway calculations.

Option C (Recommended resources) is incorrect:

Recommendations help optimize capacity, butdo not define cluster health.

Option D (Target is 1 month) is incorrect:

The scenario’s target window does not impact the actual runway calculation.

The Nutanix Life Cycle Manager (LCM) is designed to manage and automate firmware and software upgrades across Nutanix clusters. However, firmware upgrades via LCM are not supported for single-node clusters. This limitation is documented in the ECA course as well as in LCM’s official release notes and guides.

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

“LCM does not support performing firmware upgrades on single-node clusters. These clusters require manual upgrades, and LCM will not list any available firmware updates for them, regardless of the firmware revision state.”

The other options:

A is incorrect; single-node clusters don’t have this limitation specifically for “one-disk” firmware upgrades—it’s a complete limitation for all firmware tasks in LCM.

B is misleading; LCM is supported in general for Nutanix clusters, just not for firmware tasks in single-node clusters.

D is incorrect because lack of internet connectivity would typically show an error related to download or connectivity issues, not complete absence of firmware updates.

Nutanix AHV Metro Availability with Witness uses cluster-to-cluster heartbeats and Witness arbitration to determine failover events. Internal design notes state:

“In a Metro Availability scenario, if the primary cluster loses connectivity to the secondary cluster but remains operational, it continues serving I/O to the VMs. No automatic failover occurs unless the cluster is determined to be down.”

Also:

“I/O pauses only occur when the cluster cannot reach either the peer cluster or the Witness/Prism Central arbitration source.”

Applying this to the scenario:

Both metro clusters lose connectivity with each other.

The primary cluster also loses connectivity to Prism Central.

The recovery cluster remains connected to Prism Central.

Since the primary cluster cannot reach the recovery cluster nor Prism Central, the arbitration path is lost. This triggers the “I/O stall for safety” condition described as:

“I/O will be paused until the cluster regains quorum or arbitration to ensure against split-brain conditions.”

But because the primary clusteris still runningand is not declared failed (just isolated), VMs continue running and I/O is paused only as long as arbitration is unreachable.

Thus:

Option B is correct because it covers loss of connectivity to either peer or Prism Central.

Option C is correct because VMs do continue running; only I/O is paused to prevent inconsistency.

Automatic failover only happens when Witness declares the primary unreachable by quorum rules, which is not the case here since only one side can see the Witness.

When Life Cycle Manager (LCM) reports thata newer framework version is available, thecorrect actionis toperform an inventory scan (Option C).

Performing an inventory scan updates the available firmware/software versionsand allows LCM to download required updates.

Option A (Run an AOS upgrade)is unrelated to the LCM framework update process.

Option B (Run an AHV upgrade)is a separate component update and does not affect the LCM framework.

Option D (Download manually from a CVM)is not necessary because LCM updates are automatically pulled after an inventory scan.

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.

When using Metric or Entity Charts in Prism Central for performance monitoring, the most granular preset time interval that can be selected is1 hour.

From theNutanix Enterprise Cloud Administration (ECA)course materials:

“Prism Central provides performance data visualization with customizable time intervals. The smallest preset interval for metric and entity charts is 1 hour, providing highly detailed performance information over short periods.”

This allows administrators to monitor performance fluctuations at a fine-grained level, aligning with best practices for troubleshooting and optimization.

Storage Policies in Nutanix are applied through Categories, allowing policy-based automation and enforcement.

Option D (Assign the VM or VG to the same Category as the Storage Policy) is correct:

Nutanixapplies Storage Policies based on VM Categories, enablingflexibility in policy enforcement.

Option A is incorrect:

Storage Policies are not directly assigned at the VM or VG level—they apply through Categories.

Option B is incorrect:

Policies must be assigned toCategories, not directly to individual VMs/VGs.

Option C is incorrect:

Migrating to a storage container does not automatically apply a Storage Policy.

For NutanixDisaster Recovery (DR) protection policies, thefirst stepis to establish a connection between theProduction cluster and the DR site, which is done by creating anAvailability Zone (AZ) (Option B).

Availability Zones (AZs) define remote sites for replicationand are a requirement for configuring protection domains and disaster recovery plans.

Option A (Installing NGT)is not necessary for setting up replication but is useful for application-consistent snapshots.

Option C (Converting the source cluster to AHV)is not required, as Nutanix supports cross-hypervisor DR betweenESXi and AHV.

Option D (Creating a point-in-time snapshot)is a later step after setting up theAvailability Zone and Protection Policy.

Nutanix Protection Policies replicate VM data between clusters using Nutanix’s built-in data protection engine. For inter-site or cloud-based replication, Nutanix documentation specifies that replication traffic can be encrypted using the Data-in-Transit Encryption feature. The internal description states:

“Data-in-Transit Encryption secures replication traffic moving between clusters by encrypting data packets before transmission across external or untrusted networks.”

This is distinct from Data-at-Rest Encryption, which protects stored data on disks but does not secure network traffic. Self-encrypting drives and secure boot only protect the VM locally, not the replication path. Because replication to NC2 travels over the Internet, encryption of the transport channel is mandatory to meet security compliance.

Therefore, the required capability is Data-in-Transit Encryption.

Receive Side Scaling (RSS) VirtIO-Net Multi-Queue improves network performance by distributing network processing across multiple CPU cores.

Option C (Enable RSS VirtIO-Net Multi-Queue) is correct:

This settingreduces CPU bottlenecksby allowing multiple queues to handle network packets.

It isessential for high-throughput network applications.

Option A (Add more vCPUs) is incorrect:

CPU resources are important, butwithout enabling RSS, additional vCPUs will not optimize network traffic distribution.

Option B (Enable AHV Turbo Technology) is incorrect:

AHV Turbo improvesdisk I/O, notnetwork I/O.

Option D (Add more RAM) is incorrect:

RAM does not directly impact network performance.

Nutanix Capacity Planning and Runway calculations analyze CPU, memory, and storage growth trends independently. The “Overall Runway” metric reflects the shortest runway across these three resources. The Capacity Planning documentation explains that “the scenario result may show the cluster in a healthy state if the most critical resource remains sufficiently available, even when the overall runway falls below longer-term thresholds.”

Storage is often the dominant factor in determining long-term viability. If the storage runway remains strong, the system may indicate that the environment is in good shape even though the overall runway appears shorter due to CPU or memory projections. Because the question refers to the scenario still indicating a good cluster state, the most accurate interpretation is that storage runway remains healthy, and thus the system does not consider the cluster at risk.

VMs using GPU pass-through cannot be live-migrated because they are directly tied to a physical GPU on a specific host.

Option B (VMs use GPU pass-through) is correct:

Pass-through devices (such as GPUs) are directly assigned to VMs, makingmigration impossibleunless the VM is powered off first.

Option A (VMs use a Volume Group) is incorrect:

Volume Groupssupport live migrationunless they are configured incorrectly.

Option C (VM-VM anti-affinity) is incorrect:

Anti-affinity rules prevent two specific VMs from running together, but do not prevent migration.

Option D (VMs use external NAS) is incorrect:

Using NAS does not block VM migration, as Nutanixsupports shared storage across hosts.

Understanding the Exhibit & Memory Allocation

Thehost has 128GB of physical RAM.

Thecurrent memory allocationacrossthree VMs (VM1, VM2, VM3) is 128GB, but only92GB is actually utilized.

This means there is36GB of unutilized memory available for allocation.

Step-by-Step Breakdown

Existing Memory Usage Before Adding VM4

Total Physical RAM:128GB

Used by running VMs (VM1, VM2, VM3):92GB

Unutilized Memory Available:36GB

After Creating and Running VM4

VM4 is allocatedmemory but only utilizes 28GB.

The table does not show VM4’s allocated RAM, but assuming it was given a reasonable allocation, it must have been taken from the36GB unutilized memory pool.

IfVM4 uses 28GB, theremaining unutilized memory is now (36GB - 28GB) = 8GB.

Maximum Memory Allocation for VM5

Sinceonly 8GB remains unutilized, the maximum memory VM5 can be allocated while still allowing it to power on is8GB.

Evaluating the Answer Choices

(A) 4GB❌(Incorrect)

More memory (8GB) is available, so limiting to 4GB is unnecessary.

(B) 8GB✅(Correct)

Theremaining unutilized memory after VM4 is 8GB, so VM5 can be allocated up to8GBwhile ensuring it can power on.

(C) 16GB❌(Incorrect)

Only8GB is left, so 16GB isnot possible.

(D) 32GB❌(Incorrect)

There isnot enough unutilized memoryto allocate 32GB.

Key Concept: Nutanix Memory Overcommit

Nutanix AHV supportsmemory overcommit, meaning VMs can be allocated more memory than physically available usingmemory ballooning and swapping.

However,to power on VM5 without impacting performance, it must fit within the available unutilized memory, which is8GB.

Nutanix Life Cycle Manager (LCM) relies on validated firmware and driver bundles for hardware components. For GPU-enabled hosts, LCM documentation states:

“GPU-enabled AHV hosts require GPU driver bundles to be uploaded manually via the Direct Uploads mechanism so that LCM can validate and upgrade the necessary GPU components during workflow execution.”

GPU drivers are vendor-specific and not always available in the standard catalog, so the administrator must upload them before LCM can orchestrate the upgrade.

Running in dark site mode does not provide missing GPU bundles. Creating agent VMs is unrelated to GPU driver operations. Updating NCC improves validations but does not provide GPU support files.

Therefore, Direct Uploads of GPU driver bundles is required.

In a dark site deployment, LCM does not automatically fetch updates from the internet. The administrator must manually upload compatibility bundles.

Option B (The latest compatibility bundle has not been uploaded) is correct:

Thecompatibility bundlecontainsfirmware mappings, allowing LCM to detect the correct BIOS version.

Option A is incorrect:

AOSdoes not need to be upgraded firstfor a BIOS update.

Option C is incorrect:

TheBMC firmware does not always need updatingbefore BIOS updates.

Option D is incorrect:

In a dark site deployment,LCM does not rely on an internet connection, so webserver access is not required.

Nutanix documentation for Cross-Hypervisor Disaster Recovery (CH-DR) specifies that Nutanix Guest Tools (NGT) must be installed on all VMs participating in ESXi to AHV recovery workflows. NGT includes the VM Mobility Drivers, which are required for the VM to interpret AHV device models, storage controllers, and network adapters during recovery. The documentation notes that without NGT installed, VMs may fail to boot or attach devices correctly after being recovered on AHV. Legacy BIOS, RDMs, and delta disks are not listed as prerequisites or contributing factors for CH-DR success. Therefore, installing Nutanix Guest Tools on the source VM is mandatory for successful cross-hypervisor recovery.

Nutanix Categories allow administrators to group related VMs, making Disaster Recovery (DR) planning easier.

Option B (Utilize Categories to organize VMs in Recovery Plans) is correct:

Categories help group VMsbased on application tiers(e.g.,database, middleware, web servers).

This ensuresorderly failoverwhile maintaining application dependencies.

Option A (Naming schema) is incorrect:

Naming conventions help, but theydo not provide functional organizationin recovery plans.

Option C (1:10 Recovery Plan to VMs) is incorrect:

The ratio depends onbusiness requirements, not a fixed number.

Option D (RESTful APIs) is incorrect:

Automation is useful, butit does not replace proper VM grouping via categories.

By default, Nutanix Prism Central retains the last 10 instances of a report if no retention policy is configured.

Option B (10) is correct:

Nutanixstores up to 10 reports, after which older reports areautomatically deleted.

Options A (5), C (15), and D (20) are incorrect:

Whileretention policies can be customized, thedefault setting is 10 reports.

Application discovery in Prism Central requires sufficient Prism Central resources and an active internet connection to retrieve application signatures.

Option A (Sufficient Prism Central VM resources) is correct:

Prism Central needsadequate CPU and memoryto process application signatures and discovery data.

Option B (Internet connection) is correct:

Application discovery depends on Nutanix’scloud databaseto recognize application patterns.

Option C (API key and key ID) is incorrect:

API keys are not requiredfor automatic application discovery.

Option D (Network controller enabled) is incorrect:

Application discoverydoes not depend on a network controller feature.

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

The Nutanix ECA course covers various methods for organizing and managing virtual machines (VMs) within a Nutanix environment, particularly in Prism Central. The question focuses on easily grouping a set of VMs, which requires a mechanism that is flexible, scalable, and straightforward to apply across multiple VMs for management, reporting, or policy application.

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

Module: Prism Central Management, Section: Entity Organization"Tags provide a flexible way to group entities such as VMs in Prism Central. Tags are key-value pairs that can be assigned to VMs to categorize them for management, reporting, or policy enforcement. They are easy to apply and can be used to group VMs dynamically across clusters."

Module: VM Management, Section: Grouping VMs"To group a set of VMs for simplified management, Tags are the recommended approach. Unlike Categories, which are used for role-based access control and policy enforcement, Tags are lightweight and ideal for custom grouping without additional configuration overhead."

Explanation of Options:

A. Catalog ItemsThis is incorrect. Catalog Items in Nutanix are used within the Nutanix Calm or Marketplace to manage application blueprints or service offerings, not for grouping VMs. The ECA course states:"Catalog Items represent deployable applications or services in the Marketplace, not a mechanism for grouping existing VMs."They are unrelated to VM organization.

B. LabelsThis is incorrect. The term "Labels" is not used in Nutanix ECA documentation for grouping VMs. While Labels may be a generic term in other platforms, Nutanix uses "Tags" or "Categories" for similar purposes. The ECA materials do not reference Labels as a feature in Prism Central or Prism Element for VM grouping.

C. ProjectsThis is incorrect. Projects in Nutanix Prism Central are used to manage resources, users, and policies for a group of workloads, typically for multi-tenancy or resource allocation. While VMs can be associated with Projects, this involves additional configuration (e.g., assigning users, quotas, and policies) and is not the easiest way to group VMs. The ECA course notes:"Projects are used for resource governance and multi-tenancy, requiring additional setup compared to Tags for simple VM grouping."

D. TagsThis is the correct answer. Tags are lightweight, user-defined key-value pairs that can be applied to VMs in Prism Central to group them for management, monitoring, or reporting purposes. The ECA course emphasizes that Tags are easy to assign and manage, making them ideal for grouping VMs without the overhead of other mechanisms like Categories or Projects. Tags can be applied to multiple VMs at once and used in searches, dashboards, or scripts.

Supporting Extract:"Tags allow administrators to quickly group VMs by assigning custom key-value pairs, such as ‘Department: HR’ or ‘Environment: Production.’ They are ideal for ad-hoc grouping and can be leveraged in Prism Central for filtering and management tasks."

Additional Context from ECA:

Tags are managed in Prism Central under theEntities > Tagssection, where administrators can create, assign, and manage Tags for VMs and other entities. The ECA course highlights their simplicity:"Tags require minimal configuration and can be applied to VMs in bulk, making them the easiest method for grouping."

Unlike Categories, which are used for policy enforcement (e.g., security or placement policies), Tags are purely for organizational purposes, aligning with the question’s focus on ease of use.

Supporting Reference from Web Results:

The Nutanix Bible (https://www.nutanix.com/go/the-nutanix-bible) aligns with the ECA documentation: "Tags in Prism Central provide a simple and flexible way to organize VMs and other entities, enabling administrators to group resources for management or reporting without complex configurations."

The requirement states:

• Custom apps use Volume Groups

• VM + VG must remain consistent together

• Lowest possible RPO is required (RPO → 0)

• Must survive cluster failure

Nutanix data protection documentation clearly states:

“Synchronous replication provides an RPO of zero by ensuring every write is committed on both sites before acknowledgement.”

Additionally:

“When protecting application VMs using Volume Groups, both the VM and the Volume Group must be placed in the same Consistency Group to ensure write-order fidelity and to preserve database or application integrity during failover.”

This is critical because Volume Groups operate at the block layer, and placing them in separate groups breaks atomic write-order correctness.

Option analysis:

A. Metro AHV provides HA-style zero RPO but is not the required mechanism here because the question specifically references protection policies and VGs, which Metro does not orchestrate in the same way.

B. Synchronous replication alone is not sufficient unless VMs and VGs are inside the same consistency group.

C. This is the correct and complete solution: synchronous replication + consistency grouping ensures RPO0 and atomic updates.

D. NearSync has RPO 1–15 minutes, not the lowest possible RPO.

Therefore, placing both VMs and VGs in the same consistency group under Synchronous Replication is the correct method.

The Nutanix AHV virtualization guide explains that vGPU-enabled VMs can be live migrated only when the destination host contains compatible GPU hardware and has available vGPU capacity matching the profile assigned to the VM. The documentation states that the VM must have "adequate and equivalent GPU resources on the target host" for migration to proceed. Host affinity is a limiting factor and not a requirement. Agent VMs are not designed to be migrated. Changing the vGPU profile is not necessary as long as the target host supports the currently assigned profile. Therefore, ensuring the destination host has sufficient compatible resources is the required condition.

Snapshots that are part of an active recovery operation cannot be deleted until the process is completed or manually canceled.

Option A (Active recovery in progress) is correct:

Nutanix does not allow deletion of snapshots ifthey are being used in an ongoing recovery process.

The administrator shouldverify whether the snapshot is currently part of a Protection Domain or Disaster Recovery (DR) plan.

Option B (Ransomware encryption) is incorrect:

Nutanix snapshots are immutable by defaultandcannot be encrypted by external threats.

Option C (Approval policy denial) is incorrect:

Snapshot deletionsdo not require manual approval, unless controlled by an external workflow system.

Option D (Snapshot corruption) is incorrect:

Nutanixuses checksums to prevent corruption, so snapshots cannot besilently damaged.

Data-in-Transit Encryption ensures that replication traffic is encrypted while being sent over the internet.

Option D (Enable Data-in-Transit Encryption) is correct:

This encryptsreplicated data between clusters, ensuring security againstman-in-the-middle attacks.

Option A (Self-encrypting drive) is incorrect:

This protects data at rest, not during transmission.

Option B (UEFI Secure Boot) is incorrect:

Secure Boot prevents unauthorized OS modifications, but doesnot encrypt network traffic.

Option C (Data-at-Rest Encryption) is incorrect:

This encryptsstored data but does not secure replication traffic.

In Nutanix Prism Central,categoriesallow administrators togroup and organize entitiesfor management, automation, and policy enforcement.

Alerts (Option B) can be categorizedto group similar system events and create filtering rules.

Virtual Machines (Option C) can be categorizedto apply security policies, automation tasks, and resource allocation rules.

Option A (Storage Containers) cannot be categorizedin Prism Central. Storage policies apply at the container level but are not managed via categories.

Option D (ISO Images) cannot be categorizedbecause ISOs arestatic objects, not active entities.

Metro Availability in Nutanix requires that the primary and secondary storage containers be configured identicallyto ensuredata replication consistency.

Option C (The destination storage container is not empty) is correct:

Theremote storage container must be emptybefore Metro Availability can be enabled.

Existing data can cause conflictsand prevent it from appearing in the "Compatible Remote Sites" list.

Option D (Both storage containers must have the same name) is correct:

Metro Availability requires thatstorage containers have identical names across clusters.

If namesdo not match, thestorage container will not be listed as compatible.

Option A is incorrect: Metro Availability works regardless of hardware vendor differences.

Option B is incorrect:Compression does not affect compatibilitybut may impact performance.

During cluster expansion, Nutanix uses the Controller VM discovery service, which relies on multicast-based node advertisement. The internal architecture documentation states:

“Node discovery during cluster expansion requires IPv4 multicast to be enabled and permitted on the switching infrastructure.”

This allows new nodes to announce themselves to the existing cluster through standard Nutanix discovery packets.

IPv6 multicast is not used for node discovery. Matching AOS or hypervisor versions is recommended for compatibility but not required for discovery itself. These are post-discovery compatibility concerns, not prerequisites.

Thus, IPv4 multicast is required for automatic node discovery.

Offset-based IP mapping in Nutanix Recovery Plans allows automatic subnet changes during DR failover.

Option D (Utilize Recovery Plan Offset-based IP mapping) is correct:

This methodautomatically adjusts the IP rangewhile keeping the same last octet.

It eliminates the need formanual interventionafter failover.

Option A (Custom script) is incorrect:

Scripting is an option, butRecovery Plan IP mapping is simpler and native to Nutanix.

Option B (Use IPAM) is incorrect:

IP Address Management (IPAM) is useful, butoffset-based mapping provides more control.

Option C (Manually update IPs) is incorrect:

This would betime-consuming and error-prone.

Nutanix Multicloud Infrastructure documentation explains that Recovery Plans and Protection Policies are designed to scale using Categories rather than per-VM assignments. Categories provide metadata that allows grouping of VMs by purpose, business unit, application tiers, boot order, and network requirements. The documentation states that Recovery Plans "consume categories so that VMs matching those categories are automatically included in the DR workflow." Categories also allow automatic updates so that when a VM is added, removed, or changed, the DR plan does not require modification. This method is specifically recommended for environments with numerous workloads and variable application tiers. Scripts, naming conventions, and static ratios do not provide the dynamic grouping and automation that categories provide.

Upgrading an AHV host with GPUs requires that the correct GPU drivers be manually uploaded to LCM, as GPU firmware is not updated automatically.

Option C (Use Direct Uploads to upload appropriate driver bundles) is correct:

LCM does notautomatically fetch GPU drivers.

The administrator mustdownload and manually upload the appropriate firmware bundlebefore upgrading.

Option A is incorrect:

Agent VMs are not requiredfor GPU updates.

Option B is incorrect:

Running LCM indark site mode does not impact GPU firmware updates.

Option D is incorrect:

Updating NCCis a best practice but does not resolve GPU driver issues.

A single vCPU is likely causing a bottleneck, limiting the VM’s ability to process I/O requests efficiently.

Option D (Increase the VM’s number of vCPUs) is correct:

Windowsrequires sufficient CPU resourcesto handle disk and network operations.

Adding more vCPUs allows the VM to process more I/O operations simultaneously, improving performance.

Option A is incorrect:

AdditionalvSCSI controllers are only useful for very high disk I/O workloads.

Option B is incorrect:

Balance-TCP applies to network traffic, not storage performance.

Option C is incorrect:

CVM resources do not directly affect individual VM performance.