NCA-6.5 questions and answers

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.

Network segmentation is the best feature or configuration for securing network traffic between the management and storage replication environments. Network segmentation is the practice of dividing a computer network into subnets, each serving a different purpose or function. By dividing the network into different segments, it is possible to control and monitor the flow of traffic between the different segments, and to implement different security policies for each segment.
For example, the management environment could be segmented from the storage replication environment, and only specific traffic, such as management traffic, would be allowed to flow between the two segments.
This can help to protect the management environment from potential security threats that may originate from the storage replication environment.
Other options like firewall rules, VM anti-affinity rules, and different storage containers can also help to secure network traffic, but network segmentation provides a more comprehensive and granular way to secure the traffic between different environments. You can find more information on this topic in the Nutanix Security Configuration Guide, which is available on the Nutanix support website:
https://portal.nutanix.com/#/page/docs/details?targetId=Security-Guide-v5_24:Security-Guide-v5_24

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.
References:
https://www.nutanix.com/what-is-nutanix/distributed-storage-fabric/

Discoveries within the Nutanix Support Portal are used to identify clusters that are affected by known issues. This can help Nutanix Support quickly identify and address any potential problems that may be caused by a specific issue.
References:
https://portal.nutanix.com/page/documents/details?targetId=Support-Portal-User-Guide-v2_0:sp-discoveries-c.html

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.
References:
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".

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.

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.
References:
https://www.nutanix.com/products/app-mobility-fabric

After a Protection Domain is migrated, an administrator should mount datastores on hosts to make sure that the data is accessible by the virtual machines running on those hosts.
References:
Nutanix Certified Associate 6.5 Exam Study Guide, page 54

In a Nutanix environment, the product or feature most suitable for deploying a Microsoft SQL cluster is Nutanix Objects. Nutanix Objects is a S3-compatible object storage solution that provides a highly scalable and durable storage for unstructured data. It is built on top of the Nutanix Distributed File System (NDFS) and provides a high-performance, scalable, and highly available storage solution. One of the key features of Nutanix Objects is its ability to support Microsoft SQL Server Always On Availability Groups (AAG) on S3 object storage. This allows you to deploy a highly available SQL cluster on Nutanix, with the ability to failover SQL services to a different node in the event of a failure, and provide high availability and disaster recovery for SQL databases.

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)

The manage-ovs command can be used to find the correct VLAN ID from the CVM, as it allows the administrator to view and configure network settings for Open vSwitch (OVS). The ifconfig command can be used to view network interfaces and IP addresses, but not VLAN IDs. The acli command can be used to manage Acropolis services and objects, but not network settings. The ovs-vsctl command can be used to view and configure OVS settings, but it is not available on the CVM.
References:
https://www.nutanix.com/content/dam/nutanix/resources/misc/ebg-nca-6-5.pdf
(page 38)

Nutanix supports high availability (HA) for VMs by automatically restarting them on other nodes in the cluster in case of a node failure. The cluster CPU and memory utilization will increase temporarily until the failed node is recovered, but there will be no user impact.
References:
https://www.nutanix.com/content/dam/nutanix/resources/misc/ebg-nca-6-5.pdf
(page 28)