NCP-CI-Azure Exam Dumps : Nutanix Certified Professional - Cloud Integration - Azure (NCP-CI-Azure v6.7)

NC2 Cluster Node Limit: NC2 on Azure has specific limitations regarding the maximum number of nodes supported in a single cluster.

Maximum Nodes: According to the current NC2 on Azure guidelines, a single cluster can support up to 18 nodes.

Workload Support: This limitation ensures optimal performance and management of resources within the Azure environment.

Comparison of Options:

14 nodes: Less than the maximum supported.

24 nodes and 28 nodes: Exceed the maximum supported, potentially leading to performance and management issues.

Conclusion: For supporting new workloads, the maximum number of nodes in an NC2 on Azure environment is 18.

References:

Nutanix Clusters on Azure Technical Specifications

Azure Virtual Machine Scale Sets Documentation

Floating IP Address Limitation:The cluster already has 25 floating IP addresses in use by other VMs. If the administrator cannot assign a floating IP address to the new VM, it is because the pool of available floating IPs is exhausted.

Requesting Additional Floating IPs:To resolve this issue, the administrator needs to request additional floating IP addresses to be allocated to the NAT subnet. This will ensure that there are enough IP addresses available for all VMs requiring inbound connectivity.

References:

Nutanix Networking Configuration Guide

Azure IP Address Management Documentation

NC2 on Azure Deployment: Deploying Nutanix clusters in Azure involves configuring various components, each needing appropriate network isolation and configuration.

Components and vNets:

Bare-metal instance: Requires its own vNet to ensure proper network isolation and performance.

Prism Central: Needs a dedicated vNet to manage and monitor the Nutanix environment, ensuring it has the required network access and isolation.

Azure Load Balancer: Does not require its own vNet but needs to be associated with the appropriate vNet where services are deployed.

Virtual Network Gateway: Is used for VPN connections but does not necessitate a separate vNet; it operates within an existing vNet.

Network Isolation: Providing separate vNets for Bare-metal instances and Prism Central ensures optimal performance and management capabilities.

Conclusion: Both Bare-metal instances and Prism Central require their own vNets in the NC2 on Azure deployment.

References:

Nutanix Clusters on Azure Deployment Guide

Azure Virtual Network Documentation