NCP-CI-AWS Exam Dumps - Nutanix Certified Professional (NCP) Questions and Answers

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.

To deploy NC2 in AWS using an existing VPC, the following AWS resources should be configured beforehand:

NAT Gateway: This allows instances in the private subnet to connect to the internet or other AWS services, while preventing the internet from initiating connections with those instances.

Public and Private Subnets: These are necessary to segregate the network traffic. Public subnets provide a direct route to the internet gateway, while private subnets are used for internal resources that do not need direct access to the internet.

Nutanix Cloud Clusters on AWS Deployment Guide

Nutanix Support and Insights

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.

To manually hibernate an NC2 on AWS cluster, the administrator can use the following methods:

Select the cluster under NC2 console and Select Hibernate/Resume on the cluster sur page: Navigate to the specific cluster in the NC2 console and use the provided Hibernate/Resume option.

Log into NC2 console, find the cluster name and select Hibernate/Resume from the ellipses: Access the NC2 console, locate the cluster name, and select the Hibernate/Resume option from the ellipses (three dots) menu.

These options allow for the manual control of the cluster ' s hibernation state directly within the NC2 console interface.

Nutanix Cloud Clusters on AWS Administration

Nutanix Support and Insights

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.

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.

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.

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

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.

To backup Prism Central configuration data to an Amazon S3 bucket, thepcdr-clicommand with theprotectparameter is used. This parameter is specifically designed for creating protection policies and backing up Prism Central data.

Nutanix Prism Central Documentation

Nutanix pcdr-cli Command Reference