NCP-MCI-6.5: Nutanix Certified Professional-Multicloud Infrastructure 6.5

When a VM is connected to a Nutanix managed network, the IP address is assigned when the VM is powered on. A Nutanix managed network is a network that is created and managed by Prism Central using IP address management (IPAM). IPAM allows Prism Central to automatically assign IP addresses to VMs from a pool of available addresses in a subnet.IPAM also tracks the IP address usage and availability across clusters and networks4.

When a VM is connected to a Nutanix managed network, the administrator can choose one of the following assignment types for the IP address:

Assign Static IP: This option allows the administrator to manually specify a static IP address for the VM from the subnet range. The IP address will not change unless the administrator changes it.

Assign with DHCP: This option allows Prism Central to dynamically assign an IP address for the VM from the subnet range using DHCP. The IP address may change depending on the DHCP lease time and availability.

No Private IP: This option allows the administrator to skip assigning an IP address for the VM.This option is useful for scenarios where the administrator wants to use an external IPAM solution or assign an IP address later5.

Regardless of the assignment type, the IP address is assigned when the VM is powered on. This is because Prism Central needs to communicate with the hypervisor (AHV or ESXi) to configure the virtual NIC (vNIC) of the VM with the IP address information.This communication can only happen when the VM is in a powered on state6.

The correct answer is A. Long term storage of data which is written once and read infrequently.

Erasure Coding is a feature that increases the usable capacity on a Nutanix cluster by reducing the amount of data replication. Instead of replicating data, Erasure Coding uses parity information to rebuild data in the event of a disk failure. The capacity savings of Erasure Coding is in addition to deduplication and compression savings1.

Erasure Coding is most beneficial for scenarios where the data is written once and read infrequently, such as long term storage of archival data, backup data, or cold data. This is because Erasure Coding has some trade-offs and limitations that may affect the performance and availability of the cluster. Some of these trade-offs and limitations are2:

Erasure Coding requires more CPU and memory resources than replication, as it involves more complex calculations for encoding and decoding data.

Erasure Coding increases the network bandwidth consumption, as it involves more data transfers between nodes for encoding and decoding data.

Erasure Coding reduces the resiliency of the cluster, as it can tolerate fewer node failures than replication. For example, a cluster with redundancy factor 2 can tolerate one node failure with replication, but only two disk failures with Erasure Coding.

Erasure Coding is not effective for workloads that have many overwrites or random writes, as it involves more overhead for updating the parity information.

Erasure Coding is not supported for some features, such as volume groups, file server VMs, or Metro Availability.

Therefore, if an administrator needs to configure a container on a Nutanix cluster, they should enable Erasure Coding only if the container will store data that is written once and read infrequently. This way, they can maximize the capacity savings of Erasure Coding without compromising the performance and availability of the cluster.

In Nutanix AHV, when creating a virtual switch and trying to add network interfaces (NICs) to it, the NICs must be connected to the network before they can be selected and assigned to the switch. If the interfaces are showing as disconnected, the system will not allow them to be added to a virtual switch because it cannot verify their operational status or the presence of a live network connection.

It is a standard requirement for the interfaces to have physical connectivity (i.e., network cables plugged in and connected to a live switch port) so that the AHV host can detect the link status as up. Once the interfaces are connected and recognized by the host, they can then be added to a virtual switch in the Nutanix AHV.

It's important to note that while the command-line interface (CLI) is indeed a powerful tool for managing network configurations on AHV hosts, and some configurations do indeed require CLI, the inability to select disconnected interfaces is not specifically a limitation that requires the use of CLI to overcome. The focus should be on ensuring that the physical connectivity is established for the interfaces in question.

This behavior is consistent with networking best practices and Nutanix's network configuration guidelines, as detailed in the Nutanix AHV Networking Guide. This guide explains the requirements and procedures for configuring virtual switches and managing NICs in a Nutanix AHV environment.

https://next.nutanix.com/how-it-works-22/scheduled-power-outage-relocating-cluster-hardware-ifyou-need-to-shut-down-all-the-nodes-in-your-ahv-cluster-here-s-how-37326

The best way for the administrator to limit the amount of storage space that data stored in a single container can consume is to set an advertised capacity for the container. This will ensure that the data stored in the container doesn't exceed the set limit, and it will also help prevent any potential performance issues due to resource contention. Additionally, the administrator should consider thick provisioning the container, which will pre-allocate the amount of storage space that can be used by the container. This will help ensure that the data stored in the container doesn't exceed the advertised capacity.