Pass the Nutanix Certified Professional (NCP) NCP-CI-AWS Questions and answers with ValidTests

For AOS software support related to NC2, the appropriate entity to contact is Nutanix. Nutanix provides comprehensive support for their software, including the Acropolis Operating System (AOS) used in NC2 deployments.

Support Scope:

Nutanix offers support for the deployment, configuration, and management of NC2 clusters, including any issues related to AOS software.

This includes troubleshooting, updates, and technical assistance.

Why Not Other Options:

Internal IT Operations team: Typically handles internal issues but does not have the specialized knowledge or resources for AOS software support.

Partner: May provide support but would ultimately escalate issues to Nutanix for software-specific concerns.

Public Cloud Vendor: Manages infrastructure-related issues but does not provide support for Nutanix AOS software.

Nutanix Support Documentation

Nutanix Cloud Clusters on AWS Administration Guide

Nutanix Best Practices for AOS Support

To correctly route traffic in a hybrid environment using Flow Virtual Networking, administrators must distinguish between internal private traffic and external internet traffic. Internal traffic usingRFC 1918address ranges (10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16) should be routed to theoverlay-external-subnet-no-nat. This ensures that traffic directed to the on-premises data center retains its original IP address for auditing and security purposes. Conversely, all other traffic (0.0.0.0/0), typically destined for the internet, should be routed to theoverlay-external-subnet-nat. This configuration allows the NAT Gateway to handle internet-bound requests while maintaining a transparent, non-NAT path for corporate internal communication.

NC2 on AWS allows for the dynamic addition ofAmazon EBS volumesto bare-metal nodes to expand the cluster ' s storage capacity beyond the local NVMe drives. According to Nutanix architectural guidelines, once these EBS volumes are attached and integrated into the storage pool, the capacitycan only be increased. Reducing the storage capacity by removing or shrinking attached EBS volumes is not a supported operation because it would risk data loss and disrupt the Distributed Storage Fabric (DSF) which expects consistent disk availability. Therefore, administrators should carefully size their initial EBS requirements, knowing that they can scale up to meet demand but cannot scale back the capacity of individual existing volumes without a complex data migration or cluster redeployment.

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.

Hibernation is a key cost-optimization feature of NC2 that allows bare-metal nodes to be powered down while preserving the cluster ' s data state in cloud storage. For this functionality to be supported, the data must reside in a specific storage architecture. Only Volumes-only containers support the hibernate and resume feature in NC2 on AWS. These containers are specifically engineered to allow the Nutanix Distributed Storage Fabric (DSF) to safely offload data and metadata to Amazon S3 during the hibernation process and successfully re-integrate it into new bare-metal instances upon resumption. Standard storage containers or AES-optimized containers do not currently support the data mobility and offloading workflows required to preserve cluster state when the physical compute nodes are completely de-provisioned from the AWS environment.

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

During the NC2 cluster creation process, the administrator is presented with options for the licensing portfolio they wish to utilize. Nutanix has transitioned to theNCI (Nutanix Cloud Infrastructure)portfolio, but the legacyAOSportfolio is still available for certain customers. If the " AOS Licenses " option appears greyed out or unselectable, it is typically becausethe administrator did not select AOS in the licensing section of the NC2 Creation Wizard. The wizard requires an explicit choice early in the workflow to determine which features and software tiers (Pro, Ultimate, etc.) will be available for selection later. If the portfolio is not correctly identified at the start, the specific license keys or reservations associated with the legacy AOS model will not be recognized by the deployment engine, defaulting instead to the newer NCI-based consumption model.

Before accessing the Nutanix Cloud Clusters (NC2) console, the first step is to create a My Nutanix account.

This account serves as the primary gateway for managing and accessing Nutanix services, including NC2.

Once the account is created, users can log in to the Nutanix portal, where they can manage their subscriptions, start trials, and access various Nutanix services, including the NC2 console.

Refer to the Nutanix documentation on getting started with NC2 and the My Nutanix account creation process.

Ensure the specialist is assigned the RBAC role with proper permissions (Answer A):

Role-Based Access Control (RBAC) ensures that the specialist has the necessary permissions to troubleshoot and manage the NC2 environment. This avoids unnecessary privilege escalations and maintains security.

Confirm the Support Authorization on the organization is set to Full Access (Answer C):

Setting the Support Authorization to Full Access allows the Nutanix support specialist to have the required access to investigate and resolve issues in the environment. This is essential for effective troubleshooting.

Nutanix RBAC Documentation

Nutanix Support Access Guide

In the NC2 console, an organization is used to segregate clusters based on specific requirements. This segregation allows administrators to manage clusters more effectively by grouping them according to business units, projects, or other criteria. This organizational structure helps in maintaining clear boundaries and applying specific policies or permissions to different clusters within the same NC2 environment.

Nutanix Cloud Clusters on AWS Administration

Nutanix Certified Professional - Cloud Integration - AWS