Free NCA 7.5 practice test: 30 questions with answers

Nutanix Move is the migration tool designed to move VMs from other hypervisors such as ESXi onto AHV. Nutanix Files provides SMB and NFS file services, Prism Central manages multiple clusters, and Nutanix Calm handles application blueprints, so none of those is the migration tool.

AHV is the built-in hypervisor based on KVM and is included with AOS, so it does not need a separate hypervisor purchase. The ESXi option is wrong because AHV is not VMware-based, the console option describes Prism Central, and the file services option describes Nutanix Files.

Nutanix Kubernetes Platform (NKP) is the Nutanix offering for running and managing Kubernetes clusters, including lifecycle tasks. Volumes, Objects and Data Lens are storage or data services and do not manage Kubernetes clusters.

Nutanix Volumes provides block storage through iSCSI, which suits LUNs for a Windows failover cluster. Files delivers SMB and NFS, Objects delivers S3 object storage, and Flow manages network security, so none of those presents iSCSI LUNs.

Nutanix Objects is an object storage service that exposes an S3-compatible API to applications. SMB and NFS are file protocols used by Nutanix Files, iSCSI LUNs come from Nutanix Volumes, and vSphere datastores are not an access method for Objects.

Flow network security (microsegmentation) lets administrators write policies based on VM categories, such as allowing only the application tier to reach the database tier on a given port. Health check schedules, migration plans and snapshot retention do not control which VMs can communicate.

Prism Element runs per cluster and manages that cluster, while Prism Central is an optional management layer that gives a single view across multiple registered clusters. Prism Central is not required on each node, Prism Element does not manage several clusters at once, and Prism Central does not replace AOS.

Nutanix Files serves file shares over SMB for Windows clients and NFS for Linux and UNIX clients. The S3 and Swift options are object APIs, iSCSI and Fibre Channel are block protocols, and HTTP and gRPC are not file-share protocols.

Nutanix Guest Tools (NGT) enables VSS-based application-consistent snapshots and file-level restore for guest VMs. Move is a migration appliance, a Prism Central plug-in does not add guest VSS support, and Foundation images nodes rather than guest VMs.

Live migration moves a running VM between hosts in the cluster without powering it off. Cold migration requires the VM to be shut down first, cloning creates a separate copy, and a snapshot restore reverts the VM's state rather than moving it.

In AHV, a virtual network mapped to a VLAN ID is what VM NICs attach to. A storage container is a storage construct, a protection domain groups VMs for data protection, and a category is a label, so none of them presents a VLAN to VMs.

Bonding combines physical uplinks so that traffic keeps flowing if one link fails, and it can spread traffic across the links depending on the bond mode. Bonding does not add storage capacity, has no link to vSphere DRS, and is unrelated to running AOS without AHV.

Erasure coding stores parity information instead of full extra copies, which lowers capacity overhead for cold data. Raising the replication factor adds copies and increases overhead, synchronous replication protects against site loss rather than saving space, and frequent snapshots consume more capacity.

A storage container is a logical partition of the storage pool that is presented to the hypervisor as a datastore for VM data. Boot devices, Objects backup targets and virtual switches are different constructs and do not describe containers.

Nutanix licensing is based on the cores in the cluster, so the entitlement must cover the added cores before the expansion. Switch brand, whether VMs are running, and the state of Prism Central are not licensing requirements for adding nodes.

A prepared image or template lets administrators deploy identical VMs quickly and consistently. Manual installs take longer and drift over time, live migration only moves an existing VM between hosts, and ISO exports do not produce deployable VMs.

A two-node cluster uses a witness VM as a tiebreaker so that quorum survives the failure of one node. A second Prism Central instance, an Objects bucket or a Move appliance does not provide quorum for the cluster's high availability.

A cluster with redundancy factor 3 needs at least five nodes so that the cluster metadata and configuration can keep three copies. Three or four nodes support only RF2, and a two-node cluster with a witness is a special RF2 design.

Nutanix Cloud Clusters (NC2) runs Nutanix clusters on AHV in public clouds, which allows the on-premises environment to be extended. Move, Files and Prism Element are not designed to host cloud-based Nutanix clusters.

AOS keeps redundant copies of data, so after a drive failure it re-replicates the affected data to the remaining disks to restore the configured replication factor. Losing the VMs, halting all I/O, or reusing the drive without protection are not how the cluster responds.

Maintenance mode evacuates running VMs from the host so the firmware and hardware work can happen without disrupting workloads. Deleting containers would destroy data, while disabling Prism Element or powering off Prism Central disrupts management without moving the VMs.

Life Cycle Manager (LCM) inventories and applies firmware and software updates for supported components across the cluster. Pulse sends telemetry, Foundation images nodes during deployment, and Move migrates workloads, so none of them performs this update role.

Cluster software upgrades are rolling, moving through nodes one at a time so that data and VMs remain available. Powering off every node, deleting containers, or using Move are not requirements for an AOS upgrade.

Nutanix Cluster Check (NCC) is the health check framework that runs a broad set of checks from the command line on a CVM. Life Cycle Manager tracks updates, Foundation images nodes, and Pulse sends telemetry, so none of them is the health check tool.

NCC reports configuration, hardware and service issues so administrators can fix them before they become outages. It does not create containers, migrate VMs or install hypervisor updates.

Alerts call attention to conditions that need action, while events are informational records of activities and changes that support auditing. The option that swaps the two definitions is the most tempting mistake.

The alert details identify the affected component, and the documented procedure lets the administrator replace the disk while protection is restored. Deleting a container, silencing alerts or snapshotting every VM does not fix the failed disk and can cause data or monitoring problems.

Pulse is the Nutanix telemetry feature that sends diagnostic information to Nutanix Support for proactive case handling. Calm, Era and Flow are used for application automation, database lifecycle and network security, so they are not telemetry features.

A log bundle is the standard diagnostic package that support engineers use to analyze intermittent cluster issues, and it is attached to the case. Sharing credentials and exporting VM disks are unsafe and do not provide the diagnostic data, and restarting Prism Central does not either.

High storage latency with low CPU use points to the storage path, so the VM and container IOPS and latency charts are the right place to start. CPU history alone cannot rule out a storage bottleneck, and display settings and license dates have no effect on VM response times.