Nutanix NCA-6.5 Practice Test - Questions Answers, Page 4

From Prism Central's main dashboard page, an administrator can access any cluster by clicking the cluster quick access link. This will open the cluster summary page, which contains detailed information about the cluster, including the nodes, virtual machines, and applications running on the cluster. Reference: https://portal.nutanix.com/page/documents/details?targetId=Platform- Administrator-Guide-v5_7:pag-prism-central-cluster-access-c.html

A virtual network with IPAM (IP Address Management) supports automatically assigning IP addresses to VMs. This eliminates the need for manual configuration of IP addresses for each VM, and makes it easy to manage and track IP address usage.

Reference: https://portal.nutanix.com/page/documents/details?targetId=Platform-Administrator-Guide-v5_7:pag-network-ipam-c.html

Role-based access control (RBAC) allows administrators to configure access control for different users and groups in the Nutanix cluster. This feature is available through Prism Central, where administrators can configure roles and permissions for different users and groups.

Reference: https://portal.nutanix.com/page/documents/details?targetId=Platform-Administrator-Guide-v5_7:pag-user-role-c.html

Nutanix's scale-out storage technology, the Distributed Storage Fabric, makes its hyperconverged platform possible. It provides a single, unified layer of storage to multiple nodes in a cluster, allowing data to be stored, accessed, and processed in a distributed, fault-tolerant manner.

Reference: https://www.nutanix.com/what-is-nutanix/distributed-storage-fabric/

To upgrade the LCM framework to the latest version, the administrator must go to the Settings page of the Prism Central UI, and then select the Upgrade Software option. This will show the available versions of the LCM framework, and allow the administrator to select the desired version and upgrade. Reference: https://portal.nutanix.com/page/documents/details?targetId=Platform- Administrator-Guide-v5_7:pag-lcm-upgrade-c.html

In the case of a single host in a four-node AHV-based cluster experiencing a complete network failure, the user VMs running on that host will stay up, but will be unreachable until connectivity is restored. This is because if more than enough resources exist in the cluster to tolerate a node failure, the VMs will continue to run, but will be unable to communicate with other nodes in the cluster due to the network failure. This is stated in the official Nutanix Certified Associate (NCA) v6.5 study guide on page 49, under the heading "Virtual Machine Availability in the Event of Node Failure".

Anti-affinity rules are used to ensure that virtual machines are not running on the same physical host. This can be useful in situations where the administrator wants to ensure that virtual machines are running on different hosts for high availability and to minimize the impact of a host failure. By creating an anti-affinity rule via CLI, the administrator can ensure that the SQL Server VMs are running on different hosts while still leveraging high availability in case of host failure. Reference:

https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v5_11:wcaffinity-anti-affinity-rules_wc-affinity-anti-affinity-rules.html

When an SSD fails within a node, the CVM on that node will reboot to maintain the health of the cluster. The CVM is responsible for managing the storage and virtualization components of the cluster, and a reboot is necessary to ensure that the cluster continues to function properly. The VMs running on that host will not be affected and continue to run, but the CVM will be unavailable for a short period of time until the reboot is completed. The Cluster continues to operate in a healthy state and doesn't go in read-only mode or cause any host to go down. Reference:

https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v5_11:wcmonitoring-cluster-health_wc-monitoring-cluster-health.html