NCA-6.5 Practice Exam Questions with Answers Nutanix Certified Associate (NCA) v6.5 exam Certification

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

 To display potentially reclaimable resources in a Nutanix cluster running out of memory, an administrator can use the List of Inactive VMs and List of Overprovisioned VMs predefined views for Reporting 

ADS is a feature of Nutanix AHV (Acropolis Hypervisor) that proactively monitors a Nutanix cluster for compute and storage I/O contention or hotspots over a period of time [1]. It provides dynamic and intelligent scheduling of workloads on the cluster for optimal performance and utilization.

Compression is a Nutanix storage efficiency feature that is suitable for nearly every workload, as it reduces the amount of data stored on disk without impacting performance. Erasure Coding, Deduplication, and Thick Provisioning are other storage efficiency features, but they have different trade-offs and use cases. References: https://www.nutanix.com/content/dam/nutanix/resources/misc/ebg-nca-6-5.pdf (page 30)

To maintain high availability in the case of a node failure in a two-node cluster, a Witness VM is required. Therefore, the correct answer is A. The Witness VM acts as a tie-breaker and arbitrator in the event of a split-brain scenario, where both nodes lose connectivity to each other, to ensure that only one node continues to operate and serve workloads. It is also recommended to use a high-performance network to minimize network latency between the two nodes and the Witness VM.

The type of relationship that a VM Affinity policy defines is VM to Host. A VM Affinity policy is used to specify which host a virtual machine should be placed on. This can be used to ensure that certain VMs are always running on the same host for performance or availability reasons. Additionally, VM Affinity policies can also be used to ensure that VMs are spread across multiple hosts for better load balancing.

The oplog is a critical component of the Nutanix distributed storage fabric and can be impacted by high CPU Ready time. When the CPU Ready time is high, there can be delays in writing data to the oplog, resulting in slower overall cluster performance. Additionally, high CPU Ready time can also lead to increased write amplification, further reducing I/O performance.

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:wc-affinity-anti-affinity-rules_wc-affinity-anti-affinity-rules.html

Replication Factor 2 (RF2) refers to the number of copies of data written in the cluster. When RF2 is enabled, the Nutanix Distributed File System (NDFS) will create two copies of the data, resulting in higher levels of data durability and availability. Reference: https://portal.nutanix.com/page/documents/details?targetId=Advanced-Administration-v5_7:aa-ndfs-rf2-c.html

When upgrading AOS in a vSphere-based Nutanix cluster with no automatic live migration, the VMs will continue to run on the same host, providing that the VMs have neither affinity nor anti-affinity rules configured. The upgrade process will put the host into maintenance mode, which will cause the VMs running on that host to be suspended temporarily. Once the AOS upgrade is completed, the host will be taken out of maintenance mode, and the VMs will be resumed, but running on the same host. The AOS upgrade process does not automatically live migrate VMs to other hosts, because the automatic live migration feature is not enabled in the cluster. Reference: https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v5_11:wc-upgrading-aos_wc-upgrading-aos.html

The Compatibility and Interoperability Matrix (CIM) is the resource that should be used to ensure a successful upgrade of the hypervisors and AOS within a vSphere-based Nutanix cluster. The CIM provides information about the compatibility and interoperability of the different components of the Nutanix cluster, including the hypervisors, AOS, and other related components. Reference: https://www.nutanix.com/support/compatibility-matrix/

App Mobility Fabric is a technology from Nutanix that allows applications and data to move freely between runtime environments. It allows applications and data to be moved from one environment to another without any disruption or downtime. Reference: https://www.nutanix.com/products/app-mobility-fabric

The Data Services IP address is the address that allows external connections to Nutanix storage presented by the Volumes feature. This address is used to access the storage from external sources and is used for replication and external snapshotting. Reference: https://portal.nutanix.com/page/documents/details?targetId=Prism-Admin-Guide-v5_6:pr-storage-storage-networks-c.html

Pulse should only be disabled under the guidance of Nutanix Support and not for any other reason. Pulse is a feature of the Nutanix cluster that enables the cluster to report back health and performance data to Nutanix for troubleshooting and performance optimization purposes. Disabling Pulse without the guidance of Nutanix Support is not recommended, as it could lead to potential issues with the cluster. Reference: https://portal.nutanix.com/page/documents/details?targetId=Platform-Administrator-Guide-v5_7:pag-pulse-c.html

A vDisk is a file that is stored on storage devices owned by a CVM. A vDisk represents a virtual disk that is attached to a VM or a CVM. A Storage Pool is a logical grouping of physical disks in a cluster. An Extent Group is a collection of data blocks that belong to a vDisk. A Container is a logical grouping of vDisks that share the same storage policies and settings. References: https://www.nutanix.com/content/dam/nutanix/resources/misc/ebg-nca-6-5.pdf (pages 31-32)

Nutanix Objects is a storage service that can store petabytes of unstructured data and supports S3 APIs. It is a distributed object store that provides an easy-to-use interface for storing and managing objects and data. It also provides advanced features such as versioning, replication, encryption, and access control. Reference: https://portal.nutanix.com/page/documents/details?targetId=Platform-Administrator-Guide-v5_7:pag-objects-c.html

When uploading images from a local workstation to Prism Central, the destination cluster is determined based on the alphabetical order of the cluster names. Specifically, the first available cluster in alphabetical order is selected as the destination for the image upload.

This behavior is documented in the Prism Central Admin Guide, which states that when you upload an image to Prism Central, "the image is stored in the first cluster that has sufficient space and starts with the letter that appears first in the image name."

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”.

Link Aggregation Control Protocol (LACP) is a NIC-teaming configuration that balances network traffic based on source/destination IP addresses and TCP/UDP ports. LACP allows the administrator to configure multiple NICs as a single logical NIC, known as a Link Aggregation Group (LAG), which can increase the available bandwidth and provide redundancy. LACP uses a hashing algorithm to distribute traffic across the NICs in the LAG, based on the source and destination IP addresses and TCP/UDP ports. This ensures that traffic is evenly distributed across the NICs, which helps to improve overall network performance and availability. Reference: https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v5_11:wc-network-configuring-uplink-ports_wc-network-configuring-uplink-ports.html

Check the below.