NCP-MCI-6.5 Practice Exam Questions with Answers Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI) v6.5 exam Certification

A bully VM is a VM that consumes too many resources and causes other VMs to starve. A bully VM can affect the performance and availability of other VMs on the same host or cluster by hogging CPU, memory, disk, or network resources. A bully VM can be identified by using the VM Profile feature in Prism Central2. The VM Profile feature analyzes the resource utilization of each VM and assigns it a profile based on its efficiency and impact on other VMs. The profiles are as follows3:

• Efficient: The VM is well-provisioned and has optimal resource utilization.
• Over-provisioned: The VM has more resources than it needs and has low resource utilization.
• Constrained: The VM has less resources than it needs and has high resource utilization.
• Inactive: The VM has no resource utilization and is idle or powered off.
• Bully: The VM has high resource utilization and causes contention for other VMs.

To identify a bully VM, the administrator can use Prism Central to view the VM Profile dashboard and filter by profile type. The dashboard shows the number of VMs in each profile type, as well as their resource consumption and efficiency score. The administrator can also drill down into each VM to see its detailed metrics and recommendations for optimization.

The correct answer is B. The existing and the expansion node are on different VLANs.

The output shows that the new node has a br0-up bond with four interfaces: eth0, eth1, eth2, and eth3. The bond is configured with LACP active and LACP fallback set to false. This means that the bond will only work if the upstream switch supports LACP and is configured to form an LACP group with the four interfaces. However, the output also shows that the bond has no IP address assigned to it, which indicates that the bond is not operational. One possible reason for this is that the existing and the expansion node are on different VLANs, and the upstream switch is not configured to allow the VLAN traffic on the LACP group. This would prevent the new node from communicating with the cluster and being discovered by the Expand Cluster function in Prism.

To verify this, the administrator can check the VLAN configuration on the upstream switch and compare it with the existing nodes. Alternatively, the administrator can use the “manage_ovs show_uplinks” command on an existing node and compare the output with the new node. If there is a VLAN mismatch, the administrator can either change the VLAN configuration on the switch or on the new node to match the existing nodes.

According to section 5 of the exam blueprint guide1, one of the topics covered is live migration. Live migration is the process of moving a running VM from one host to another without any downtime or interruption of service. To perform live migration, there are some prerequisites that must be met, such as:

• All AHV hosts have IP addresses in the same subnet
• All VMs are configured for the same VLAN
• The source and destination hosts have enough resources to accommodate the VM
• The VM does not have any PCI devices attached

This will allow the administrator to quickly identify VMs that are overprovisioned or underutilized based on their performance metrics.

https://www.nutanix.com/support-services/training-certification/certifications/certification-details-nutanix-certified-professional-multicloud-infrastructure-6_5

A Nutanix cluster requires a minimum of three nodes to maintain quorum and data availability. Removing a node from a 3-node cluster would violate the redundancy factor and cause data loss. Therefore, it is not possible to remove a host from a 3-node cluster using Prism or CLI. The only way to replace a node in a 3-node cluster is to use the Foundation tool, which will erase the existing cluster configuration and create a new cluster with the new node1.

One of the possible reasons for a cluster to transition out of NearSync is insufficient network bandwidth between the source and target clusters. NearSync requires a minimum network bandwidth of 10 Mbps per VM for replication3. If the network bandwidth is lower than the required amount, the replication of recovery points may take longer than the configured RPO, resulting in an Out of NearSync condition. To address this issue, you can increase the network bandwidth between the clusters or reduce the number of VMs protected by NearSync4.

References: 1: Stargate - Nutanix Bible 2: Nutanix Cluster Architecture Overview - Nutanix Bible 3: NearSync Disaster Recovery (RPO <= 15 minutes) - Nutanix Support & Insights 4: Transitioning in and out of NearSync - Nutanix Support & Insights

"An administrator has been tasked with increasing security on Nutanix cluster by disabling password authentication when accessing the CVM and AHV hosts and instead moving to key-based SSH, What is the easiest way for the administrator to meet these needs? Enable Cluster Lockdown and provide an RSA key."

 Cluster Lockdown mode disables password authentication when accessing the CVM and AHV hosts and instead requires key-based SSH. To enable Cluster Lockdown mode, you need to provide an RSA key.

Therefore, by enabling Cluster Lockdown mode and providing an RSA key, you can increase security on Nutanix cluster by disabling password authentication when accessing the CVM and AHV hosts and instead moving to key-based SSH with minimal effort.

https://next.nutanix.com/how-it-works-22/streamlined-login-and-increase-security-key-based-ssh-login-37397

According to section 4 of the exam blueprint guide1, one of the topics covered is AHV networking components and configuration settings. One of these components is Open vSwitch (OVS), which is a software switch that provides network connectivity between VMs and physical networks. OVS has two types of ports:

• Uplink ports: These are physical ports that connect to external networks or switches.
• Internal ports: These are virtual ports that connect to VMs or other internal networks.

To view the uplink state of all AHV nodes in the cluster, an administrator can use the manage_ovs command with the show_uplinks option. This command displays information such as port name, link state, speed, duplex mode, MTU size, bond mode, and bond status. However, this command only works on a single node. To run the command on all nodes in the cluster, an administrator can use the allssh command, which executes a command on all CVMs in parallel. Therefore, the correct command is:

allssh manage_ovs show_uplinks

Configure VM-Host affinity for the nodes that meet the application’s GPU requirement. This is because VM-Host affinity allows the administrator to specify which nodes a VM can run on or must not run on1. By creating a VM-Host affinity rule that binds the application VM to the three nodes that have the physical GPU, the administrator can ensure that the VM will always run on a node that meets its requirement, regardless of any HA or migration events. This also allows the other nodes in the cluster to host other VMs without any restrictions.

According to the Troubleshooting hosted disk I/O performance problems (1008885), when using VMware hosted products, consider that both the virtual machines and host operating system often share the same disk resources and hardware. If a hard disk fails, the virtual machines that have data on the failed device will experience an HA event, causing them to restart on a node that contains the replica data.

A managed network is a type of network that can be created on an AHV cluster and allows VMs to automatically be assigned an IP address at creation time. A managed network uses the Nutanix IP Address Management (IPAM) service, which provides DHCP and DNS functionality for the VMs on the network. A managed network can be configured with a subnet range, a default gateway, and DNS servers. The IPAM service will allocate IP addresses from the subnet range to the VMs and register their hostnames in the DNS servers. The IPAM service will also release the IP addresses when the VMs are deleted or moved to another network1.

To create a managed network on an AHV cluster, the administrator can use Prism Element or Prism Central. The steps are as follows2:

• In Prism Element, go to the Network Configuration page and click Create Network.
• In Prism Central, go to the Networks page and click Create.
• Enter a name and description for the network.
• Select Managed as the network type.
• Enter the subnet range, default gateway, and DNS servers for the network.
• Optionally, enable VLAN tagging and enter a VLAN ID for the network.
• Click Save.

CloudInit is a package that contains utilities for early initialization of cloud instances. It allows you to customize virtual machines provided by a cloud vendor by modifying the generic OS configuration on boot. You can use CloudInit to set the OS hostname, add custom users, add keys, run custom scripts, and more2. CloudInit is supported by most major Linux and FreeBSD operating systems and works across different cloud platforms3. Sysprep is a tool for Windows operating systems that prepares an installation for cloning, auditing, and customer delivery4.

References: 1: Replacing Nodes in Nutanix Cluster - Nutanix Support & Insights 2: Customize a Linux VM with cloud-init in Azure - Azure Virtual Machines 3: Cloud-Init - The standard for customising cloud instances 4: Sysprep (Generalize) a Windows installation

Categories are key-value pairs that can be used to tag entities such as VMs, images, networks, and projects in Prism Central. Categories can be used to create dynamic groups of entities based on their attributes, and assign roles and permissions to those groups3. In this case, a category such as OS=Linux can be used to group all Linux VMs and grant access rights to the Linux administration team.

According to the web search results, Distributed Storage Fabric (DSF) is the scale-out storage technology that makes HCI and cloud possible45. DSF pools the storage devices that are directly attached to a cluster of servers and presents them to applications across a variety of storage protocols4. DSF also manages and protects data by a fine-grained, distributed metadata system that ensures uniform distribution of data throughout the cluster to eliminate hot spots and speed up rebuilds

The best way to fix this issue is to increase the amount of memory assigned to the VM from the Prism web console. This option allows the administrator to modify the VM configuration without accessing the CVM or shutting down the VM. The Prism web console provides a simple and intuitive interface for managing Nutanix clusters and VMs1. To change the memory allocation for a VM, the administrator can follow these steps2:

• Go to the VM dashboard
• Select the VM from the VMs list
• Choose Update
• Adjust the amount of memory assigned to the VM
• Click Save

According to the Nutanix Support & Insights web search result1, if the owner Controller VM becomes unavailable, the address moves to another Controller VM, ensuring that it is always available. This IP address is also used as a cluster-wide address by clients configured as part of Nutanix Files and other products. Therefore, the host will automatically redirect I/O and VMs will continue running without any interruption.

https://portal.nutanix.com/page/documents/details/?targetId=Web-Console-Guide-Prism-v51:wc-block-services-c.html

NTP service needs to be configured to ensure logs, alerts and information is consistent across clusters that are located in different countries. NTP stands for Network Time Protocol and it is used to synchronize the clocks of all the nodes in a cluster1. This helps to maintain accurate timestamps for logs, alerts and other information that are generated by Nutanix clusters1.

Data locality is the capability of storing VM data on the node where the VM is running and ensuring that the read I/O does not have to traverse the network. Data locality is a unique feature of Nutanix that provides high performance and low latency for VMs by minimizing network traffic and crosstalk. Data locality works by writing one copy of the data local to the VM and the other copy (or copies) on other nodes. When a VM migrates to another node, Nutanix also moves its data to the new node and serves all I/O requests locally. Data locality also adapts to changing workloads and access patterns by dynamically moving data to where it is needed most1.

According to the web search results, one recommended configuration change to improve throughput for a custom backup application that requires a 2TB disk and runs on Windows is to span the 2TB disk across four vDisks. Spanning is a technique that allows you to create a single logical disk from multiple physical disks. Spanning can improve throughput by distributing I/O requests across multiple disks and reducing contention5. To span a disk across four vDisks, the administrator should create four vDisks of equal size (500 GB each) and attach them to the VM. Then, in Windows Disk Management, create a spanned volume from the four vDisks and format it as NTFS6.

According to the Nutanix Support & Insights web search result2, VM NICs on AHV can operate in two modes: Access and Trunked. Access NICs are the default, and allow one VLAN on the NIC. Trunked NICs allow multiple VLANs on a single NIC for VMs that are VLAN aware. If you must use trunked NICs, follow the steps described in the web search result2. Therefore, the most efficient way to have a VM on an AHV cluster with access to multiple VLANs is to update a vNIC on the VM to operate in trunked mode for all desired VLANs.

According to the web search results, the policy that should be used to meet this requirement is an Isolation Environment Policy. An Isolation Environment Policy is a type of security policy that can be created in Prism Central using Flow Network Security, which is a feature that provides microsegmentation and network security for Nutanix environments1. An Isolation Environment Policy allows the administrator to isolate a group of VMs from another group of VMs based on their categories, and block all traffic between them regardless of direction2. This policy can be useful for creating isolated environments for testing, development, or compliance purposes2.

According to the Nutanix Support & Insights website1, you can configure alert emails through Prism Central by enabling or disabling customer email notification for each alert. You can also modify or create custom alert policies for different entities and clusters23.

Zombie VMs and overprovisioned VMs are two types of inefficient VMs that can waste resources and increase costs in a Nutanix environment. Zombie VMs are VMs that are powered on but have no activity or utilization for a long period of time. Overprovisioned VMs are VMs that have more resources allocated than they actually need or use. Both types of VMs can be identified by adding predefined views to a report in Prism Central.

A predefined view is a template that defines what data is displayed and how that data is represented in a report. Prism Central provides several predefined views for different purposes, such as capacity planning, performance analysis, anomaly detection, and efficiency optimization. To add a predefined view to a report, go to Operations > Reports > New Report and select the desired view from the list1.

The Zombie VMs List view shows the list of zombie VMs in the environment based on the CPU usage, memory usage, disk IOPS, and network throughput metrics. The view also shows the amount of resources wasted by these VMs and the potential savings that can be achieved by deleting or resizing them2.

The Overprovisioned VMs List view shows the list of overprovisioned VMs in the environment based on the CPU usage, memory usage, disk IOPS, and network throughput metrics. The view also shows the amount of resources wasted by these VMs and the potential savings that can be achieved by resizing them3.

By adding these two views to a report, an administrator can identify inefficient VMs and take appropriate actions to optimize resource utilization and reduce costs.

References: 1: Reports Management - Prism Central Guide 2: Zombie VMs List - Prism Central Guide 3: Overprovisioned VMs List - Prism Central Guide

Port 389 is the default port for LDAP without SSL encryption. Port 636 is used for LDAP over SSL (LDAPS). Port 3268 and 3269 are used for Global Catalog (GC) and Global Catalog over SSL (GCSSL), respectively2.

According to the Nutanix Support & Insights web search result1, route injection is used to maintain I/O operations in the cluster when the Stargate service becomes unavailable on a single CVM on an AHV node. Route injection is a mechanism that allows the CVMs to communicate with each other and redirect the I/O requests to another healthy CVM in the cluster. Route injection uses the Linux kernel routing table to add or delete routes dynamically, based on the availability of the Stargate service on each CVM.

https://portal.nutanix.com/page/documents/details?targetId=Prism-Central-Guide-Prism-v5_10:mul-pc-install-scratch-c.html

 According to the Nutanix Support & Insights web search result4, Prism Central can be installed manually on an AHV cluster by using three disk images: boot, home, and data. These disk images must be downloaded from the portal for the Prism Central VM and uploaded to an image service on the AHV cluster. The boot image contains the operating system and kernel for Prism Central. The home image contains the configuration files and logs for Prism Central. The data image contains the database and application files for Prism Central.

The correct answer is C. The VLAN was not created on the upstream switches.

A VLAN (virtual local area network) is a logical segmentation of a physical network that allows devices on the same VLAN to communicate with each other, regardless of their physical location. A VLAN also isolates the devices on different VLANs from each other, unless there is a router or a layer 3 switch that can route traffic between VLANs. To create a VLAN, the administrator needs to configure the network devices that are involved in the VLAN, such as switches, routers, and hosts. The administrator also needs to assign a unique VLAN ID to each VLAN, which is a number between 1 and 4094 that identifies the VLAN1.

In Nutanix AHV, the administrator can create a Nutanix managed network with a specific VLAN ID for guest VMs. This network can be assigned to VM NICs using Prism Element or Prism Central. However, creating a Nutanix managed network does not automatically create the VLAN on the upstream switches that connect the AHV hosts. The administrator needs to manually configure the upstream switches to allow the VLAN traffic on the ports that connect to the AHV hosts. The administrator also needs to ensure that the upstream switches are interconnected physically or virtually and can forward traffic between different VLANs if needed2.

Therefore, if an administrator has created a Nutanix managed network with a VLAN ID of 512 and notices that the VMs on that network can only communicate with other VMs on the same host, but not with VMs on different hosts in the cluster, the most likely cause of this issue is that the VLAN was not created on the upstream switches. This means that the switches are dropping or blocking the traffic with VLAN ID 512 and preventing it from reaching other hosts or VMs. To resolve this issue, the administrator should create the VLAN on the upstream switches and allow it on the ports that connect to the AHV hosts3.

Automated live migration is a feature of Nutanix that allows the cluster to automatically move VMs from one host to another without any downtime, in order to optimize the performance and availability of the cluster. According to the Nutanix documentation1, automated live migration can occur in the following scenarios:

• Cluster resource hotspot: When a host or a group of hosts experience high resource utilization, such as CPU, memory, or network, the cluster can automatically migrate some VMs to other hosts with lower utilization, in order to balance the load and avoid performance degradation.
• AOS upgrade: When upgrading the Nutanix software (AOS), the cluster can automatically migrate the VMs from the host that is being upgraded to another host in the same availability zone, in order to maintain the VM availability and minimize the impact of the upgrade process.
• AHV host maintenance mode: When putting an AHV host into maintenance mode, the cluster can automatically migrate all the VMs from that host to another host in the same availability zone, in order to prepare the host for maintenance operations such as hardware replacement or firmware update.

To periodically send information about cluster efficiency via email to a set of users, the administrator can follow these steps:

• Create a report in Prism Central that contains the relevant information about cluster efficiency.
• Add a schedule to the report to generate and send the report via email to the set of users at a specified frequency.

This will ensure that the users receive regular updates about the cluster efficiency without the need for manual intervention.

According to the Nutanix Prism Central Guide, role-based access control (RBAC) in Prism Central allows you to create custom roles and assign them to users or groups based on the categories of the entities they need to manage1. Categories are key-value pairs that you can assign to entities such as VMs, hosts, clusters, images, etc. to group them logically2. For example, you can create a category key called “OS” and assign values such as “Linux” or “Windows” to different VMs based on their operating system.

In the exhibit, the Linux Admin role has been created with the following settings:

• The role has the “VM Admin” permission, which allows the user to perform all actions on VMs3.
• The role has been assigned to the admin1 user.
• The role has been scoped to the entities that have the category key “OS” and the value “Linux”.

However, the admin1 user does not have access to all Linux VMs in the environment. This means that some of the Linux VMs do not have the proper category assigned to them. To grant the proper access, the administrator should add the category key “OS” and the value “Linux” to each Linux VM that needs to be managed by the Linux Admin role. This can be done either individually or in bulk through Prism Central4. Once the categories are added, the admin1 user will be able to see and manage all Linux VMs in the environment.

The storage policy value that can be inherited from a cluster is Compression. In the Nutanix Multicloud Infrastructure (NCP-MCI) 6.5, compression is a storage optimization feature that can be configured at the cluster level and inherited by all the entities within the cluster. This feature helps in reducing the storage footprint by compressing the data before writing it to the disk. The other options like IO performance, Storage Container, and QoS are not inherited from the cluster. They are configured and managed separately for each entity as per the requirements.

First Preference:

• Policy is applied to a specific entity

2nd Preference:

• Policy is applied to an entity type in a category

3rd Preference:

• Policy is applied to an entity type in a cluster

4th Preference:

• Policy is applied to all entities of an entity type

Comprehensive Detailed Explanation with References:In Nutanix Prism, when multiple alert policies are created and applied to the same entities, the policies are evaluated based on their specificity. The order of precedence from highest to lowest is as follows:

• Policy is applied to a specific entity: Custom alert policies that are applied to specific entities take precedence over those applied to broader categories. This is because the more specific policy is usually created with a particular context or requirement in mind for that entity.
• Policy is applied to an entity type in a category: The next level of precedence is given to policies that are applied to all entities of a certain type within a specific category. Categories allow grouping of entities based on certain criteria, and policies applied here are more specific than to an entire cluster or entity type.
• Policy is applied to an entity type in a cluster: This refers to policies that are applied to all entities of a certain type within a specific cluster. This is more general than the above two but still targets a specific cluster environment.
• Policy is applied to all entities of an entity type: The lowest precedence is given to policies that are broadly applied to all entities of a particular type across the entire Nutanix environment.

This order ensures that the most specifically targeted policies are given priority, which allows for fine-tuned control and customization of alert policies. The details of alert policy precedence are typically covered in the Nutanix Prism Central Guide and the documentation related to Prism Central's alerting and policies.

Stargate is the AOS process that handles all I/O operations for the cluster. It is responsible for determining whether an I/O from a user will be written to the OpLog or to the Extent Store, based on the type and size of the I/O. Stargate also performs data tiering, compression, deduplication, and erasure coding1. Stargate runs on every CVM and communicates with other Stargates to ensure data locality and redundancy2.

Shadow Clones is a Nutanix feature that provides effective caching optimization in VDI environments. VDI stands for Virtual Desktop Infrastructure, which is a technology that allows users to access virtual desktops hosted on a centralized server. VDI environments typically have a high degree of similarity among desktop images, which means that many VMs access the same data blocks from the storage layer. Shadow Clones leverages this similarity by creating read-only copies of frequently accessed data blocks on each node’s SSD tier, reducing network traffic and improving performance. Shadow Clones works automatically and transparently without any configuration or intervention from the administrator.

References: : [Fault Tolerance - Nutanix Bible] : [Block Awareness - Nutanix Bible] : [Block Awareness - Nutanix Support & Insights] : [Shadow Clones - Nutanix Bible] : [Shadow Clones - Nutanix Support & Insights] : [Shadow Clones - Nutanix Community]

http://www.vstellar.com/2019/01/10/ahv-networking-part-1 -basics/#:~:text=AHV%20Network%20Architecture&text=virbr0%20is%20an%20internal%20switch,virbr0)%20have%20IP%20address%20192.168.

Curator is the process that runs on every node in a Nutanix cluster and is responsible for data management tasks such as deduplication, compression, erasure coding, and replication factor compliance. Curator also handles disk failure recovery by scanning Cassandra to find all data previously hosted on the failed disk, and all disks in that node. Curator then rebuilds the data on other nodes in the cluster using the distributed storage fabric1.

The correct answer is D. VM Storage Controller Bandwidth.

VM Storage Controller Bandwidth is a metric that measures the amount of data that a VM is reading and writing to the storage fabric. The storage fabric is the network of storage controllers (CVMs) that provide distributed and fault-tolerant storage services to the VMs on the Nutanix cluster. The VM Storage Controller Bandwidth metric shows the read and write bandwidth in megabytes per second (MBps) for each VM. The higher the bandwidth, the more data the VM is transferring to and from the storage fabric1.

The administrator can use Prism Central to view the VM Storage Controller Bandwidth metric for each VM in a chart or a widget. The administrator can also use Prism Central to view other metrics related to the VM’s storage performance, such as VM Storage Controller IOPS, VM Storage Controller Latency, and VM Disk Usage2.

According to the Nutanix Support & Insights web search result3, advertised capacity is an advanced container setting that allows the administrator to reserve an advertised storage space for a storage container. An advertised capacity setting gives the hypervisor a maximum storage size that the storage container can use. This setting can be any arbitrary value greater than or equal to the resiliency required. The hypervisor ensures that the storage container storage doesn’t go beyond the advertised capacity. If the administrator wants a container to be displayed and limited to 1TB in the hypervisor, they should set the advertised capacity to 1TB.

In this case, the administrator wants to investigate the performance of a core banking system that consists of application servers and database servers. The application servers have high CPU utilization during business hours, which may indicate a bottleneck or a resource contention issue. The administrator needs to review multiple metrics in Prism Analysis Graphs to identify the root cause and determine if there is a problem with the app servers only, or with other components as well.

The metrics that are relevant for this analysis are:

• Cluster IO: This metric shows the input/output operations per second (IOPS) and throughput (MBps) of the cluster. It can help to understand if there is a high demand for disk IO from the VMs or if there is any latency or congestion in the storage layer.
• Cluster CPU: This metric shows the CPU utilization (%) and load average of the cluster. It can help to understand if there is enough CPU capacity in the cluster to handle the workload or if there is any imbalance or contention among hosts.
• Cluster Memory: This metric shows the memory utilization (%) and available memory (GB) of the cluster. It can help to understand if there is enough memory capacity in the cluster to support the VMs or if there is any pressure or swapping in the memory layer.
• Network: This metric shows the network throughput (MBps) and packets per second (pps) of the cluster. It can help to understand if there is enough network bandwidth in the cluster to transfer data between hosts and VMs or if there is any congestion or packet loss in the network layer.
• App Server CPU: This metric shows the CPU utilization (%) and load average of each application server VM. It can help to understand if there is any variation or anomaly in the performance of each app server or if there is any correlation with other metrics.
• Database Server CPU: This metric shows the CPU utilization (%) and load average of each database server VM. It can help to understand if there is any variation or anomaly in the performance of each database server or if there is any correlation with other metrics.

According to the Migration to a different processor web search result2, live migration of VMs depends on the source and destination hosts having the same CPU functions (CPU flags). Live migration requires the source and destination hosts to have CPUs from the same manufacturer, and only CPU functions which both hosts support are provided (same CPU generation, or by using VMware Enhanced vMotion Compatibility (EVC)). If the administrator adds a node with older generation processors to an existing AHV cluster with newer generation processors, then live migration of VMs is prevented between newer and older processors, unless EVC is enabled.

The cluster time zone is a setting that determines the time zone used by all CVMs in the cluster. The cluster time zone affects the timestamps of Nutanix logs, events, alerts, and reports. The cluster time zone also affects the scheduling of tasks such as snapshots, replication, and upgrades. By default, the cluster time zone is set to UTC (Coordinated Universal Time) when the cluster is created3.

To change the cluster time zone, the administrator needs to use the ncli (Nutanix command-line interface) on any CVM in the cluster. The steps are as follows4:

• Log in to any CVM using SSH.
• Run ncli cluster get-timezone to check the current cluster time zone.
• Run ncli cluster set-timezone timezone= to change the cluster time zone, where  is a valid time zone identifier (for example, America/New_York).
• Run ncli cluster get-timezone again to verify that the cluster time zone has been changed.

Note that changing the cluster time zone does not affect the time zone of Prism Element or Prism Central VMs. To change their time zone, the administrator needs to use Prism Element UI or Prism Central UI respectively5.

https://portal.nutanix.com/page/documents/solutions/details/?targetId=BP-2029_AHV:BP-2029_AHV

Administrators can use Acropolis with IPAM to deliver a complete virtualization deployment, including network management, from the unified Prism interface. This capability radically simplifies the traditionally complex network management associated with provisioning VMs and assigning network addresses. To avoid address overlap, be sure to work with your network team to reserve a range of addresses for VMs before enabling the IPAM feature.

The Acropolis master assigns an IP address from the address pool when creating a managed VM NIC; the address releases back to the pool when the VM NIC or VM is deleted.