Free Nutanix NCA-6.10 Practice Exam with Questions & Answers | Set: 2

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 uplink interfaces based on the source of the traffic, ensuring optimal usage of available network bandwidth without requiring LACP configuration on the physical switches.

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.

The correct answer isB. 1

Nutanix Prism Central provides the ability to create and manage support casesdirectly from the UI, but this functionality requiresat least one clusterto be registered to Prism Central. The Support option becomes active onceone or more clustersare managed.

Important distinctions:

Zero clusters(Option A): With no clusters registered, Prism Central is effectively disconnected from any environment and thus cannot associate logs or telemetry with a support case.

One cluster(Option B): Enables access to support features, including log bundle generation and direct case submission.

Options C and D (2 or 3 clusters) are incorrect; they arenot a requirementfor enabling support case functionality.

Prism Central UI Navigation Path:

Settings (gear icon) > Support > Create Support Case

Official Reference:

Nutanix Prism Central Guide – Support Integration Section

Excerpt: "To open a support case through Prism Central, ensure at least one cluster is registered. Support features become available once a cluster is connected."

Conclusion:Only one cluster is required to activate the support case workflow in Prism Central.

Answer: B

APriority 1 (P1)case guarantees an8-hour response timefor customers with Production Support. P1 cases are designated for critical issues that severely impact business operations or cause a complete system outage, requiring immediate attention from Nutanix Support.

Other priorities:

P2: High-impact issues but not critical, response time varies.

P3: Medium impact, typically non-urgent issues.

P4: Low priority, general inquiries or minor issues.

Nutanix Distributed Storage Fabric (DSF) provides storage access to an ESXi hypervisor using theNFS (Network File System)protocol. DSF abstracts the underlying storage hardware and exposes storage as an NFS datastore to ESXi hosts. This integration enables high performance, data protection, and scalability while simplifying storage management.

Other options:

LVM: Not used in Nutanix storage.

iSCSI: Used for specific use cases, not the default protocol for ESXi.

SMB: Not supported for ESXi environments.

TheData Protectionfeature in Prism Element provides built-in disaster recovery capabilities by enabling asynchronous replication between Nutanix clusters. With a latency of 30ms between the two sites, asynchronous replication can ensure that data is replicated efficiently while adhering to recovery point objectives (RPO). The administrator can configure Protection Domains and Replication Targets to set up DR between the clusters.

A. Recovery Plan:Incorrect, as Recovery Plans are part of Prism Central for orchestrated failover, not Prism Element.

B. Protection Policies:Incorrect, as these are defined under Prism Central.

C. Data Protection:Correct, as it enables disaster recovery via replication configurations in Prism Element.

D. Metro Cluster:Incorrect, as Metro Cluster requires low latency (<5ms) and is not suitable for a 30ms latency scenario.

In Nutanix Prism Element, thered heart iconat the top-right of the UI indicates that there is acritical alertaffecting the cluster's health. This icon is part of theAlert Monitoring System, and clicking on it redirects the user to theAlerts dashboard, where all current active alerts—including their severity, source, and recommended remediation steps—are listed.

What to do:

Navigate to theAlertssection.

Review allcritical alertsfor further diagnosis.

Cross-reference with theHealth dashboardif deeper system component checks are needed.

Clarification of Other Options:

A. Health:Summarizes system component states but does not provide detailed alert causes.

B. Tasks:Tracks user-initiated jobs, unrelated to fault diagnosis.

D. Analysis:Used for performance metrics and trends, not fault alerts.

Prism UI Navigation Path:

Click the red heart icon → Alerts Dashboard

Official Reference:

Nutanix Administration Guide – Alerts and Monitoring

Excerpt: “A red heart icon in Prism indicates a critical alert. Use the Alerts dashboard to identify and resolve the issue.”

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.

The correct answer isC. It must have the same hypervisor as the other nodes in the cluster.

When adding astorage-only (SO) nodeto a Nutanix cluster:

It mustrun the same hypervisoras the existing nodes.

The SO node doesnot host VMsbut participates in thestorage layerto increase capacity and performance.

Nutanix currentlydoes not support mixed hypervisors(e.g., combining AHV with ESXi) within the same cluster, even for storage-only nodes.

Clarifications:

A & B:Neither Nutanix Files nor Objects are required for adding storage-only nodes.

D:Cross-hypervisor configuration is unsupported at the cluster level.

Official Reference:

Nutanix Hardware Administration Guide – Storage-Only Node Requirements

Excerpt: “All nodes in a cluster, including storage-only nodes, must run the same hypervisor type.”

Answer: C

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.