NCA-6.5 Nutanix Certified Associate (NCA) v6.5 exam Questions and Answers

Administrators can use recovery plans to specify groups of virtual machines and assign them to a destination for disaster recovery using Leap. Reference: Nutanix Certified Associate 6.5 Exam Study Guide, page 56

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.

To send weekly performance reviews to several line of business managers about VMs they are managing, the administrator should use Prism Central Reports with a schedule. Prism Central Reports is a tool that allows the administrator to create custom reports, which can include information such as CPU usage, memory usage, and disk I/O for specific VMs. The administrator can schedule the reports to be generated and sent out on a regular basis, such as weekly. This will allow the line of business managers to review the performance of the VMs they are responsible for on a regular basis, and take appropriate actions if necessary. Reference: https://portal.nutanix.com/page/documents/details?targetId=Prism-Central-Admin-Guide-v5_11:pcc-reports-overview_pcc-reports-overview.html

An administrator can create an Entity Chart to view the logical usage for multiple storage containers in one chart. This chart can be created from the Prism Element dashboard, and it provides a visual representation of the logical usage of each container, allowing administrators to easily compare the usage of multiple containers at once.

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

Direct Upload is a LCM feature that simplifies upgrades on clusters without Internet access. It allows users to upload the desired version of the software to the cluster using a USB drive or other portable storage device, and then install it without the need to access the Internet. Reference: https://portal.nutanix.com/page/documents/details?targetId=Platform-Administrator-Guide-v5_7:pag-lcm-direct-upload-c.html

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.

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)

Categories enable Image Placement Policies to be mapped to target clusters by defining a set of key-value pairs that can be applied to clusters, hosts, or VMs. Categories can be used to control where images are replicated and stored. References: https://www.nutanix.com/content/dam/nutanix/resources/misc/ebg-nca-6-5.pdf (page 23)

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

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

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/

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

HTTP is the only option available for an administrator to upload a remote disk file to Image Configuration. FTP, SCP, and SFTP are not supported by Nutanix. References: https://www.nutanix.com/content/dam/nutanix/resources/misc/ebg-nca-6-5.pdf (page 24)

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. Reference: https://portal.nutanix.com/page/documents/details?targetId=Support-Portal-User-Guide-v2_0:sp-discoveries-c.html

In order to resolve the issue of not receiving NCC health checks and alerts for newly-added nodes via email, the administrator should configure SMTP (Simple Mail Transfer Protocol) settings. SMTP is used to send email notifications from the Nutanix cluster, and if it is not configured properly, the health checks and alerts will not be sent via email. The administrator should check the SMTP settings in the Prism web console and ensure that they are correct and that the correct email address is specified for receiving notifications. This will ensure that the health checks and alerts for the newly-added nodes are sent to the correct recipient.