Free Practice Questions for Nutanix NCP-CI-Azure Exam

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

When selecting the NC2 subscription plan from the Nutanix billing portal, the available options are:

Pay-as-you-Go (PayG):Allows you to pay for the services as you use them, providing flexibility and avoiding upfront costs.

Bring your own License (BYOL):Enables you to use your existing Nutanix licenses within the cloud environment, offering cost savings if you already have licenses.

These options provide flexibility in how you can manage and pay for your Nutanix cloud clusters.References

Nutanix Cloud Clusters Pricing and Plans

Log Modules in Prism Central:When configuring a syslog server, different log modules can be selected to send logs to an external syslog server for centralized logging and analysis.

Acropolis Logs:The Acropolis module captures logs related to the Acropolis Hypervisor (AHV), including virtual machine operations, storage operations, and other critical functions within the Nutanix environment.

References:

Nutanix Prism Central Administration Guide

Nutanix Acropolis Documentation

my.nutanix.com Portal:This portal provides access to various Nutanix services and features, including the NC2 deployment interface.

NC2 Tile:The NC2 tile within the portal is specifically designed for deploying and managing Nutanix Cloud Clusters. It provides the necessary tools and settings to initiate and configure NC2 clusters on Azure or other cloud environments.

References:

Nutanix NC2 Deployment Guide

my.nutanix.com Portal 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

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

References:

Azure Resource Providers Documentation

Nutanix on Azure Setup Guide

Default Route for Internet Traffic:By setting the default route of 0.0.0.0/0 for the Nutanix User VPC pointing to the external-NAT network, all internet-bound traffic from the desktops will be routed through the Azure NAT Gateway, conserving bandwidth on the ExpressRoute connection.

On-Premises Route:Setting a specific route to the on-premises subnet for the Nutanix User VPC pointing to the external-No-NAT network ensures that traffic destined for on-premises resources bypasses the NAT Gateway and utilizes the ExpressRoute connection, optimizing the use of network paths.

References:

Azure NAT Gateway 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

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

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