Nutanix Nutanix Certified Professional - Cloud Integration - Azure (NCP-CI-Azure v6.7) NCP-CI-Azure Exam Dumps: Updated Questions & Answers (October 2025)

In this scenario, the issue arises from overlapping IP address ranges between the Transit VPC and the User VPC. Here’s a detailed breakdown:

Understanding ERPs (Elastic Routing Prefixes):

The ERP for the Transit VPC is 10.1.1.0/25, which covers IP addresses from 10.1.1.0 to 10.1.1.127.

The ERP for the User VPC is 10.1.1.0/24, which covers IP addresses from 10.1.1.0 to 10.1.1.255.

IP Address Overlap:

Since 10.1.1.0/25 is a subset of 10.1.1.0/24, there is a significant overlap in the IP address ranges of these two ERPs.

This overlap can cause routing issues because the same IP address range is being used in both VPCs, leading to ambiguity in routing and communication.

Communication Issue:

When a VM in the User VPC tries to communicate with other resources, the network cannot accurately determine the correct route due to the overlapping IP address ranges.

This overlap prevents proper routing and results in the VM being unable to communicate with other resources as intended.

Resolution:

To resolve this issue, the ERPs must be in different CIDR ranges. This means the IP address ranges for the Transit VPC and the User VPC should not overlap.

For example, if the Transit VPC uses 10.1.1.0/25, the User VPC could use a different range such as 10.1.2.0/24 or any other range that does not overlap with 10.1.1.0/25.

By ensuring that the ERPs are in different CIDR ranges, the network can properly route traffic between the VPCs without any conflicts or ambiguities, thereby enabling the VM in the User VPC to communicate with other resources effectively.

To connect the company's on-premises datacenter to the Azure cloud environment while avoiding traffic over the public internet, the administrator should use Azure ExpressRoute. ExpressRoute provides a private connection to Azure, offering more reliability, faster speeds, and lower latencies compared to typical internet connections. This service ensures that data traffic does not traverse the public internet, enhancing security and performance.References

Azure ExpressRoute Overview

Flow Virtual Networking: Nutanix Flow Virtual Networking allows for the creation of overlay networks to segment and manage network traffic.

Network Types:

Underlay: Refers to the physical network infrastructure.

Overlay: Logical network built on top of the physical infrastructure, providing flexibility for creating isolated subnets and accommodating different workloads.

VPC: Virtual Private Cloud, a network within a public cloud provider.

VNET: Azure-specific virtual network.

Requirement: Creating a subnet for new workloads within Flow Virtual Networking suggests using an overlay network for logical separation and management.

Conclusion: An overlay network within Flow Virtual Networking will satisfy the task of accommodating a new type of workload in the NC2 Azure instance.

References:

Nutanix Flow Networking Guide

Azure Virtual Network Documentation

NC2 Console:The NC2 console is specifically designed for deploying and managing Nutanix clusters on Azure. It provides the necessary tools and interface to configure, monitor, and manage the NC2 clusters effectively.

Cluster Deployment:Using the NC2 console ensures that all configurations and integrations with Azure are correctly handled, providing a seamless deployment experience.

References:

Nutanix NC2 Deployment Guide

Nutanix Console Documentation

Flow Gateway VMs: Flow Gateway VMs are used to manage and route network traffic within an NC2 on Azure cluster, ensuring sufficient bandwidth for workloads.

Scalability: To ensure enough available bandwidth, multiple Flow Gateway VMs can be deployed.

Maximum Limit: The highest number of Flow Gateway VMs that can be deployed within an NC2 on Azure environment is 6, providing the necessary capacity to handle high traffic volumes and ensure optimal performance.

Conclusion: Deploying up to 6 Flow Gateway VMs ensures adequate bandwidth for NC2 workloads.

References:

Nutanix Clusters Networking Guide

Azure Network Performance Documentation

Cluster State Requirement: To expand a cluster, it must be operational and in a connected state to ensure seamless integration of additional nodes.

Cluster Stopped State: If the cluster is stopped, it cannot perform expansion operations.

Minimum Nodes Requirement: There is no minimum node count prerequisite for expanding the cluster as long as the cluster is connected.

Cluster Connected State: Ensuring the cluster is connected verifies that it is operational and can communicate with additional nodes being added.

Conclusion: The cluster must be in a Cluster Connected state to expand successfully.

References:

Nutanix Clusters Expansion Guide

Azure NC2 Configuration Documentation

In the scenario presented, the NC2 cluster was initially deployed with two Flow Gateways (FGW1 and FGW2) in HA. After adding four bare-metal nodes and additional workloads, two more Flow Gateways (FGW3 and FGW4) were added to handle the increased bandwidth for north/south traffic. Given the configuration, the existing workloads can utilize all available Flow Gateways (FGW1, FGW2, FGW3, and FGW4) for No-NAT (routed) traffic paths. This setup allows for Equal Cost Multipath (ECMP) routing, distributing traffic load across all Flow Gateways.

References

Nutanix Flow Networking

User VM:The initial source of the traffic within the Azure environment.

Delegated Subnet:Traffic from the User VM flows through the delegated subnet, which is configured to handle specific network traffic.

Flow Gateway:The Flow Gateway manages and routes the traffic from the delegated subnet, providing network services and connectivity.

Floating IP Address:The Flow Gateway assigns a floating IP address for the outbound traffic, facilitating NAT operations.

Azure NAT Gateway:The traffic is then routed through the Azure NAT Gateway, which provides outbound internet connectivity for the User VMs, ensuring secure and efficient routing.

References:

Azure Virtual Network NAT Documentation

Nutanix NC2 Configuration Guide

Payment Method Options:When using a Pay As You Go subscription plan and opting to pay directly to Nutanix, wire transfer is a valid and secure payment method.

Direct Payment:Wire transfers allow for the direct transfer of funds from the organization's bank account to Nutanix, ensuring a straightforward and efficient payment process.

References:

Nutanix Billing and Payment Documentation

Pay As You Go Subscription Payment Methods Guide

NATed Path Configuration: When using the NATed Path, it is essential to ensure that traffic can flow out of the Flow gateway VM to external networks.

Default Route: Adding a default route on the Nutanix User VPC ensures that all outbound traffic is directed to the appropriate network gateway.

Configuration Steps:

Navigate to the routing settings of the Nutanix User VPC.

Add a default route with the destination of 0.0.0.0/0, pointing to the External Overlay network.

Security Group Settings:

Ensure that the External Flow Gateway Security Group on the External NIC allows outbound traffic.

Ensure that the Internal Flow Gateway Security Group on the internal NIC allows outbound traffic (if needed for internal network flows).

Conclusion: Properly configuring the default route on the Nutanix User VPC enables outbound traffic flow via the NATed Path through the External Overlay network.

References:

Nutanix Flow Gateway Configuration Guide

Azure VPC Routing Documentation