Free Nutanix NCP-CI-Azure Exam Dumps August 2026

To extend an on-premises subnet to an NC2 cluster on Azure, the administrator should configure:

Subnet Type: Both on-premises VLAN subnets and VPC subnets. This ensures that the subnet can span both the on-premises environment and the Azure environment.

Traffic Type: Support for IPv4 unicast traffic, IPv6 unicast traffic, and ARP is necessary to ensure proper communication and address resolution across the extended subnet.

On-premises Hypervisor: ESXi and AHV are supported hypervisors for this type of configuration, allowing for a seamless extension of the subnet between these environments.

Reference

Nutanix Hybrid Cloud Networking

To allow access from the native Azure VMs to the workloads running in the Nutanix User VPC, the administrator needs to:

Adjust the Inbound Network Security Group (NSG) on the Flow Gateway VM's Internal NIC.

Specifically, allow traffic from the subnet range of the native Azure VMs (10.20.80.0/20) in the Inbound rules of the NSG associated with the Internal NIC of the Flow Gateway VM.

This configuration change permits the desired network traffic, ensuring that the native Azure VMs can communicate with the workloads in the Nutanix User VPC. Reference

Azure Network Security Groups Overview

Nutanix Networking and Security Best Practices

Azure Resource Providers: To prepare an Azure subscription for NC2, specific resource providers must be registered to enable necessary services and resources.

Required Providers:

Microsoft.Network: This provider is essential for networking functionalities, including virtual networks, subnets, and other network resources necessary for NC2 deployment.

Microsoft.Nutanix: This provider is specifically required for integrating and managing Nutanix resources within the Azure environment.

Other Providers:

Microsoft.HybridNetwork and Microsoft.HybridCompute: These are not specifically required for NC2 but might be relevant for other hybrid or extended network configurations.

Conclusion: Registering both 'Microsoft.Network' and 'Microsoft.Nutanix' ensures that all necessary network and Nutanix-specific resources are available for NC2 deployment.

Azure Resource Providers Documentation

Nutanix on Azure Setup Guide

To collect the appropriate logs (Cluster_agent, Host_agent, and Hostsetup) for diagnosing the deployment issue with Nutanix Support, the administrator should:

Log in to Prism Element to access the Controller VM (CVM) console.

Run the logbay collect command from the CVM console. This command collects the necessary logs and packages them for support.

This method ensures that the correct logs are gathered in a format that Nutanix Support can analyze. Reference

Nutanix Support Documentation on Log Collection

Microsoft Azure Consumption Commitment (MACC): To ensure that the Nutanix licensing costs apply to the MACC, the company needs to make purchases that are recognized by Azure's billing system.

Azure Marketplace Purchases: By purchasing Nutanix licenses through the Azure Marketplace, the costs will be included in the Azure billing and count towards the MACC, thereby leveraging the committed spend.

Azure Marketplace Documentation

Nutanix Licensing Guide

Cloud Hardware Support: For issues related to cloud hardware, such as EC2 instances or VPC configurations, the responsible entity is typically the public cloud vendor.

Nutanix Responsibility: Nutanix manages the software layer and integration aspects of the NC2 service, but the underlying hardware support is managed by the cloud provider (e.g., AWS, Azure).

Support Process:

Public Cloud Vendor: Contact the public cloud vendor for issues directly related to the hardware, as they own and manage the physical infrastructure.

Nutanix: For software and configuration issues specific to the NC2 service, contact Nutanix support.

Conclusion: For cloud hardware-related support, the appropriate contact is the public cloud vendor.

Nutanix Support Guide

Azure Support Documentation

Node Termination Observation: When a node is terminated from the Azure portal, the NC2 cluster will detect that the node is no longer operational.

Marking as Degraded: NC2 will mark the node as degraded, indicating that the node is not functioning as expected. This status allows administrators to take necessary actions to resolve the issue, such as provisioning a new node or addressing the degradation cause.

Nutanix NC2 Cluster Management Guide

Azure Instance Termination Documentation