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.

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.

To automate the deployment of a large number of Linux VMs (such as 100), each with similar base configurations but unique hostnames, local configurations, and additional package installations,Cloud-Initis the most appropriate approach. Cloud-Init is a widely supported industry-standard tool for automating the initialization and configuration of Linux instances at first boot.

From theNutanix Enterprise Cloud Administration (ECA)course materials:

“Cloud-Init is the recommended method for configuring Linux virtual machines during deployment in Prism Central. It allows administrators to inject configuration scripts and user data that customize the VM at boot time, including hostname, network settings, user creation, and package installations.”

Specifically:

“Using Cloud-Init, you can create a template or base image for the Linux VMs and then customize each VM deployment by passing individualized configuration parameters, ensuring that while the base configuration remains consistent, each VM has unique settings such as hostname or installed software.”

This method is far superior to manual configuration, which is impractical for 100 VMs, and it’s not suitable to use SysPrep (which is for Windows-based customization). VM templates alone would provide only the base image; they do not address unique per-VM settings.

Therefore,Cloud-Initensures a repeatable, scalable, and fully automated deployment process that aligns with the Nutanix best practices for deploying large numbers of Linux VMs with unique configurations.

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