Free Practice Questions for Nutanix NCP-CI-AWS Exam

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

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.

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.

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.

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

In an NC2 on AWS deployment using Flow Virtual Networking (FVN),North-South traffic(traffic moving into or out of the Nutanix VPC) is handled via adistributed gateway model. Unlike traditional setups that might rely on a single bottleneck node, the distributed gateway model allows each Nutanix node in the cluster to participate in routing traffic to the AWS VPC router. This architecture provides high availability and scales performance linearly as nodes are added to the cluster. By distributing the gateway function, Nutanix ensures that no single point of failure exists for internet-bound or cross-VPC traffic, optimizing the path between Nutanix User VMs and native AWS services or the public internet.

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

Migrating an existing NC2 cluster from native AWS networking to an overlay network (Flow Virtual Networking) requires careful coordination between the Nutanix software and the AWS environment. A primary prerequisite is ensuring thatExternal IPAMis correctly configured for the cloud subnets to manage the IP address lifecycle within the new overlay. Additionally, the administrator must ensure thatcorresponding cloud subnets are added in the Prism Element UI and mapped to the existing AWS subnets. This mapping is essential for the Nutanix Controller VMs (CVMs) and AHV hosts to properly encapsulate and route traffic between the virtual overlay and the physical AWS VPC infrastructure. Validating these configurations prevents IP conflicts and connectivity loss during the transition from standard VPC routing to the software-defined Geneve-encapsulated overlay.

While NC2 bare-metal instances come with high-performance local NVMe storage, many organizations require additional capacity to support large data sets or long-term storage needs. For instance types that support Amazon EBS attachment, theminimum number of additional EBS volumesthat can be added per node is1. Adding even a single EBS volume allows the Nutanix cluster to expand its storage pool beyond the physical limitations of the bare-metal chassis. Administrators can then increase this capacity as needed, although once attached, these volumes typically cannot be removed or decreased. This flexibility is key for scaling storage-intensive applications without necessarily increasing the compute node count, thereby optimizing the overall TCO of the cloud cluster.

Bare-metal EC2 instances are a specialized resource in AWS, and their availability can sometimes be limited within a specific region or Availability Zone. If an administrator attempts to expand an NC2 cluster and the requested instance types are out of stock at the AWS level, the NC2 console will attempt to provision the nodes but will eventually reach aretry limit and fail. The portal does not indefinitely hold the cluster in maintenance mode. Instead, the administrator is responsible for verifying node availability through the AWS Service Health Dashboard or AWS support. If the desired instance type (e.g., i3.metal) is unavailable, the administrator may need to consider expanding into a different Availability Zone or choosing a different supported instance type to satisfy the expansion requirement.