Nutanix NCS-Core Practice Test - Questions Answers, Page 30

In a situation where traffic is not being balanced across the physical NICs and the Top-of-Rack (ToR) switches have been configured with LACP (Link Aggregation Control Protocol), the appropriate AHV network configuration to resolve this issue within Prism Element is 'Active-Active.' This setting enables both NICs to actively handle traffic, which, combined with LACP, allows for load balancing and redundancy, effectively utilizing all available network paths. This setup ensures that traffic is spread evenly across the physical NICs, maximizing network throughput and resilience.

Nutanix Prism User Guide

Nutanix AHV Administration Guide

In a scenario where a new AHV cluster is installed and the traffic is not being balanced across the physical NICs despite the ToR switches being configured with LACP, the appropriate network option to set within Prism Element is Active-Active. This configuration allows for a traffic-hashing algorithm, such as balance-TCP, to split traffic between multiple links in an active-active fashion.Since the uplinks appear as a single L2 link, the algorithm can balance the traffic among bond members without any regard for switch MAC address tables1.

Nutanix Community: AHV Networking | Enable, Disable and Verify LACP1

Nutanix Support & Insights: Layer 2 Network Management2

Nutanix Support & Insights: Enabling LAG and LACP on the ToR Switch (AHV Only)

For a customer using an ESXi cluster with two 10GbE NICs on each node and a vSphere Distributed Switch, the recommended load balancing configuration, following Nutanix Best Practices for redundancy and efficiency, is 'Route based on IP hash.' This setting allows for optimal utilization of network bandwidth and redundancy by distributing the traffic based on the IP address pairings, ensuring a balanced load across the physical NICs.

Reference: Nutanix Bible, Nutanix University NCS-Core 6.8 learning materials

The subnet 192.168.254.0/24 is commonly reserved for CVM (Controller Virtual Machine) internal switch traffic within Nutanix environments. This subnet is used internally by the CVMs for management and storage operations that are integral to the Nutanix infrastructure. Using a separate, reserved subnet helps to isolate management traffic from general network traffic, enhancing security and performance.

Reference:

Nutanix University - NCS-Core 6.8 Learning Path

The Nutanix Bible, Network Configuration chapter (https://www.nutanixbible.com/)

The CVM IP address is a hard requirement for deploying a Nutanix cluster. Each CVM must have a unique IP address assigned to it as this IP address is critical for cluster operations, including data replication, management activities, and communication between CVMs and hypervisors. The other options, while important for various functionalities, do not represent a hard requirement for initial deployment.

Reference:

Nutanix University - NCS-Core 6.8 Learning Path

The Nutanix Bible, Cluster Configuration chapter (https://www.nutanixbible.com/)

To deploy the Foundation VM on VMware ESXi or AHV Hypervisors, the two necessary files are:

foundation_VM-version.tar which contains the complete Foundation VM package.

foundation_VM-version.vmdk, which is the virtual disk file for VMware environments.

These files are required to create and boot the Foundation VM in these hypervisor environments, facilitating the deployment and configuration of the Nutanix nodes within the cluster.

Reference: Nutanix Bible, Nutanix University NCS-Core 6.8 learning materials

To deploy the Foundation VM on VMware ESXi or AHV Hypervisors, the two necessary files are:

foundation_VM-version.tar which contains the complete Foundation VM package.

foundation_VM-version.vmdk, which is the virtual disk file for VMware environments.

These files are required to create and boot the Foundation VM in these hypervisor environments, facilitating the deployment and configuration of the Nutanix nodes within the cluster.

Reference: Nutanix Bible, Nutanix University NCS-Core 6.8 learning materials

If a consultant is unable to ping the CVM from the hypervisor using the external interface in a network without VLAN tagging, and both are using the same subnet, the issue might be related to an incorrect default gateway configuration. The default gateway must be correctly set to ensure proper routing of packets between the CVM and the hypervisor. An incorrect gateway can prevent successful communication even if both devices are on the same subnet.

Reference:

Nutanix University - NCS-Core 6.8 Learning Path

The Nutanix Bible, Networking chapter (https://www.nutanixbible.com/)

To meet the customer's requirements for high availability and the ability to manage up to 12,500 VMs, the consultant should use Prism Central Scale-out deployment. This deployment mode allows Prism Central to be scaled out across multiple instances, significantly enhancing both performance and resilience, ensuring that the management and operations of a large number of VMs can be handled efficiently and without a single point of failure.

Reference: Nutanix Bible, Nutanix University NCS-Core 6.8 learning materials

Based on the exhibit which shows an NX-3160 block with marked slots, the correct slot for installing a new node in the existing NX-3160 block is slot 2. This configuration is typically aligned with the chassis' design for orderly expansion and maintaining balanced power and cooling distribution among the nodes.

Reference: Nutanix Bible, Nutanix University NCS-Core 6.8 learning materials