Nutanix NCA-6.10 Nutanix Certified Associate NCA v6.10 Exam Practice Test

The default admin session logout time in Nutanix is15 minutes. If no activity is detected within this time, the session is automatically logged out for security reasons. This timeout can be adjusted in the system settings if needed, depending on organizational requirements.

References:

Nutanix Security Best Practices Documentation.

Nutanix Administration Guide - Session Timeout Configuration.

Redundancy Factor 3 (RF3) requires a minimum of five nodes in the cluster to ensure that data can be distributed across enough nodes to tolerate the failure of two nodes. If the cluster has fewer than five nodes, RF3 cannot be enabled.

A. Check that the cluster has been properly licensed:Licensing is not directly related to enabling RF3.

B. Check that the cluster has five or more nodes:Correct, as RF3 requires at least five nodes.

C. Check hardware availability of the nodes:While hardware health is important, it does not determine RF3 eligibility.

D. Check AOS version and upgrade, if needed:RF3 requirements are not specific to an AOS version.

References:

Nutanix Best Practices Guide for RF2 and RF3.

Nutanix Support KB Article on RF Configuration Requirements.

Non-migratable VMs in a Nutanix cluster typically include those with attached Volume Groups. This is because such VMs leverage direct-attached storage via iSCSI, which ties them to a specific host, preventing live migration to another host. Volume Groups provide block storage to applications, and the iSCSI protocol does not support live migration of such connections.

Here's a breakdown of the options:

A. VMs without NGT:Nutanix Guest Tools (NGT) are used for guest-level integration but do not affect VM migratability.

B. VMs marked as an Agent:This setting does not inherently make VMs non-migratable. It primarily affects roles and tasks within certain configurations.

C. Memory Overcommitted:While memory overcommitment can affect performance, it does not make VMs non-migratable. Nutanix AHV handles memory allocation dynamically.

D. VMs with attached Volume Groups:Correct answer, as the iSCSI connections used by Volume Groups are host-specific and cannot migrate seamlessly.

References:

Nutanix AHV Administration Guide: Nutanix Documentation

Nutanix Support KB Article on Volume Groups and VM Migration Limitations.

Nutanix University Certification Materials, NCP and NCM course modules.

When using ESXi as the hypervisor in a Nutanix cluster, the supported storage protocol for a datastore isNFS (Network File System). Nutanix exposes its distributed storage to ESXi hosts using NFS for VM storage. This protocol is simple to configure and provides high performance and reliability through Nutanix’s data services.

Other options:

iSCSI: Not typically used for ESXi datastores but can be utilized for specific use cases like external storage connectivity.

SMB: Not supported for ESXi datastores.

LVM: Logical Volume Management is not used in this context.

References:

Nutanix Best Practices for Running VMware vSphere on Nutanix.

VMware Compatibility with Nutanix Clusters Documentation.

Nutanix Storage Protocol Support Overview.

Nutanix licensing is available in three tiers:

Starter: Entry-level features for basic virtualization and storage requirements.

Pro: Advanced features such as data protection and disaster recovery.

Ultimate: Comprehensive feature set, including advanced analytics and automation.

This tiered approach enables administrators to choose the appropriate license level based on their business requirements.

References:

Nutanix Licensing Overview Documentation.

Nutanix Support Portal - Licensing Details.

In aRedundancy Factor 3 (RF3)cluster,5 copies of the metadataare maintained to ensure data durability and cluster resiliency. RF3 provides fault tolerance against up to two simultaneous failures (e.g., node or disk failures) and requires more metadata copies to achieve this level of protection.

Other redundancy factors:

RF2maintains 3 copies of metadata.

RF3 requires at least 5 metadata copies to protect against additional failures.

References:

Nutanix Storage Concepts Guide - Redundancy Factors.

Nutanix Metadata Management Documentation.

By default, Nutanix Lifecycle Manager (LCM) auto-inventory runs at2:00 AMlocal cluster time. LCM performs a daily check to gather information about available updates for firmware, software, and other components to ensure the cluster remains up-to-date. This operation is non-disruptive and does not impact cluster performance.

References:

Nutanix Lifecycle Manager (LCM) Documentation - Default Settings.

Nutanix Support Portal - LCM FAQ.

To run a full health check in Prism Element, the administrator should first select theActionsmenu. From there, the administrator can choose to execute health checks for the entire cluster or specific components. This ensures a comprehensive evaluation of the cluster’s health.

Other options:

Scheduled: Refers to predefined or automated health checks.

Checks: Displays the list of checks but doesn’t initiate them.

Failed: Filters checks based on their status but doesn’t start a new check.

References:

Nutanix Cluster Health Documentation.

Nutanix Prism Element User Guide - Health Check Procedures.

To verify if the cluster is currently protected from potential data loss due to a component failure, the administrator should check theData Resiliency Status widgeton the Prism Element Home dashboard. This widget provides real-time information about the cluster's resiliency status, including warnings or errors about data redundancy or protection.

Other options:

A. Select the gear icon and then select Pulse:Pulse is used for telemetry data, not data resiliency status.

B. Click on Home and then Alerts:Alerts show specific issues but do not directly indicate the overall resiliency status.

D. Navigate to the Health dashboard:The Health dashboard provides detailed health checks but does not display the current resiliency status.

References:

Nutanix Administration Guide - Data Resiliency Status.

Nutanix Prism UI Documentation - Dashboard Overview.

To enable Windows Defender Credential Guard, the VM must be configured withUEFI(Unified Extensible Firmware Interface) instead of Legacy BIOS. UEFI provides the necessary support for Secure Boot and Virtualization-Based Security (VBS), both of which are prerequisites for Credential Guard.

Steps:

When creating or editing the VM, selectUEFIas the firmware type.

Ensure Secure Boot and VBS are enabled in the OS configuration.

References:

Microsoft Windows Defender Credential Guard Requirements.

Nutanix AHV VM Configuration Guide - UEFI Support.

TheReserved Capacityoption in a storage container explicitly reserves a portion of cluster storage for that container. This reservation reduces the amount of storage available for other containers. Reserved Capacity ensures that specific workloads have guaranteed storage resources, preventing resource contention or overcommitment.

Other options:

Advertised Capacity: Defines the storage limit displayed to users but does not reserve storage.

Erasure Coding: Optimizes storage efficiency but does not reduce available capacity.

Capacity Deduplication: Reduces space consumption by eliminating duplicate data but does not affect other containers' storage.

References:

Nutanix Storage Best Practices Guide.

Nutanix Prism UI Help - Storage Container Configuration.

WSZC

When using the LCM (Life Cycle Manager) Dark Site procedure, theLCM Frameworkshould be checked and upgraded first. The LCM Framework is the core component responsible for orchestrating updates for other Nutanix software components. Ensuring the framework is up to date guarantees compatibility and reliability during subsequent upgrades.

A. MSP:Incorrect, as MSP (Managed Service Provider) is not directly related to the LCM Dark Site procedure.

B. Foundation:Incorrect, as Foundation is used for initial cluster deployment, not for lifecycle management.

C. NCC:While NCC is critical for health checks, it does not need to be updated first in the LCM process.

D. LCM Framework:Correct, as it manages the update process and must be updated first.

References:

Nutanix Life Cycle Manager Guide.

Nutanix Support Knowledge Base Article on LCM Dark Site Upgrades.

TheRecycle Binin Nutanix clusters temporarily stores deleted VMs for 24 hours, allowing administrators to recover them if needed. This feature helps protect against accidental deletions by providing a grace period for recovery before permanent deletion occurs.

A. Stores the OpLog's most recent deleted data in case of a CVM failure:Incorrect, as the OpLog pertains to write operations, not VM deletion.

B. Keeps deleted VMs for 24 hours for recovery:Correct, as the Recycle Bin's purpose is temporary VM recovery.

C. Allows administrators to undo the last five actions:Incorrect, as there is no such feature for undoing multiple actions in Prism.

D. Centralizes the deleted data from the different VMs in the cluster:Incorrect, as the Recycle Bin is specifically for deleted VMs, not generalized data centralization.

References:

Nutanix Administration Guide: Recycle Bin Functionality.

Nutanix Support Knowledge Base Article on VM Recovery via Recycle Bin.

Nutanix AHV (Acropolis Hypervisor) supports integrated IP address management (IPAM) as a built-in feature. IPAM allows administrators to dynamically allocate and manage IP addresses for VMs within a network segment. This functionality simplifies network management by automating the assignment of IPs without relying on external DHCP servers.

A. ESXi:Incorrect, as ESXi does not include built-in IPAM.

B. Hyper-V:Incorrect, as Hyper-V lacks integrated IPAM functionality.

C. AHV:Correct, as AHV has built-in IPAM for automated IP address allocation.

D. XenServer:Incorrect, as XenServer does not support integrated IPAM.

References:

Nutanix AHV Networking Guide: IPAM Configuration.

Nutanix University: AHV Networking Module.

When a Nutanix cluster alert occurs, indicating maintenance mode issues, the most likely cause is that another node in the cluster is already in maintenance mode. Nutanix clusters enforce restrictions to prevent more than one node from entering maintenance mode simultaneously. This ensures the cluster can maintain resiliency and availability, adhering to the redundancy factor (RF) policy.

If another node is already in maintenance mode, the cluster cannot afford to have additional nodes enter maintenance without compromising data and service availability.

References:

Nutanix Cluster Best Practices Documentation - Maintenance Mode.

Nutanix Alerts and Events Guide, accessible via Prism UI.