Free Nutanix NCP-CI-AWS Practice Exam with Questions & Answers | Set: 3

In an isolated Flow Virtual Networking (FVN) environment, User VMs are often placed on subnets without direct external routing. To enable administrative access for a " jump box " VM, aFloating IPmust be utilized. The administrator should request a Floating IP and associate it with theoverlay-external-subnet-nat. This Floating IP acts as a public-facing address that the NAT gateway maps to the private IP of the jump box VM. This allows external users to connect to the jump box from outside the VPC while keeping the rest of the workload VMs entirely isolated from external traffic. It is critical to associate the IP with the NAT-enabled external subnet to ensure that the necessary address translation occurs for the inbound connection.

For a new NC2 on AWS deployment where workload VMs have low storage and memory requirements but high CPU frequency ( > 3.0 GHz) requirements, and the goal is to minimize the number of CPU cores to reduce application licensing costs, thei3.metalinstance type is the most suitable.

i3.metal:

High CPU Frequency: i3.metal instances offer high-frequency Intel Xeon processors (up to 3.1 GHz) which meet the high CPU frequency requirement.

Low Storage and Memory: These instances come with a balanced amount of storage and memory, suitable for workloads with low requirements in these areas.

Minimized CPU Cores: i3.metal instances have fewer CPU cores compared to other high-frequency instances like i4i.metal, making them ideal for minimizing application licensing costs.

Other Instance Types:

z1d.metal: While also offering high CPU frequency, these instances typically come with a higher core count and more memory, which may not be optimal for minimizing licensing costs.

i4i.metal: Designed for I/O intensive applications with higher core counts.

m5d.metal: Balanced instance type but with more cores and not as high CPU frequency as required.

AWS EC2 Instance Types Documentation

Nutanix Cloud Clusters on AWS Administration Guide

Nutanix Best Practices for Instance Selection

To support Nutanix ' s native Local Key Manager (LKM) for data encryption in a cost-effective manner, a minimum of three nodes is required. This ensures that there is enough redundancy and reliability for the encryption services to function properly, complying with best practices for distributed key management.

Nutanix Support and Insights

Nutanix Cloud Clusters on AWS Administration

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

Flow Virtual Networking (FVN)provides an advanced software-defined networking layer that supports three specific types of connectivity models for NC2 clusters. First,NAT (Network Address Translation)networks allow User VMs to access external resources (like the internet) using the gateway ' s IP, providing a layer of security. Second,No-NATnetworks allow for transparent routing between the Nutanix overlay and on-premises or other VPC environments, preserving the original VM IP addresses. Third,L2 Stretchednetworks (Subnet Extensions) use VXLAN tunnels to extend a single broadcast domain from an on-premises data center to the cloud cluster. These three types allow administrators to tailor their network architecture based on the specific security and connectivity requirements of each workload hosted in the cloud.

Synchronous replication requires extremely low latency (typically sub-5ms) and high throughput between the primary and secondary storage controllers. While Flow Virtual Networking (FVN) supports various multi-VPC architectures, the most robust and supported configuration for synchronous replication within a single AWS region is to ensure that both clusters reside within the same AWS VPC. This placement minimizes network hops and avoids the additional latency that might be introduced by VPC Peering or Transit Gateway traversal between separate VPCs. By sharing the same VPC, the clusters communicate over the same high-speed internal AWS network fabric, providing the deterministic performance and zero-RPO data protection required for synchronous data writes and Metro Availability configurations.

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 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.

When establishing a landing zone in a brand new AWS region for NC2 with Flow Virtual Networking (FVN), the network team must provision specific subnets to support the management plane and the transit architecture. The first essential component is theFVN Overlay External Subnet, which resides within the Transit VPC and acts as the entry/exit point for traffic moving between the overlay network and external environments like the internet or on-premises data centers. The second requirement is a dedicatedPrism Central subnet, which is necessary to host the Prism Central instance that will manage the NC2 clusters within that region. These subnets provide the structural foundation for the software-defined networking overlay, ensuring that management traffic is properly segregated from user workload traffic and that the transit gateway logic has a designated physical network path.

The 192.168.5.0/24 range is often reserved for internal cluster communication within Nutanix deployments.

Using this CIDR range for other purposes could lead to network conflicts and connectivity issues, as it might interfere with the internal operations and communication channels of the Nutanix cluster.

Ensuring that the CIDR range is not overlapping with any reserved ranges is crucial for maintaining proper network connectivity and cluster functionality.

Refer to the Nutanix documentation on network configuration and best practices for NC2 deployments to confirm reserved IP ranges and their appropriate use.