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

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.

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

For a VM to be accessible over the internet through a load balancer, the VM itself must have a public IP address.

In this case, the health check for the VM target is failing and the DNS returns a " NOT Found " message because web-1 does not have a public IP assigned.

Without a public IP, the load balancer cannot route traffic to web-1 from the internet.

Assigning a public IP to web-1 ensures that the VM can be accessed via the load balancer, resolving the connectivity issue.

Refer to the AWS documentation on network load balancers and public IP assignments, and Nutanix documentation on VM network configurations.

While NC2 on AWS runs on bare-metal EC2 instances, hardware-level events or maintenance notifications are initially generated by the AWS infrastructure. To provide a streamlined management experience, Nutanix integrates these AWS-specific events directly into theNC2 console ' s notification center. This allows administrators to monitor for issues such as scheduled reboots, hardware degradations, or instance status checks without constantly switching between the Nutanix and AWS management portals. While Prism Central and Prism Element provide software-level alerts for the Nutanix OS, the NC2 portal is the primary location for alerts related to the underlying cloud lifecycle and infrastructure events that may impact cluster health.

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.

To resolve the IP conflict issue when an EC2 instance is powered on in a subnet also used by Nutanix NC2, the administrator should block or exclude the IP address used by the NC2 VM from being assigned to EC2 instances. This can be done by configuring the IP address management (IPAM) settings to ensure that the specific IP addresses allocated to the NC2 VMs are not used by EC2 instances, preventing IP conflicts and ensuring smooth operation of both environments.

Nutanix Cloud Clusters on AWS Deployment Guide

Nutanix Support and Insights

AWS supports EC2 bare-metal instances in regions with at least 3 partitions. Partitions in AWS provide high availability and fault tolerance by distributing instances across different hardware to minimize the impact of hardware failures.

AWS EC2 Bare Metal Instances Documentation

AWS Regions and Availability Zones

The Nutanix NC2 portal uses a hierarchical structure consisting of Customers, Organizations, andWorkspacesto manage resources. A common point of confusion for administrators is that clusters are localized to specific Workspaces. If an administrator logs into the portal and finds their cluster " missing, " the most likely cause is that they are currently viewing a differentworkspacethan the one where the cluster was provisioned. The NC2 console requires users to select the correct context to view their resources. Checking the workspace selector in the portal interface usually resolves this visibility issue, as the account and overall portal permissions are already verified by the successful login.

The clusters that are to be protected must be registered with the same instance of Prism Central (Answer C):

For Cluster Protect to function correctly, all clusters intended for protection must be registered under the same Prism Central instance. This ensures consistent management and coordination of protection policies and operations across clusters.

The Cluster Protect feature requires AOS version 6.7 or higher (Answer D):

Cluster Protect is a feature that is available starting from AOS version 6.7. To utilize this feature, ensure that the Nutanix clusters are running this version or a newer one.

Nutanix Cluster Protection Documentation

Nutanix AOS Release Notes

The exhibit indicates a replication operation with specific details about the protection domain, remote site, and snapshot. Key points to note are:

Bytes Completed: 0 bytes completed.

Complete Percent: 0.0%

Paused: false

Aborted: false

Given these details:

No ongoing replication: The operation has started, but there is no progress in terms of bytes completed or percentage completed. Since the status shows 0 bytes and 0 percent completed, it indicates that no data has been replicated yet.

Nutanix Protection Domain and Replication Documentation

Nutanix Best Practices for Monitoring Replication