Nutanix NCP-CI-AWS Practice Test Questions Answers

Synchronous replication in Nutanix Cloud Clusters (NC2) on AWS requires extremely low latency, typically less than 5ms round-trip time (RTT). To achieve this, clusters must be located within the same AWS region, often within different Availability Zones or the same VPC.

Supported networking configurations for this high-speed data exchange include using standard native AWS networking on both clusters to ensure direct, low-latency communication. Additionally, a hybrid setup where one cluster utilizes native networking and the remote cluster uses Flow Virtual Networking (FVN) is supported, provided the underlying network infrastructure satisfies the latency requirements for synchronous operations. This ensures that data is written to both clusters simultaneously before an acknowledgment is sent to the application, providing zero recovery point objective (RPO).

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.

A valid CIDR range: A CIDR (Classless Inter-Domain Routing) range is necessary for creating the subnets within the VPC. This range defines the IP address space for the cluster and its components.

A my.nutanix.com account: This account is required to access Nutanix services, including the NC2 console, manage licenses, and perform other administrative tasks.

AWS Direct Connect and an on-premises Prism Central environment are not prerequisites for deploying an NC2 on AWS cluster. While Direct Connect can be used for enhanced network performance and connectivity, it is not a requirement for deployment. Similarly, having an on-premises Prism Central environment is not mandatory for NC2 deployment on AWS.

Refer to the Nutanix documentation on NC2 prerequisites and setup guides, and AWS documentation on VPC and subnet creation.

For environments requiring highly flexible and complex network addressing,Flow Virtual Networking (FVN)is the superior choice over standard native AWS networking. Native AWS networking is often restricted by the CIDR blocks of the VPC, and managing non-contiguous ranges across multiple subnets can become administratively burdensome.FVNuses an overlay architecture (Geneve) that abstracts the User VM networking from the physical AWS VPC infrastructure. This allows administrators to define virtual networks and subnets using any IP range, including multiplenon-contiguous CIDR ranges, without being constrained by the primary VPC address space. This flexibility is essential for large-scale deployments or multi-tenant environments where overlapping or non-standard IP schemes must be supported seamlessly.

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.