Nutanix Updated NCS-Core Exam Questions and Answers by lili

When encountering an error related to unsupported ISO media during the imaging process, and the ISO version is not listed in the whitelist file, the consultant should take several steps to resolve the issue. Replacing and saving the whitelist file in Foundation ensures that the latest compatibility data is used. Downloading the iso_whitelist.json from the Support portal provides the most recent and comprehensive list of supported ISO versions. Editing the whitelist file in Foundation allows the consultant to manually add or update entries to include the ISO in question, ensuring the imaging process can proceed.

References:

• Nutanix Bible: Foundation Imaging and Compatibility
• Nutanix University: Handling Foundation Errors

When receiving a field advisory from Nutanix support regarding a rare problem that could destabilize the cluster, the recommended action is to update AOS. This can be done via Prism Element by selecting "Upgrade Software." This method ensures that any patches or updates that address the identified issue are applied directly to the AOS environment, mitigating any potential risks associated with the reported problem. Since the organization uses VMware vSphere, the update specifically targets the AOS to ensure the underlying infrastructure supporting vSphere remains stable.References: Nutanix Support Portal, Nutanix Field Advisories, Prism Element Guide.

In environments where IPv6 is not allowed for node discovery and the use of an external flat switch by the consultant is also restricted, the viable approach is to connect to the top of rack switch and discover the nodes using IPv4. This method aligns with the customer’s networking policies and leverages the existing network infrastructure to facilitate the discovery and configuration of the nodes within the Nutanix cluster.References: Nutanix Bible, Nutanix University NCS-Core 6.8 resources, and Nutanix official guidelines on node discovery using IPv4.

In Nutanix, a cluster with RF2 (Redundancy Factor 2) can tolerate the failure of a single node or drive1. However, to ensure that the cluster can survive a complete rack failure without negatively affecting workload performance, we need to consider rack awareness. When rack fault tolerance is enabled, the cluster has rack awareness and the guest VMs can continue to run with failure of one rack (RF2) or two racks (RF3). The redundant copies of guest VM data and metadata exist on other racks when one rack fails2.

Given the current cluster configuration (30 nodes distributed 10 nodes per rack across three 42U racks), adding 3 additional nodes per rack (9 nodes total) would increase the redundancy of the cluster and improve its ability to withstand a complete rack failure. This is because the additional nodes would provide more storage capacity and compute resources, allowing the cluster to continue running workloads even if one rack fails.

References:

• Understanding Fault Domains and Rack Awareness | Nutanix Community
• RF2 -> RF3 | Requirements | Nutanix Community