Free Practice Questions for Nutanix NCP-CI-AWS Exam

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

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.

For a VM deployed in an NC2 cluster on AWS to be accessed by resources within the on-premises datacenter, the security group associated with the User VM (UVM) subnet must allow inbound traffic on the specific ports required by the application.

If the security group rules do not permit inbound traffic on these ports, the communication will fail, even if other network configurations are correct.

The administrator should ensure that the UVM Security Group includes rules to allow inbound traffic for the application ' s required ports, facilitating proper communication between the VM and on-premises resources.

Refer to the AWS documentation on security group configurations and Nutanix NC2 documentation for details on configuring network access and security group rules.

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

Nutanix Cloud Clusters (NC2) on AWS is designed to provide a " cloud-native " resilience experience, meaning it proactively manages the underlying hardware health.

If AWS issues a notification for aSystem Rebootor a hardware-related event on a bare-metal instance, the NC2 console does not simply wait for the reboot to occur. To maintain cluster availability and avoid potential data integrity issues during an uncontrolled hardware event, NC2 triggers anautomated host replacement. The system will provision a new bare-metal instance, integrate it into the cluster, and migrate the data and workloads (using High Availability if necessary) away from the degraded or scheduled-to-reboot host. This automation ensures that the Nutanix cluster remains healthy and functional despite the ephemeral nature of cloud infrastructure hardware.

When a catastrophic failure occurs, such as an entire AWS Availability Zone (AZ) becoming unavailable, the Cluster Protect feature provides a cloud-native orchestrated recovery path. The critical first step for an administrator to trigger the recovery workflow is to manually set the cluster to the " Failed " state within the NC2 console. Marking the cluster as failed signals the NC2 portal that the original infrastructure is non-functional and initiates the logic required to redeploy the cluster in a healthy, alternative AZ. Without this manual confirmation, the portal may continue attempting to reach the original nodes. Once the " Failed " state is confirmed, the portal provides the subsequent options to provision new bare-metal hardware and re-hydrate data from the Amazon S3 snapshots.

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

When a " boot timeout " alert occurs during a cluster expansion, it often indicates that the NC2 console requested a new instance from AWS, but the instance failed to reach a " healthy " state within the allotted time. While networking can be a factor, common " hard " stops at the AWS API level includeService QuotasandInstance Limits. AWS accounts have default limits on the number of bare-metal instances (like i3.metal or i4i.metal) that can be active in a single region. If the expansion request exceeds thevCPU quotaor the specificinstance type limit, AWS will deny the request or fail to provision the hardware. Administrators must verify these quotas in the AWS Service Quotas console and request an increase to support the additional nodes required for the Nutanix cluster.

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.