Free Nutanix NCP-MCI-6.5 Practice Exam with Questions & Answers | Set: 2

A storage policy can be associated with a VM. A storage policy is a set of rules that define how data objects are stored and protected. It specifies the characteristics of storage, data protection, and data placement for virtual disks that are assigned to a VM. Subnets, catalogs, and categories are not associated with storage policies.https://portal.nutanix.com/page/documents/details?targetId=Prism-Central-Guide-vpc_2022_6:mul-cluster-storage-policy-summary-view-pc-r.html

A. This statement is incorrect because there is no static threshold set to trigger a critical alert at 6000 MB. The graph shows a peak that goes above 6000 MB, but the alert configuration below does not specify a static threshold at this value.

B. This is the correct statement. The configuration under "Behavioral Anomaly" is set to alert every time there is an anomaly, with a critical level alert set to trigger when the I/O working set size is between 0 MB and 4000 MB. The graph illustrates that the anomalies (highlighted in pink) occur when the working set size exceeds the normal range (blue band). Therefore, any anomaly detected above 4000 MB would trigger a critical alert.

C. This statement is incorrect because there is no indication that a warning alert is configured to trigger after 3 anomalies. The exhibit does not show any configuration that specifies an alert based on the number of anomalies.

D. This statement is incorrect as there's no indication that a warning alert will be triggered based on the I/O working set size exceeding the blue band. The alert settings are configured to ignore anomalies below 4000 MB and to trigger a critical alert for anomalies above this threshold.

The settings displayed in the exhibit are typically part of Nutanix's Prism infrastructure management platform, which can set various thresholds for performance metrics and trigger alerts based on those thresholds. The behavior is defined in the Prism documentation where the alert configuration is outlined.

Prism Central is a multi-cluster manager that provides a single, centralized management interface for Nutanix environments1. Prism Central can be deployed in different configuration scenarios, depending on the network and security requirements of the environment. Some of the valid scenarios are:

• Environments use Network Address Translation (NAT): NAT is a method of mapping one IP address space to another by modifying network address information in IP datagram packet headers while they are in transit across a traffic routing device2. NAT can be used to enable communication between Prism Central and Prism Elements that are in different networks or subnets3. For example, Prism Central can be deployed in a public cloud and use NAT to access Prism Elements that are in a private data center3.
• Prism Elements and Prism Central are in different subnets: A subnet is a logical subdivision of an IP network that allows multiple networks to share a single physical network4. Prism Elements and Prism Central can be in different subnets as long as they can communicate with each other through routing or NAT3. For example, Prism Central can be deployed in a management subnet and access Prism Elements that are in different application subnets3.
• Environments do not have Internet access: Internet access is not required for the deployment of Prism Central, as long as the environment meets the prerequisites and considerations for installing or upgrading Prism Central. For example, Prism Central can be deployed in a dark site, which is an environment that does not have Internet access or has restricted Internet access. In this case, the administrator needs to manually enable microservices infrastructure and download the required software packages from another source.

Based on the VM performance metrics shown in the exhibit, the most likely cause of the poor performance in the particular VM is that the host’s CPU is severely overloaded. This is indicated by the high percentage of Hypervisor CPU Ready Time, which is shown as 96% in the CPU ready chart. CPU Ready Time is a metric that shows the amount of time a VM is ready to run but is unable to run because the host CPU resources are not available. In a healthy environment, this value is typically low. A high percentage indicates that the VMs are waiting for available CPU cycles, which means the CPU is not able to schedule the VM effectively, often due to overcommitment or heavy CPU load.

When the CPU ready time is consistently high, it is a clear indicator that the VM is frequently waiting for CPU resources, which can lead to performance issues such as sluggishness or delays in processing. It is not related to the storage subsystem (Oplog fullness or SSD tier size), nor directly to the number of vCPUs assigned to the VM. While adding more vCPUs might seem like a solution, it could actually exacerbate the issue if the host is already CPU constrained.

To resolve this issue, an administrator should consider balancing the load across the hosts more effectively, possibly by using Nutanix's built-in automation and balancing features, or by scaling out the cluster to add more CPU resources. It is also advisable to check for any VMs with unusually high CPU demand and to adjust resource allocation as needed. Nutanix provides extensive documentation and guidelines in their Resource Management Guide to help administrators identify and resolve such performance issues.

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.

Answer: A. VM-VM anti-Affinity policy

A VM-VM anti-Affinity policy is a rule that ensures that two or more VMs don’t run on the same AHV host. It’s useful when an application provides HA and an AHV host can’t be an application’s single point of failure1. In this case, the SQL cluster VMs should have a VM-VM anti-Affinity policy configured to prevent them from running on the same host and causing an outage if that host fails. A VM-VM anti-Affinity policy can be created using the aCLI commands2. The other options are not relevant for this scenario.

References: 1: Affinity Policies - Nutanix Support & Insights 2: Affinity Policies Help | Nutanix Community

The default network configuration for AHV hosts and CVMs is a bond named br0-up with two or more uplinks in active-backup mode. This means that only one uplink is active at a time, while the others are in standby mode. This provides high availability, but not load balancing or increased bandwidth. To increase the bandwidth available to the AHV host and the CVM, the administrator can change the bond mode to Active-Active, which allows all uplinks to be used simultaneously. This can be done using the manage-ovs commands on each AHV host. The steps are as follows1:

• Log in to the AHV host using SSH.
• Enter maintenance mode on the CVM by running allssh 'cluster status | grep -i cvm | grep -i down'.
• Change the bond mode to Active-Active by running manage_ovs --bond_mode active-active update_uplinks br0-up , where  is a comma-separated list of uplink interfaces (for example, eth0,eth1).
• Verify the bond mode by running manage_ovs show_uplinks.
• Exit maintenance mode on the CVM by running allssh 'cluster start'.

According to the web search results, the most efficient action an administrator should take to ensure a supported state when adding a node with a higher AOS release to an existing cluster is to perform a standalone reimage of the new node and then add it to the cluster1. This way, the new node will have the same AOS version as the existing nodes, and there will be no compatibility issues or downtime. Therefore, option C is correct, while options A, B, and D are not.

https://portal.nutanix.com/page/documents/details/?targetId=Web_Console_Guide-Prism_v4_7:lic_licensing_managing_c.html

Reclaiming Licenses (Including License Renewal)

You can reclaim and optionally re-apply licenses for nodes in your clusters:

• You must reclaim licenses when you plan to destroy a cluster. First reclaim the licenses, then destroy the cluster. You do not need to reclaim Starter licenses. These licenses are automatically applied whenever you create a cluster, including after you have destroyed a cluster.
• Return licenses to your inventory when you remove one or more nodes from a cluster. Also, if you move nodes from one cluster to another, first reclaim the licenses, move the nodes, then re-apply the licenses.
• You can reclaim licenses for nodes in your clusters in cases where you want to make modifications or downgrade licenses. For example, applying an Ultimate license to all nodes in a cluster where some nodes are currently licensed as Pro and some nodes are licensed as Ultimate. You might also want to transition nodes from Ultimate to Pro licensing.
• You must reclaim licenses when you renew licenses. First reclaim the expired licenses, then apply new licenses.

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.