NCP-CI-AWS Nutanix Certified Professional - Cloud Integration - AWS (NCP-CI-AWS 6.10) Exam Question and Answers

When deploying Windows Server workloads on NC2 on AWS without existing licenses, administrators must carefully choose the tenancy and licensing model to remain compliant with Microsoft ' s cloud mobility rules. For a new deployment where " Bring Your Own License " (BYOL) is not an option due to the lack of existing licenses with Software Assurance, the administrator should select Shared Tenancy with License-included instances. This configuration ensures that the cost of the Windows OS is included in the hourly rate of the bare-metal instances provisioned by AWS. Although the question ' s source Answer (A) lists " BYOL, " standard Nutanix/AWS best practices for unlicensed environments dictate using License-included options on Shared Tenancy to provide the most cost-effective and compliant path for Windows-based virtual machines in the cloud.

Upon creation, each node within an AWS NC2 cluster has3 Amazon Elastic Block Store (EBS)volumes attached.

These volumes are used for different purposes, such as operating system storage, Nutanix services, and user data storage.

The number of EBS volumes is designed to ensure adequate storage performance and capacity for the NC2 cluster ' s operations and workload demands.

Refer to the Nutanix documentation on NC2 cluster setup and AWS EBS volume configurations to confirm the details on the number and purpose of EBS volumes attached to each node.

When creating user VM subnets for multiple NC2 clusters in AWS, the best approach is to create guest-VM subnets for each cluster. This ensures that each cluster has its own dedicated subnets, which simplifies network management and avoids potential IP conflicts.

Advantages of Dedicated Subnets:

Isolation: Each cluster operates in its own subnet, providing better isolation and security.

Management: Easier to manage and troubleshoot network issues when each cluster has its own subnets.

Scalability: More scalable as each subnet can be managed and expanded independently.

Steps to Create Guest-VM Subnets:

Identify the IP range for each subnet.

In the AWS VPC console, create a new subnet for each cluster using the identified IP ranges.

Associate the new subnets with the respective clusters during or after the cluster deployment process.

Why Not Shared Subnets:

Shared subnetscould lead to IP conflicts and make network management more complex, especially as the number of clusters grows.

Nutanix Cloud Clusters on AWS Administration Guide

AWS VPC Subnet Creation 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

When a node is marked as " Condemned, " it indicates that the system has determined that the node is no longer reliable for operations. As part of the automated recovery and protection process, the following action is typically taken:

The node has a power reset sent to it (Answer A):

In most cases, a condemned node undergoes a power reset as an initial recovery attempt. This action attempts to reboot the node to bring it back to a healthy state. If the reset fails, further manual or automated steps may be required to address the hardware or software issue.

Nutanix Cluster Management Documentation

Nutanix Support Knowledge Base

In an NC2 environment using Flow Virtual Networking (FVN), the External Routable Prefix (ERP) is used to identify the address space that can reach external networks. If the ERP is correctly configured in both the Transit and User VPCs but outbound communication still fails, the issue typically lies within the virtual routing table. A static route (such as 0.0.0.0/0) must be manually added to the User VPC routing table with the next hop set to the overlay-external-subnet. Without this explicit static route, the virtual router within the User VPC does not know how to direct traffic toward the Transit VPC for outbound delivery, even if the address ranges are theoretically compatible. Verifying this routing path is a standard step in ensuring overlay workloads can reach on-premises or internet resources.

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.

For VDI workloads that require GPU acceleration, the g4dn.metal nodes are the appropriate choice. These instances are equipped with NVIDIA T4 GPUs, which are well-suited for graphics-intensive applications such as VDI workloads that need GPU acceleration. Other node types like AN36P, m6g.metal, or AN36 do not provide the necessary GPU capabilities.

Nutanix Support and Insights - GPU support in AWS

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.

Route tables for cloud subnets contain incorrect route entries:

If the route tables associated with the cloud subnets contain incorrect route entries, the NC2 cluster might not be able to reach the necessary AWS services or endpoints. Correct route entries are crucial for ensuring proper communication between the NC2 cluster and the underlying AWS infrastructure.

IAM roles and policies are incorrectly configured:

Incorrectly configured IAM roles and policies can prevent NC2 from making API calls to AWS services. These roles and policies must be properly set up to allow the necessary permissions for NC2 to interact with AWS resources and perform required operations.

Refer to the AWS documentation on route table configuration and IAM roles and policies, and Nutanix documentation on NC2 cloud connectivity and permissions.

Successful onboarding of an AWS environment into the Nutanix Cloud Clusters ecosystem requires a precise set of administrative permissions to be present on the account used for initial configuration. Specifically, the AWS user must haveCreateRoleFullAccessto allow the automated scripts to generate the necessary service-linked roles. Additionally, the user must possessIAMFullAccessto manage identity policies andAWSCloudFormationFullAccessto execute the deployment templates. This specific combination ensures that the NC2 portal can correctly configure the " Cross-Account Role " which serves as the primary communication bridge between the Nutanix management plane and the AWS infrastructure APIs. Failing to provide any of these three core permissions will result in an " Insufficient Permissions " alert during the cloud account registration process.

For a new NC2 on AWS deployment where workload VMs have low storage and memory requirements but high CPU frequency ( > 3.0 GHz) requirements, and the goal is to minimize the number of CPU cores to reduce application licensing costs, thei3.metalinstance type is the most suitable.

i3.metal:

High CPU Frequency: i3.metal instances offer high-frequency Intel Xeon processors (up to 3.1 GHz) which meet the high CPU frequency requirement.

Low Storage and Memory: These instances come with a balanced amount of storage and memory, suitable for workloads with low requirements in these areas.

Minimized CPU Cores: i3.metal instances have fewer CPU cores compared to other high-frequency instances like i4i.metal, making them ideal for minimizing application licensing costs.

Other Instance Types:

z1d.metal: While also offering high CPU frequency, these instances typically come with a higher core count and more memory, which may not be optimal for minimizing licensing costs.

i4i.metal: Designed for I/O intensive applications with higher core counts.

m5d.metal: Balanced instance type but with more cores and not as high CPU frequency as required.

AWS EC2 Instance Types Documentation

Nutanix Cloud Clusters on AWS Administration Guide

Nutanix Best Practices for Instance Selection

To create a cluster in Nutanix Cloud Integration with AWS, the role needed is Cluster Super Admin.

The Cluster Super Admin role provides the highest level of privileges required to perform critical operations such as creating, managing, and deleting clusters.

This role is essential for overseeing the cluster setup and configuration processes, ensuring the user has full control over the cluster lifecycle.

Refer to the Nutanix documentation on roles and permissions for NC2 on AWS for further details on the capabilities and required permissions for cluster creation.

Nutanix provides a flexible licensing model for NC2, allowing customers to use their existingon-premises licensesthrough reservation. A key benefit of this approach is thatreserved licensed capacity automatically handles incidental overages. If a cluster temporarily scales out and exceeds the reserved capacity, the Nutanix billing system accounts for the excess usage automatically, typically by drawing from the associated Pay-As-You-Go (PAYG) account or consumption credits. This ensures that the cluster remains operational and compliant even during unexpected spikes in demand. Administrators can manage these reservations through the Nutanix portal, allowing them to balance their committed on-premises license spend with the variable needs of their cloud-resident clusters.

To provide VMs with outbound internet connectivity in AWS using a private subnet, the administrator needs to create the following components in the VPC:

Private Subnet: A private subnet is required to house the VMs that need outbound internet access but do not require direct inbound access from the internet.

NAT Gateway: A NAT (Network Address Translation) Gateway is necessary to allow instances in the private subnet to connect to the internet or other AWS services while preventing the internet from initiating a connection with those instances.

Public EIP (Elastic IP Address): An EIP is associated with the NAT Gateway to provide a persistent public IP address that allows outbound internet traffic from the private subnet to be routed correctly.

Route Table: A route table is configured to route traffic from the private subnet to the NAT Gateway for outbound internet access.

AWS NAT Gateway Documentation

AWS VPC Subnet Basics

To create a CloudFormation stack, the AWSCloudFormationFullAccess role is required.

This role grants the necessary permissions to create, update, and delete CloudFormation stacks, which are essential for deploying and managing AWS infrastructure using CloudFormation templates.

CloudFormation stacks are often used to automate the deployment of complex infrastructures, including those required for NC2 on AWS.

Proper permissions ensure that the deployment process is seamless and adheres to the security and operational policies of the organization.

Refer to the AWS IAM documentation for details on the AWSCloudFormationFullAccess role and Nutanix documentation on prerequisites for deploying NC2 on AWS.

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

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

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.

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.

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

The maximum number of nodes supported in an NC2 cluster on AWS is 24 nodes. This limit ensures optimal performance and manageability within the AWS infrastructure while leveraging the benefits of the Nutanix architecture.

Nutanix Clusters on AWS Deployment Guide

Nutanix Support and Insights

The NC2 Tile within the my.nutanix.com portal is the correct interface to deploy NC2. This portal provides an integrated and user-friendly interface specifically designed for deploying and managing Nutanix Clusters on AWS.

NC2 Deployment Interface:

NC2 Tile within the my.nutanix.com portal: This portal provides the necessary tools and options to deploy and manage NC2 clusters. It includes functionalities for setting up the clusters, configuring network settings, and managing resources.

Advantages:

User-Friendly Interface: Simplifies the deployment process with a guided setup.

Integrated Tools: Provides access to all necessary tools for managing the deployment and monitoring of NC2 clusters.

Nutanix Cloud Clusters on AWS Administration Guide

Nutanix my.nutanix.com Portal Documentation

Nutanix Best Practices for Cluster Deployment

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.

With the Nutanix AOS Pro licensing, several advanced features and add-on products become available. Specifically, in the AWS cluster deployment wizard, the following add-ons are available:

Files:

Nutanix Files provides a software-defined, scale-out file storage solution that simplifies the management and scaling of unstructured data.

Advanced Replication:

Advanced Replication features in Nutanix include synchronous and asynchronous replication capabilities, allowing for robust disaster recovery and data protection solutions.

DARE (Data-At-Rest Encryption):

DARE ensures that all data stored on Nutanix clusters is encrypted, providing a higher level of security for sensitive information.

These features are included in the AOS Pro licensing tier, offering enhanced data management, protection, and security capabilities.

Nutanix Licensing Guide

Nutanix Cloud Clusters on AWS Administration Guide

Nutanix Best Practices for Advanced Features

The alert indicates a potential issue with the VPC/Subnet settings, preventing the cluster nodes from contacting Nutanix services.

To resolve this, the administrator needs to ensure that the subnet 10.0.1.0/24, which is assigned for Bare metal hosts, has an outbound Internet connection.

This connection is necessary for the cluster nodes to communicate with external Nutanix services for updates, license validation, and other essential operations.

Verify that there are appropriate route tables and security group rules allowing outbound traffic to the Internet from the 10.0.1.0/24 subnet.

Ensure that there is either an Internet Gateway (IGW) attached to the VPC or a NAT Gateway configured if using private subnets.

Refer to the Nutanix documentation and AWS VPC configuration guides to ensure proper Internet connectivity and routing setups.

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

AVTEP (VXLAN Tunnel Endpoint) Gatewayshowing a status of " Down " indicates a connectivity or configuration failure within the control plane. In an NC2 environment, the gateway relies on consistent communication withPrism Central (PC)for management and synchronization, as well asNTP and DNSfor time-sync and name resolution. If the route tables in the AWS VPC are missing the necessary entries to reach these management services, the VTEP gateway will fail to initialize or maintain its heartbeat, resulting in a " Down " status. While on-premises reachability is important for traffic flow, the failure to create the extension entirely usually points to these missing internal routes that prevent the Nutanix software components from coordinating correctly within the cloud environment.

When connectivity is required between two separate AWS VPCs—one hosting native EC2 instances and the other hosting an NC2 cluster—and advanced overlay networking (FVN) is not in use, the most straightforward solution is VPC Peering. Configuring VPC Peering in Amazon Web Services allows for the routing of traffic between the two VPCs using private IP addresses as if they were on the same network. This method requires the least administrative effort because it does not require the deployment of new software overlays like FVN or the management of a complex Transit Gateway. Administrators simply need to establish the peering connection and update the route tables in both VPCs to allow traffic to flow between the respective CIDR ranges, providing secure, high-performance connectivity.

AHV (Answer A):

AHV (Acropolis Hypervisor) can be upgraded using Lifecycle Manager (LCM). LCM simplifies the upgrade process and ensures that all components are updated in a coordinated manner.

BIOS (Answer C):

BIOS upgrades can also be performed using LCM. This helps in maintaining hardware compatibility and performance by ensuring that the latest firmware is installed.

Nutanix Lifecycle Manager (LCM) Documentation

Nutanix AHV Upgrade Guide

Nutanix BIOS Upgrade Documentation

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

Deploying NC2 on AWS requires the creation of specific IAM roles and policies to allow the Nutanix service to manage AWS resources like EC2 instances and VPCs. This is typically handled by an automatedCloudFormation stack. For this process to succeed, the AWS user executing the script must possess high-level administrative permissions. Specifically, they requireIAMFullAccessto create the necessary roles andAWSCloudFormationFullAccessto deploy and manage the stack itself. Without these permissions, the CloudFormation template will fail to create the security identities required for the NC2 console to communicate with the AWS API. This is a one-time prerequisite for onboarding the AWS account into the NC2 organization.

Nutanix offers a free trial to allow organizations to test NC2 capabilities.

This trial is flexible; users can initiate a separate 30-day free trial for each supported cloud provider, such as AWS and Azure, allowing for independent evaluations of different cloud environments. It is important to note that the " free " aspect of the trial applies only to theNutanix software licensing. The user is still responsible for allAWS infrastructure costs(bare-metal instances, storage, and data transfer) incurred during the trial period. Additionally, users are not restricted to the trial alone; they can choose to activate aPay-As-You-Go (PAYG)subscription even while the free trial is active to ensure a smooth transition to production after the evaluation ends.

The role of " Customer Administrator " in Nutanix Cloud Integration with AWS (NC2) is designed to meet the requirements of creating and managing multiple organizations and clusters, as well as managing user access for the entire company.

Roles and Permissions:

Customer Administrator: This role has the broadest set of permissions, allowing the user to create and manage organizations, clusters, and user access across the entire company. It encompasses administrative control over multiple aspects of the NC2 environment.

Capabilities:

Organization Management: Ability to create and manage multiple organizations.

Cluster Management: Full control over creating, configuring, and managing clusters.

User Access Management: Manage user roles and permissions, ensuring that the right individuals have access to the necessary resources.

Why Not Other Roles:

Organization Administrator: Limited to managing organizations but not clusters and user access at the company level.

Customer Security Administrator: Focuses on security aspects, lacking broader administrative capabilities.

Cluster Administrator: Limited to managing clusters without the ability to manage organizations and user access comprehensively.

Nutanix Cloud Clusters on AWS Administration Guide

Nutanix Role-Based Access Control Documentation

The 192.168.5.0/24 range is often reserved for internal cluster communication within Nutanix deployments.

Using this CIDR range for other purposes could lead to network conflicts and connectivity issues, as it might interfere with the internal operations and communication channels of the Nutanix cluster.

Ensuring that the CIDR range is not overlapping with any reserved ranges is crucial for maintaining proper network connectivity and cluster functionality.

Refer to the Nutanix documentation on network configuration and best practices for NC2 deployments to confirm reserved IP ranges and their appropriate use.

To control network traffic at the individual User VM (UVM) subnet level, creating a custom security group is the appropriate action. This approach allows for fine-grained control over inbound and outbound traffic rules that can be applied to specific subnets or individual instances within those subnets.

Custom Security Group:

Custom security groups enable administrators to define specific traffic rules tailored to the needs of individual subnets or VMs. This includes specifying allowed IP ranges, ports, and protocols.

By applying these custom security groups to the UVMs, the organization can control access and enhance security according to their policies and requirements.

Steps to Create a Custom Security Group:

Navigate to the AWS Management Console and go to the VPC service.

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

Click on " Create Security Group " and define the name, description, and VPC.

Add inbound and outbound rules according to the desired traffic control policies.

Attach the custom security group to the UVMs or subnets in question.

Nutanix Cloud Clusters on AWS Administration Guide

AWS Security Group Documentation

Nutanix Best Practices for Security Groups

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