* Azure Private Endpoint:A Private Endpoint provides secure connectivity to Azure resources by enabling private access through the Azure backbone network. This ensures that the traffic does not traverse the internet, providing enhanced security and performance.
* Delegated Subnet:By creating an Azure Private Endpoint for VMs in a delegated subnet, the administrator ensures that the VMs can access Azure resources directly and securely without using the public internet.
References:
* Azure Private Endpoint Documentation
* Nutanix NC2 Networking Configuration Guide

* Jump Host VM in External VNet with VNet Peering:
* Deploy Jump Host VM:Deploy a VM in an external VNet that is not within the same network as Prism Central.
* VNet Peering:Establish VNet peering between the external VNet and the Prism Central VNet.
This allows the Jump Host to communicate with Prism Central securely.
* Jump Host VM in Prism Central VNet Inside a Delegated Subnet:
* Deploy Jump Host VM:Deploy the Jump Host VM directly in the Prism Central VNet within a delegated subnet. This places the Jump Host in the same network environment as Prism Central, allowing direct access.
References:
* Azure VNet Peering Documentation
* Nutanix NC2 Networking and Access Configuration Guide

* SMTP Server Configuration:To send alert emails from Prism Central, it is essential to configure an SMTP server in the Prism Central settings. This server handles the email sending process, ensuring that alerts generated by Prism Central are properly delivered to the specified email addresses.
* Email Notification Setup:The SMTP server settings include the server address, port, and authentication details. Once these settings are correctly configured, Prism Central can use the SMTP server to send out alert emails reliably.
References:
* Nutanix Prism Central Administration Guide
* SMTP Configuration for Email Alerts in Prism Central

* DNS Server Options:
* Cloudflare: A public DNS service that operates over the internet.
* Azure: Azure DNS operates within the Azure cloud and does not require VPN or ExpressRoute for connectivity within Azure.
* On-premises: Requires a secure connection, such as VPN or ExpressRoute, to be accessible from Azure, as it resides outside the Azure cloud.
* Google: Another public DNS service accessible over the internet.
* Connectivity Requirements:
* On-premises DNS: To integrate on-premises DNS with Azure, secure connectivity (VPN or ExpressRoute) is necessary to ensure seamless and secure communication between the on-premises infrastructure and Azure resources.
* Conclusion: An on-premises DNS server would require VPN or ExpressRoute connectivity to be accessible and integrated with the Azure environment.
References:
* Azure DNS Overview
* VPN Gateway Configuration
* ExpressRoute Overview

* 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