NCA-V6-10 Sample Questions & Answers

Image Placement Policies in Prism Central are designed specifically for this purpose. They allow an administrator to control how images are distributed across multiple registered clusters. By creating a policy and selecting the desired clusters, Prism Central will automatically replicate and maintain the specified image on only those clusters, ensuring consistency and availability where needed.

With RF2, the Nutanix Distributed Storage Fabric (DSF) maintains two copies of all data on different nodes/disks. When one disk fails, the data remains fully accessible from its replica. DSF will then automatically start a rebuild process to create a new replica on another healthy disk to restore the cluster to full resiliency.

The Distributed Storage Fabric (DSF) is the core component of the Nutanix platform that aggregates the local storage (SSDs, HDDs) from all nodes into a single, cluster-wide storage pool. It presents this pool to the hypervisor (like AHV or ESXi) via standard protocols (iSCSI or NFS), making it appear as a centralized SAN, but with the benefits of data locality and distributed performance.

Nutanix Pulse is the telemetry service that, when enabled, automatically and securely sends system-level diagnostic information (like health status, system alerts, and configuration data) to Nutanix Support. This allows for proactive support, faster case resolution, and automated analysis of cluster health without manual intervention.

Categories in Prism Central provide a flexible way to logically group entities like VMs using a key-value pair system (e.g., Department: IT, Environment: Production). Once a VM is assigned to a category, policies for security (Flow), data protection, and image placement can be applied to the entire category, simplifying management at scale.

The first step in troubleshooting any NCC failure is to examine the detailed output for that specific check. The report will provide crucial information, such as which CVMs are experiencing high latency between each other and the measured values. This information is essential for diagnosing the root cause, which could be a physical switch misconfiguration, a bad cable, or a software issue.

For a node to be added to an existing cluster, its software versions must match. The Acropolis Operating System (AOS) and the hypervisor (e.g., AHV, ESXi) versions on the new nodes must be identical to those running on the cluster. Nutanix allows for heterogeneous hardware within a cluster, but the core software must be consistent.

Metro Availability provides a synchronous replication solution, which means that a write is not acknowledged to the guest VM until it has been committed to both the primary and secondary sites. This achieves a Recovery Point Objective (RPO) of zero. This solution requires a high-bandwidth, low-latency link (typically <5ms round-trip time), which is feasible with the described network connection.

This scenario is a prime use case for Prism Pro's automation feature, X-Play (now known as Playbooks). By creating a Playbook, the team can set a trigger based on performance anomalies like "VM Resources Constrained." The corresponding action can be to automatically add resources (e.g., +1 vCPU, +4 GB RAM) to the VM. This provides a dynamic, automated solution to scale resources up during peak demand and can be paired with another playbook to scale down, ensuring both performance and efficiency.

A Storage Pool is a logical grouping of the physical disks from the nodes within a single cluster. During cluster creation, Nutanix automatically creates one default Storage Pool that includes all available storage devices. While multiple storage pools can be created, this default behavior is standard.