Nutanix NCP-CI-AWS Nutanix Certified Professional - Cloud Integration - AWS (NCP-CI-AWS 6.10) Exam Exam Practice Test

When managing Nutanix licenses for NC2, administrators can reserve capacity from their existing licenses to ensure dedicated resource availability for cloud deployments.

This reserved capacity is flexible; it is not tied to a single cluster but can cover the usage of all NC2 clusters operating within the same workspace, simplifying license management across multiple deployments. Furthermore, these reservations are not permanent. If a company decides to shift workloads back to their data center, an administrator can unreserve the license by updating the reserved capacity to zero in the Nutanix portal, making that capacity available again for on-premises cluster consumption. This provides a seamless way to manage hybrid cloud licensing costs.

Flow Virtual Networking (FVN)introduces a software-defined overlay that requires significant management overhead for handling VPC transit, encapsulation, and complex routing tables. Due to the resource-intensive nature of managing these advanced networking services, Nutanix restricts the supported Prism Central (PC) instance sizes for FVN deployments. OnlyLarge and Extra LargePrism Central instances are supported to ensure there is adequate CPU and memory available to run the virtual routing and gateway components effectively. Smaller PC instances (Small or Medium) lack the necessary performance headroom and may experience latency or management failures when trying to process the continuous network synchronization required by the FVN overlay in a production cloud environment.

WhenFlow Virtual Networking (FVN)is enabled for an NC2 cluster, Nutanix orchestrates the creation of aTransit VPCto handle traffic between the overlay and external networks. The core subnet created within this Transit VPC is namedoverlay-external-subnet-nonat. This subnet is critical as it serves as the entry and exit point for traffic that should not be subjected to address translation, such as traffic moving between the cloud overlay and an on-premises data center via a Transit Gateway or VPN. While administrators can manually add a NAT-enabled subnet later, the " nonat " variant is the primary default used to ensure that internal corporate communications remain transparent across the hybrid cloud boundary.

To allow wide open access to a particular NC2 AWS cluster from an on-premises subnet (10.19.160.0/24), the proper Custom Security Group formatting needs to include the necessary tags that specify the external cluster UUID and the networks allowed.

Custom Security Group Configuration:

The configuration should include tags to identify the cluster and the networks that should be granted access.

Key: nutanix:clusters

Key: nutanix:clusters:external

Value: < cluster-uuid >

Explanation of Choice:

Option Bincludes the necessary tags and values, ensuring that the specific cluster UUID is recognized and the on-premises subnet (10.19.160.0/24) can communicate with the NC2 cluster.

Security Group Tags:

nutanix:clusters:external- Identifies the cluster as external.

nutanix:clusters:external:cluster-uuid- Specifies the unique identifier for the cluster, enabling proper traffic routing and access.

Nutanix Cloud Clusters on AWS Administration Guide

AWS Security Group Documentation

Nutanix Best Practices for Custom Security Group Configuration

AWS supports EC2 bare-metal instances in regions with at least 3 partitions. Partitions in AWS provide high availability and fault tolerance by distributing instances across different hardware to minimize the impact of hardware failures.

AWS EC2 Bare Metal Instances Documentation

AWS Regions and Availability Zones

Selecting the " I want to protect the cluster " option during the initial NC2 deployment wizard enables the underlying support for theCluster Protectfeature but does not fully finalize the protection policies. Once the bare-metal instances are provisioned and the Nutanix software is initialized, the administrator mustconfigure Cluster Protect after the deployment completes. This " Day Two " configuration involves specifying the Amazon S3 bucket that will serve as the backup target, defining the protection frequency (RPO), and selecting the specific User VMs or Prism Central data to be protected. Since the NCI Ultimate license already includes the advanced replication and protection features by default, no additional add-on purchase is required, but the functional setup of the backup policies remains a mandatory post-deployment task.

When reserving licenses for Nutanix Cloud Clusters (NC2), administrators must understand the inclusion of add-ons within different tiers. For organizations requiring multi-protocol storage, the Nutanix Unified Storage (NUS) add-on is flexible and can be associated with either the NCI Pro or NCI Ultimate licensing tiers. Furthermore, the NCI Ultimate tier is designed to be comprehensive; it automatically includes high-value features such as Advanced Replication and Security (Microsegmentation) by default. This simplifies the licensing process because these features do not require separate manual applications once the Ultimate tier is selected. While NCI Ultimate is feature-rich, it does not include the NUS add-on by default, which remains a capacity-based selection that must be specifically managed alongside the base license tier.

The scalability of Nutanix Cloud Clusters (NC2) on AWS is a critical architectural consideration for high-growth environments. While earlier versions or specific regions might have different baseline limits, the maximum size for a single NC2 cluster on AWS is officially supported up to28 nodes. This limit is designed to balance the performance benefits of the Nutanix Distributed Storage Fabric (DSF) with the underlying AWS bare-metal infrastructure and networking constraints. Expanding a cluster to this size allows for significant workload consolidation and high availability within a single management domain. Administrators must ensure that their AWS account quotas and VPC subnet sizing are sufficient to accommodate the vCPU and IP address requirements associated with a 28-node deployment to prevent provisioning failures.

To ensure that every NC2 on AWS cluster deployed allows full access from the on-premises CVM subnet efficiently, the administrator should create a custom AWS Network Security Group.

Use a key value oftag:nutanix:clusters:externalfor the security group, and set the inbound allow address to the on-premises subnet.

This approach leverages AWS tags to manage security group rules dynamically and ensures that the necessary access permissions are applied automatically to all clusters with the specified tag.

This method reduces the need for manual configuration of each cluster ' s security group, streamlining the process for a test/dev environment where clusters are frequently created and destroyed.

Refer to the AWS documentation on Network Security Groups and Nutanix documentation on best practices for securing NC2 clusters.

When extending a Layer 2 subnet from on-premises to NC2 on AWS, the default gateway often remains at the on-premises location.

For Virtual Machines (VMs) running on the NC2 cluster in AWS to communicate with resources outside their immediate subnet, their traffic must be directed back through the tunnel to the on-premises gateway. This is achieved by configuring arouting policyon the NC2 cluster with aForward action. This policy identifies traffic destined for the gateway and encapsulates it via the VTEP (VXLAN Tunnel Endpoint) using port 4789. Without this forward action policy, the AWS-based VMs would attempt to find a local gateway within the AWS VPC, resulting in a loss of connectivity for any North-South traffic.

NC2 on AWS allows for the dynamic addition ofAmazon EBS volumesto bare-metal nodes to expand the cluster ' s storage capacity beyond the local NVMe drives. According to Nutanix architectural guidelines, once these EBS volumes are attached and integrated into the storage pool, the capacitycan only be increased. Reducing the storage capacity by removing or shrinking attached EBS volumes is not a supported operation because it would risk data loss and disrupt the Distributed Storage Fabric (DSF) which expects consistent disk availability. Therefore, administrators should carefully size their initial EBS requirements, knowing that they can scale up to meet demand but cannot scale back the capacity of individual existing volumes without a complex data migration or cluster redeployment.

The Nutanix disaster recovery capabilities include recovery plans that define how entities are recovered in the event of a failure. There is a limit to the number of entities that can be managed within a single recovery plan.

Entity Limit:

According to Nutanix documentation, the maximum number of entities that can be recovered using a single recovery plan is 300. Exceeding this limit will cause issues during the execution of the recovery plan.

Impact of Exceeding the Limit:

If the number of entities in a recovery plan exceeds the supported limit, the recovery process may fail or not execute correctly, as observed in the scenario.

Nutanix Cloud Clusters on AWS Administration Guide

Nutanix Disaster Recovery Best Practices Documentation

When creating a new NC2 cluster using an existing AWS VPC infrastructure, two private subnets are needed. These subnets are used as follows:

One private subnet for user VMs, which houses the virtual machines that users interact with.

Another private subnet for cluster management, which is used for internal cluster operations and management tasks, ensuring that management traffic is isolated from user traffic for security and performance reasons.

Nutanix Support and Insights

Nutanix Cloud Clusters on AWS Administration

To ensure that alert emails are sent properly from Prism Central within an NC2 environment, configuring an SMTP server in the Prism Central settings is required. The SMTP server facilitates the sending of email notifications for alerts and other communications.

SMTP Configuration:

Prism Central requires an SMTP server to send email alerts. This involves specifying the SMTP server address, port, and authentication details if needed.

The configuration must include the email address from which the alerts will be sent and the recipient addresses.

Steps to Configure SMTP Server in Prism Central:

Log in to Prism Central.

Navigate to the " Settings " menu.

Select " Email Server " under the " Alerts " section.

Enter the SMTP server details, including the server address, port, and authentication credentials.

Test the configuration to ensure emails are sent correctly.

Nutanix Prism Central Administration Guide

Nutanix Support Documentation on Email Alert Configuration

Best Practices for Configuring SMTP Servers in Cloud Environments

When establishing a landing zone in a brand new AWS region for NC2 with Flow Virtual Networking (FVN), the network team must provision specific subnets to support the management plane and the transit architecture. The first essential component is theFVN Overlay External Subnet, which resides within the Transit VPC and acts as the entry/exit point for traffic moving between the overlay network and external environments like the internet or on-premises data centers. The second requirement is a dedicatedPrism Central subnet, which is necessary to host the Prism Central instance that will manage the NC2 clusters within that region. These subnets provide the structural foundation for the software-defined networking overlay, ensuring that management traffic is properly segregated from user workload traffic and that the transit gateway logic has a designated physical network path.

Synchronous replication requires extremely low latency (typically sub-5ms) and high throughput between the primary and secondary storage controllers. While Flow Virtual Networking (FVN) supports various multi-VPC architectures, the most robust and supported configuration for synchronous replication within a single AWS region is to ensure that both clusters reside within the same AWS VPC. This placement minimizes network hops and avoids the additional latency that might be introduced by VPC Peering or Transit Gateway traversal between separate VPCs. By sharing the same VPC, the clusters communicate over the same high-speed internal AWS network fabric, providing the deterministic performance and zero-RPO data protection required for synchronous data writes and Metro Availability configurations.

Flow Virtual Networking (FVN)usesGeneve encapsulation, which adds 58 bytes of overhead to every packet. On a standard 1,500-byte network, the effective MTU for the payload is reduced to1442 bytes. While Nutanix attempts to communicate this to User VMs (UVMs) via DHCP, some operating systems or static configurations ignore these advertisements. If a UVM sends a full 1,500-byte packet, the encapsulated packet (1,558 bytes) will be dropped by the AWS physical network. To resolve this, the administrator mustenable jumbo MTU on the UVMs(typically 9,001 bytes in AWS). By allowing the UVM to process larger packets or properly fragment them, the AHV host can successfully encapsulate and transmit the traffic over the underlying AWS infrastructure without fragmentation errors or packet loss.

To manually create an AWS VPC with Public access to Prism Element for testing purposes, the following components must be created:

VPC: A Virtual Private Cloud to provide an isolated network for the resources.

Delegated Subnets: Subnets within the VPC to segment the network and allocate IP ranges.

Route Tables: To define routing rules for the subnets to ensure proper traffic flow.

NAT Gateway: To enable instances in the private subnets to access the internet.

Internet Gateway: To allow direct internet access to instances in the public subnets.

Load Balancer: To distribute traffic across multiple instances for improved availability and redundancy.

Refer to the AWS documentation on VPC creation and Nutanix documentation on network setup for Prism Element access.

To ensure that the newly created NC2 organization named Finance can only deploy clusters into certain cloud regions, the administrator should specify the allowed regions during the cloud account configuration.

This action restricts the regions available for cluster deployment, ensuring compliance with organizational policies or regulatory requirements.

The allowed regions can be set in the cloud account settings associated with the Finance NC2 organization, defining the geographical scope of operations.

Refer to the Nutanix documentation on NC2 cloud account configuration and region restrictions.

TheCluster Protectfeature is the native Nutanix solution designed specifically for NC2 on AWS to protect both the cluster data and thePrism Centralmanagement instance. Unlike standard replication, Cluster Protect utilizesAmazon S3 bucketsto store snapshots of the cluster configuration, Prism Central metadata, and User VM data. This is considered the " best way " for native protection because the entire recovery workflow is orchestrated directly from theNC2 console. If a cluster or an entire Availability Zone fails, the administrator can use the NC2 portal to redeploy the cluster and restore the Prism Central instance and data from the S3 bucket, eliminating the need for third-party backup software while maintaining a simple cloud-native recovery path.

When configuring a syslog server in the Prism Central Admin Center for Nutanix, one of the available log modules is Acropolis.

The Acropolis module logs system events related to the Nutanix Acropolis operating system, which is critical for monitoring and auditing system activities and performance.

Configuring syslog with the Acropolis module ensures that important events and issues related to the Acropolis environment are captured and can be forwarded to an external syslog server for centralized logging and analysis.

Refer to the Nutanix documentation on Prism Central and syslog configuration for the full list of available log modules and detailed steps for configuration.

The steps, in order, to recover a cluster protected using the Cluster Protect feature when the Prism Central instance was not on the failed cluster are as follows:

Step 1: Set the cluster to the Failed state using the NC2 console to start the recovery workflow.

Step 2: Redeploy the cluster using the NC2 console.

Step 3: Redeploy the Multicloud Snapshot Technology.

Step 4: Recover UVM data by running CLI commands.

Set the cluster to the Failed state using the NC2 console to start the recovery workflow: This step involves marking the cluster as failed to initiate the recovery process.

Redeploy the cluster using the NC2 console: Once the cluster is marked as failed, the next step is to redeploy it using the tools available in the NC2 console.

Redeploy the Multicloud Snapshot Technology: After the cluster is redeployed, the Multicloud Snapshot Technology needs to be redeployed to ensure data consistency and availability.

Recover UVM data by running CLI commands: The final step is to recover the User VM (UVM) data by executing the necessary CLI commands to restore the data from the snapshots or backups.

Nutanix Documentation on Cluster Protect and Recovery Processes

Nutanix Support and Insights

Nutanix Cloud Clusters on AWS Administration

Within an NC2 environment, the Cluster Protect feature can ensure the protection of:

Nutanix Files: This provides file services within the Nutanix ecosystem, and Cluster Protect can safeguard the data stored in Nutanix Files.

Virtual Machine Disks: This ensures that the data stored on virtual machine disks is protected, providing backup and recovery options for the virtual machines running within the cluster.

Nutanix Cloud Clusters on AWS Administration

Nutanix AOS 6.7 Documentation

To avoid IP address conflicts and ensure there are no configuration issues when reusing an existing AWS subnet, the administrator should take the following actions:

aCLI > net.add_to_ip_blacklist 10.79.4.200 aCLI > net.add_to_ip_blacklist 10.79.4.201 (Answer A):

This command adds the specified IP addresses to the blacklist, preventing AHV IPAM from assigning these addresses to any VMs. This ensures that the existing EC2 instances with IPs 10.79.4.200 and 10.79.4.201 are not allocated to other VMs in the NC2 cluster.

Configure the AHV IPAM to use DHCP range 10.79.4.2 -10.79.4.253 (Answer D):

By configuring the AHV IPAM to use a specific DHCP range, you ensure that the IP addresses assigned to the EC2 instances (10.79.4.200 and 10.79.4.201) are not included in the DHCP pool. This prevents IP address conflicts within the subnet.

Nutanix aCLI Reference

Nutanix NC2 on AWS Documentation

AWS VPC and Subnet Basics

To SSH into a Controller VM (CVM) in an NC2 on AWS cluster without on-premises connectivity, the administrator needs to ensure that the security settings allow SSH access from the Jump Host. This involves editing the User Management Network Security Group to permit SSH traffic from the Jump Host IP.

Deploy Jump Host:

Ensure the Jump Host is deployed in a public subnet with an Elastic IP (EIP) assigned for external access.

Edit User Management Network Security Group:

Locate the security group associated with the user management network.

Modify the inbound rules to allow SSH (port 22) from the Jump Host ' s IP address. This ensures that the Jump Host can establish an SSH connection to the CVM.

Steps to Edit Security Group:

Navigate to the EC2 dashboard in the AWS Management Console.

Select " Security Groups " under the " Network and Security " section.

Find and select the appropriate security group.

Edit the inbound rules to add a new rule:

Type: SSH

Protocol: TCP

Port Range: 22

Source: Custom IP (enter the Jump Host ' s public IP address)

Additional Configuration:

Ensure that the CVM itself allows SSH connections and that no internal firewall rules block the traffic.

Nutanix Cloud Clusters on AWS Administration Guide

AWS Security Group Documentation

Nutanix Best Practices for Secure Access

For issues related to cloud hardware support such as EC2 instances, VPC, etc., the public cloud vendor (AWS in this case) should be contacted. AWS provides support and documentation for their infrastructure and services, ensuring that users can get assistance for any hardware or cloud-specific queries.

Nutanix Support and Insights

Given the company ' s large spend commitments as part of an AWS Enterprise Discount Program (EDP) totaling $15 million, purchasing Nutanix licenses through the AWS Marketplace ensures that the costs contribute to the EDP commitment.

This approach integrates the Nutanix license costs into the overall AWS spend, thereby maximizing the benefits of the EDP.

Purchasing directly from Nutanix or leveraging existing licenses might not count towards the AWS EDP commitment, and trial licenses are typically for evaluation purposes and do not contribute to the committed spend.

Refer to the Nutanix and AWS documentation on licensing and marketplace purchases, and EDP program details.

When opting for a native networking deployment (Standard AWS Networking), the architectural requirements differ from an overlay-based setup.

This configuration typically requiresone private management subnetto house the bare-metal hosts and Controller VMs (CVMs). To facilitate outbound communication and administrative access,two public subnetsare required—one for the NAT Gateway to provide internet access to the private nodes, and another to host resources like the Prism load balancer. Finally,one or more User VM (UVM) subnetsare created to host the actual workloads. Unlike Flow Virtual Networking, which uses a single transit VPC, native networking relies on these multiple standard AWS subnets to segregate management, public-facing, and workload traffic within the VPC.

Nutanix offers tailored licensing models for different workload types within NC2 to optimize costs. ForVDI-specific clusters, Nutanix utilizes auser-based consumption model. In this scenario, pricing is determined by the number of concurrent users, which is ideal for elastic desktop environments where the number of active VMs fluctuates. Conversely,general-purpose clusterstypically default to acapacity-based method. Here, consumption is calculated based on the total provisioned capacity (cores or TiB) of the cluster, providing predictable costs for steady-state server workloads. These models allow organizations to align their software spend directly with their actual resource utilization patterns. It is important to note that switching between portfolio types (NCI and AOS) is generally restricted once a cluster is deployed.

During the NC2 cluster creation process, the administrator is presented with options for the licensing portfolio they wish to utilize. Nutanix has transitioned to theNCI (Nutanix Cloud Infrastructure)portfolio, but the legacyAOSportfolio is still available for certain customers. If the " AOS Licenses " option appears greyed out or unselectable, it is typically becausethe administrator did not select AOS in the licensing section of the NC2 Creation Wizard. The wizard requires an explicit choice early in the workflow to determine which features and software tiers (Pro, Ultimate, etc.) will be available for selection later. If the portfolio is not correctly identified at the start, the specific license keys or reservations associated with the legacy AOS model will not be recognized by the deployment engine, defaulting instead to the newer NCI-based consumption model.

In the NC2 console, an organization is used to segregate clusters based on specific requirements. This segregation allows administrators to manage clusters more effectively by grouping them according to business units, projects, or other criteria. This organizational structure helps in maintaining clear boundaries and applying specific policies or permissions to different clusters within the same NC2 environment.

Nutanix Cloud Clusters on AWS Administration

Nutanix Certified Professional - Cloud Integration - AWS

To achieve anRTO (Recovery Time Objective)as low as15 minutesusing Multicloud Snapshot Technology, aPilot Light Deploymentis essential. In this model, a minimal Nutanix cluster is always active in the cloud. This active presence ensures that the Prism Central management layer is ready to receive recovery commands and that the storage containers are already mounted. Because the " compute " is already provisioned, the recovery process simply involves hydrating the snapshots from the S3 bucket and powering on the VMs according to the Recovery Plan. A " Zero Compute " model would exceed this RTO because the time required to provision new bare-metal instances from AWS and initialize the Nutanix software can take significantly longer than 15 minutes.

When using the Nutanix Cluster Protect feature to recover a failed NC2 cluster on AWS, and the management Prism Central (PC) instance is hosted on a separate, healthy cluster, a specific orchestration sequence must be followed. The process begins in the NC2 console, where the administrator must manually change the status of the cluster to Failed. This step is critical as it signals the portal to initiate the recovery workflow and release associated cloud resources. Next, the administrator uses the console to redeploy the cluster, which provisions new bare-metal instances and installs the AOS software. Once the infrastructure is ready, Multicloud Snapshot Technology (MST) must be redeployed or re-enabled on the new cluster to re-establish the connection to the Amazon S3 bucket containing the snapshots. Finally, the User VMs (UVMs) are recovered and hydrated from these snapshots. This specific order ensures that the target environment and management links are fully operational before data restoration commences.

When deploying a new NC2 cluster on AWS, especially when moving to specialized hardware like EC2 dedicated hosts, two critical external factors must be verified: subscription status and AWS resource limits. First, the administrator must ensure that theNC2 subscriptionis active and has sufficient credits or a valid payment method to support the new deployment. Second, AWS imposes default limits on the number ofvCPUsand specific instance types that can be provisioned in a region. Since dedicated hosts consume a large number of vCPUs, the deployment will fail if the AWS account quota is exceeded. Verifying and, if necessary, requesting a quota increase from AWS is a mandatory step to ensure the underlying infrastructure is available for the Nutanix software.

Ensure the specialist is assigned the RBAC role with proper permissions (Answer A):

Role-Based Access Control (RBAC) ensures that the specialist has the necessary permissions to troubleshoot and manage the NC2 environment. This avoids unnecessary privilege escalations and maintains security.

Confirm the Support Authorization on the organization is set to Full Access (Answer C):

Setting the Support Authorization to Full Access allows the Nutanix support specialist to have the required access to investigate and resolve issues in the environment. This is essential for effective troubleshooting.

Nutanix RBAC Documentation

Nutanix Support Access Guide

To enable inbound internet access to Virtual Servers in an NC2 cluster on AWS for the HTTPS protocol, the administrator should use an AWS Network Load Balancer (NLB).

Configure the NLB listener to listen on TCP port 443, which is the standard port for HTTPS traffic.

Create a target group in AWS, and register the servers (Virtual Servers in the NC2 cluster) as targets within this group.

Ensure the NLB is properly configured with an Elastic IP (EIP) if required, to provide a static IP address for the load balancer.

Verify that the security groups and network ACLs associated with the load balancer and the target group allow inbound traffic on port 443.

Refer to AWS documentation on Network Load Balancers and Nutanix NC2 on AWS integration guides for step-by-step instructions on setting up and configuring the necessary components for enabling HTTPS access.

When deploying a new NC2 cluster, the AWS Directory Service must be able to resolve the addressgateway-external-api.cloud.nutanix.com.

This external API gateway is critical for the NC2 cluster to communicate with Nutanix services for operations such as management, updates, and licensing.

Ensuring that this address can be resolved allows the cluster to interact properly with the Nutanix cloud infrastructure and services.

Refer to the Nutanix documentation on network and DNS requirements for NC2 deployments, specifically the addresses that need to be resolvable for proper functionality.

The Cluster Protect feature, which provides data protection and disaster recovery capabilities for Nutanix clusters, requires either the AOS Ultimate or NCI Ultimate license. These licenses include the necessary features to leverage Cluster Protect for ensuring data resilience and recovery.

Nutanix Documentation - Cluster Protection Features

Nutanix AOS 6.7 New Features

In an NC2 heterogeneous cluster (mixing different host types), the ability to addAmazon EBS volumesfor supplemental storage capacity is governed by both host compatibility and cluster redundancy rules. First, the administrator must ensure that the selected host types actually support EBS attachment; if the current selection does not, they mustadd a host type that supports EBS volumes. Second, the cluster must maintain its Replication Factor (RF) integrity. If the number of nodes for a specific storage-heavy host type is not amultiple of the RF(e.g., needing 4 nodes for RF2), the system may restrict storage expansion to prevent data unavailability during a failure. By ensuring the node count aligns with RF requirements and using compatible bare-metal instances, the administrator can unlock the EBS volume configuration options within the deployment workflow.

AWS Direct Connect allows companies to create private, dedicated connections between their data centers and AWS. This bypasses the internet and provides a more reliable and faster network connection directly to AWS services, including S3.

AWS Direct Connect Documentation

AWS S3 Access over Direct Connect

Multicloud Snapshot Technology (MST)provides a cost-effective DR solution by offloading snapshots to cloud storage, but it has specific architectural limitations. First, it is currently limited to theAHV hypervisor; workloads running on ESXi are not supported for MST-based protection. Second, Nutanix allows for the simultaneous use of multiple protection layers; specifically,MST DR and Cluster Protectfeatures can be configured together to provide both local and remote resilience. It is also important to note that MST is designed for asynchronous recovery and is not compatible with Zero-RPO solutions like synchronous replication or AHV Metro at this time. Understanding these hypervisor and configuration constraints is essential when designing a disaster recovery strategy that relies on cloud object storage.

When performing a migration from an NC2 environment to a Nutanix on-premises environment, the task should be performed using the NC2 Prism Central. This is because NC2 Prism Central provides a centralized management interface that allows administrators to manage and migrate workloads between cloud and on-premises environments seamlessly.

Nutanix Cloud Clusters (NC2) Documentation

Nutanix Community Guide