NCA-6.10 Nutanix Certified Associate NCA v6.10 Question and Answers

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.

TheNutanix Moveutility is specifically designed for migrating VMs between hypervisors, including from ESXi to AHV. It automates the migration process while ensuring minimal downtime. Nutanix Move supports pre-migration assessments and automates data transfer and VM configuration for AHV.

A. Move:Correct, as it is the Nutanix tool for hypervisor migrations.

B. acli:Incorrect, as acli is used for command-line configuration and management within AHV, not migration.

C. Flow:Incorrect, as Nutanix Flow focuses on network security and micro-segmentation.

D. Ncli:Incorrect, as Ncli is a command-line utility for cluster management, not migration.

References:

Nutanix Move Documentation: Supported Workflows.

Nutanix University Training on VM Migration.

Applying tags to licenses to streamline future renewals is a task that can be completed inPrism Central Licensing. Prism Central provides centralized license management for clusters, enabling administrators to apply and manage license tags, which simplifies tracking and renewal tasks across multiple clusters. Here's how it works:

Prism Central Licensing Overview:Prism Central includes a dedicated licensing interface that provides a consolidated view of all licenses associated with your clusters. From this interface, administrators can categorize licenses using tags such as "Renewal-2025" or "Production," making it easier to identify and manage renewals or assignments.

Steps to Apply Tags in Prism Central:

Navigate toPrism Central > Settings > Licensing.

Select the desired license(s) from the list.

Use the "Tags" option to create or apply predefined tags to categorize these licenses.

Why Not Other Options?:

A. Clusters in the Support Portal: The Support Portal is primarily used for support-related tasks, such as managing cases or accessing documentation, and does not include license tagging capabilities.

B. License Inventory in the Support Portal: While the Support Portal allows you to view license inventory, it does not support operational tasks like tagging.

D. Prism Element Licensing: Prism Element is focused on managing licensing for individual clusters and lacks the centralized management and tagging functionality available in Prism Central.

References:

Nutanix Prism Central Guide - Refer to the Licensing section in the official guide for detailed instructions.

Nutanix Licensing Overview - Explains Prism Central licensing features.

Nutanix University Certification Blueprints - Licensing topics often covered in relevant Nutanix certification courses.

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.

On a newly deployed AHV cluster, the default uplink bond type for the virtual switch (vs0) isBalance-SLB (Source Load Balancing). This configuration balances traffic across the uplinkinterfaces based on the source of the traffic, ensuring optimal usage of available network bandwidth without requiring LACP configuration on the physical switches.

References:

Nutanix AHV Networking Guide - Default Uplink Bond Types.

Nutanix Networking Best Practices for AHV Clusters.

Shared storage for Windows Server Failover Clustering (WSFC) is a use case for NutanixVolumes. Nutanix Volumes provides block storage (via iSCSI) to external systems, such asWSFC nodes, allowing them to share storage for failover clustering. This configuration is essential for high availability in Windows environments.

Other options:

Files: Provides file-based storage (NFS/SMB), not suited for WSFC shared block storage.

FT1 and RF2: Refer to Fault Tolerance and Redundancy Factor, not storage solutions.

References:

Nutanix Unified Storage Guide - Volumes Use Cases.

Nutanix Best Practices for Windows Clustering.

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.

When configuring dual encryption in Nutanix, anExternal Key Manager(EKM) is required. This allows the cluster to use an external hardware-based or software-based key management system to securely store and manage encryption keys. The combination of external and native encryption ensures compliance with high security standards.

A. Trusted Platform Module:Incorrect, as TPM is not used for managing dual encryption keys.

B. External Key Manager:Correct, as dual encryption relies on an external system to manage keys.

C. Native Key Manager:Incorrect, as native key management alone does not support dual encryption.

D. Lockdown Mode Enabled:Incorrect, as Lockdown Mode relates to cluster security, not encryption key management.

References:

Nutanix Data-at-Rest Encryption Guide.

Nutanix Support Documentation on Dual Encryption and Key Management.

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.

To create a VM-VM Anti-Affinity Policy ensuring VMs are not placed on the same hypervisor,Prism Centralis required. Anti-affinity policies are cluster-wide configurations managed through Prism Central’s policy-based interface, enabling placement rules to distribute workloads effectively.

Steps:

Navigate toPrism Central > Policies.

Create a new Anti-Affinity Policy.

Select the VMs and configure the policy to ensure separation.

References:

Nutanix Prism Central Guide - Policy Management.

Nutanix Best Practices for VM Placement Policies.

The Controller VM (CVM) uses thevs0bridge by default to communicate with the AHV host it runs on. Thevs0bridge is a virtual switch configured on the AHV host, providing connectivity between the CVM, virtual machines, and external networks. This setup ensures efficient network communication within the Nutanix cluster.

Other options:

virbro: Typically used in standalone KVM configurations, not in Nutanix AHV.

broandbridge0: Incorrect references to Nutanix networking structures.

References:

Nutanix AHV Networking Guide - Bridge Configuration.

Nutanix Prism Networking UI Documentation.

Replication Factor (RF) defines the number of copies of data stored in a Nutanix cluster. RF2 ensures two copies of data, and RF3 ensures three copies. This redundancy allows the system to maintain data integrity and recoverability even in the event of hardware failures.

A. It limits the scope of hardware failures during recovery operations:Incorrect, as RF focuses on data replication, not limiting failure scopes.

B. It ensures that multiple copies of data are available for recovery:Correct, as RF directly relates to data redundancy and recovery capabilities.

C. It accelerates data transfer to remote backup sites:Incorrect, as RF does not affect remote backup speed.

D. It reduces the need for offsite backup solutions:Incorrect, as RF works within the cluster, not as a replacement for offsite backups.

References:

Nutanix Bible: Replication Factor Overview.

Nutanix Support Documentation on RF2 and RF3.