Free NCP-CI-AWS Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

For issues related to cloud hardware support such as EC2 instances, VPC, etc., the public cloud

vendor (AWS in this case) should be contacted. AWS provides support and documentation for their

infrastructure and services, ensuring that users can get assistance for any hardware or cloud-specific

queries.

Reference:

Nutanix Support & Insights

In Nutanix Cloud Integration with AWS, specifically version 6.7, the role that allows full access to

clusters created within an organization is the Organization Administrator.

The Organization Administrator role has the highest level of privileges within an organization,

enabling the user to manage all aspects of the clusters, including creation, modification, and

deletion.

This role is designed to oversee and control the entire organization's resources, ensuring

comprehensive management capabilities over all clusters and associated resources.

Reference:

Refer to the Nutanix documentation on roles and permissions for NC2 on AWS for further details.

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.

Reference:

Nutanix RBAC Documentation

Nutanix Support Access Guide

To create a CloudFormation stack, the AWSCloudFormationFullAccess role is required.

This role grants the necessary permissions to create, update, and delete CloudFormation stacks,

which are essential for deploying and managing AWS infrastructure using CloudFormation templates.

CloudFormation stacks are often used to automate the deployment of complex infrastructures,

including those required for NC2 on AWS.

Proper permissions ensure that the deployment process is seamless and adheres to the security and

operational policies of the organization.

Reference:

Refer to the AWS IAM documentation for details on the AWSCloudFormationFullAccess role and

Nutanix documentation on prerequisites for deploying NC2 on AWS.

To control network traffic at the individual User VM (UVM) subnet level, creating a custom security

group is the appropriate action. This approach allows for fine-grained control over inbound and

outbound traffic rules that can be applied to specific subnets or individual instances within those

subnets.

Custom Security Group:

Custom security groups enable administrators to define specific traffic rules tailored to the needs of

individual subnets or VMs. This includes specifying allowed IP ranges, ports, and protocols.

By applying these custom security groups to the UVMs, the organization can control access and

enhance security according to their policies and requirements.

Steps to Create a Custom Security Group:

Navigate to the AWS Management Console and go to the VPC service.

Select "Security Groups" under the "Security" section.

Click on "Create Security Group" and define the name, description, and VPC.

Add inbound and outbound rules according to the desired traffic control policies.

Attach the custom security group to the UVMs or subnets in question.

Reference:

Nutanix Cloud Clusters on AWS Administration Guide

AWS Security Group Documentation

Nutanix Best Practices for Security Groups

When performing a migration from an NC2 environment to a Nutanix on-premises environment, the

task should be performed using the NC2 Prism Central. This is because NC2 Prism Central provides a

centralized management interface that allows administrators to manage and migrate workloads

between cloud and on-premises environments seamlessly.

Reference:

Nutanix Cloud Clusters (NC2) Documentation

Nutanix Community Guide

The requirement for two private subnets in the NC2 cluster configuration workflow serves the same

purposes:

One subnet is designated for user VMs, ensuring user workloads are separated from management

operations.

The other subnet is designated for cluster management, maintaining the integrity and security of

management processes and internal communications.

Reference:

Nutanix Clusters on AWS Deployment Guide

Nutanix Cloud Clusters on AWS Administration

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.

Reference:

Nutanix Lifecycle Manager (LCM) Documentation

Nutanix AHV Upgrade Guide

Nutanix BIOS Upgrade Documentation

The Nutanix Create Cluster wizard may not support selecting subnets that have both IPv4 and IPv6

CIDR blocks due to compatibility or configuration constraints.

When a subnet with both CIDR blocks is present, it can cause issues in the selection process during

cluster creation, as the system might not be able to properly handle or recognize the dual-stack

configuration.

Ensuring that the management subnet has only an IPv4 CIDR block, without an IPv6 CIDR block,

could resolve this issue and allow for successful selection in the cluster creation wizard.

Reference:

Refer to the Nutanix and AWS documentation on subnet configuration and requirements for NC2

cluster deployments, specifically addressing IPv4 and IPv6 compatibility and constraints.

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.

Reference:

Nutanix Cloud Clusters on AWS Deployment Guide

Nutanix Support & Insights

To establish full connectivity between the company’s on-premises datacenter and the AWS cloud, the

following AWS offerings will satisfy this requirement:

AWS VPN: This service allows you to create a secure connection between your on-premises network

or other remote network and your AWS VPC using an IPsec VPN tunnel. It is suitable for low to

moderate bandwidth requirements and provides secure, encrypted connections.

Direct Connect: AWS Direct Connect is a dedicated network connection from your premises to AWS.

It provides a private, high-bandwidth, low-latency connection which is ideal for high-throughput

applications and workloads that need consistent network performance.

Reference:

AWS VPN Documentation

AWS Direct Connect Documentation

Enable IGMP snooping on the AHV hosts:

IGMP (Internet Group Management Protocol) snooping is a feature that listens to IGMP traffic

between hosts and routers. By enabling IGMP snooping on the AHV (Acropolis Hypervisor) hosts, the

switch can intelligently forward multicast traffic only to the ports that have requested it.

This reduces unnecessary multicast traffic on the network and prevents congestion by ensuring that

multicast packets are only delivered to the appropriate endpoints.

Reference:

Refer to the Nutanix documentation on network configuration and best practices for managing

multicast traffic.

For VDI workloads that require GPU acceleration, the g4dn.metal nodes are the appropriate choice.

These instances are equipped with NVIDIA T4 GPUs, which are well-suited for graphics-intensive

applications such as VDI workloads that need GPU acceleration. Other node types like AN36P,

m6g.metal, or AN36 do not provide the necessary GPU capabilities.

Reference:

Nutanix Support & Insights - GPU support in AWS

When setting up a landing zone for Nutanix clusters on AWS, having only private subnets for cluster

management and user VMs is not sufficient for full cluster functionality. Nutanix clusters often need

to communicate with the internet for updates, patches, and other cloud services.

VPC Configuration:

The VPC already has two private subnets (one for cluster management and one for user VMs).

Additional Requirements:

To access public services like S3 or for the cluster nodes to reach Nutanix services for updates, a

public subnet is essential.

Why Public Subnet for Internet Access?:

A public subnet allows resources within it to communicate directly with the internet, which is

necessary for accessing Nutanix's update servers, applying patches, and other maintenance tasks.

This subnet typically includes an internet gateway, enabling instances in the public subnet to receive

and send traffic directly to the internet.

Reference:

Nutanix Cloud Clusters on AWS Administration Guide

AWS Networking Best Practices

Nutanix Networking and Subnet Configuration Guidelines

After the NC2 free trial expires, to continue using all features of NC2 on existing clusters, the

administrator needs to switch to a paid subscription plan.

A paid subscription ensures uninterrupted access to the full range of features and support for NC2

clusters.

Without switching to a paid plan, the features might be limited, and support may not be available,

impacting the cluster's operations and management.

Reference:

Refer to the Nutanix billing and subscription documentation for details on switching from a trial to a

paid plan and the benefits associated with paid subscriptions.