NCS-CORE Practice Questions

To ensure additional resiliency in a 20-node ESXi deployment capable of surviving the concurrent loss

of two nodes, the consultant should configure the system with a storage reservation and HA (High

Availability) admission control each set to 5%, combined with a cluster redundancy factor (RF) of 3.

RF3 provides the capability to tolerate the failure of up to two nodes without data loss, thus

enhancing the cluster's resilience. This configuration is optimal for maintaining cluster availability

and integrity during multiple node failures.

Reference: Nutanix Bible, Nutanix University

When looking for documents that identify specific ports such as the Shared IPMI port on nodes, the

best location within the Nutanix Support Portal is the Hardware Replacement Documentation. This

section specifically deals with physical components and their configurations, making it the most

appropriate resource for identifying physical port locations and specifications related to specific

Nutanix hardware models.

Reference: Nutanix Support Portal, Nutanix Bible, and NCS-Core 6.8 materials specifically mentioning

hardware documentation.

The CVM IP address is a hard requirement for deploying a Nutanix cluster. Each CVM must have a

unique IP address assigned to it as this IP address is critical for cluster operations, including data

replication, management activities, and communication between CVMs and hypervisors. The other

options, while important for various functionalities, do not represent a hard requirement for initial

deployment.

Reference:

Nutanix University - NCS-Core 6.8 Learning Path

The Nutanix Bible, Cluster Configuration chapter (https://www.nutanixbible.com/)

When a customer needs to add storage to an ESXi cluster without incurring additional hypervisor

licensing costs, converting the cluster to Nutanix AHV presents a viable solution. AHV allows the

incorporation of storage-only nodes, which can extend the cluster's storage capacity without

necessitating additional licenses for hypervisor usage.

Reference:

Nutanix Solutions for ESXi to AHV Migration: Nutanix Documentation

Nutanix AHV Licensing and Features Guide: Nutanix Licensing Information

The alert regarding the heartbeat datastore in vCenter, despite setting

das.ignoreInsufficientHbDatastore to true, suggests that HA has not acknowledged the updated

configuration. The effective solution is to restart HA on the cluster, which involves turning off HA and

then turning it back on. This reset will allow vCenter to re-evaluate the datastore configuration and

recognize that the insufficient heartbeat datastore alert should be suppressed as per the updated

setting.

Reference:

VMware Documentation on HA Configuration: VMware Support

Nutanix and VMware Integration Guide: Nutanix Documentation

ref: https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prismv55:wc-network-visualization-intro-c.html

In this scenario, the connectivity issue arises because the VLAN settings require a specific

configuration on the vSwitch settings when using LACP. When using LACP for load balancing network

traffic, the vSwitch or Distributed Switch must be configured with the "Route based on IP hash" load

balancing algorithm. This setting is necessary to properly distribute the traffic across the LACP

bonded links. Not selecting this setting in vSwitch0 settings would result in improper handling of

network packets over the LACP bonded links, thereby causing the hosts and CVMs to be unreachable.

Adjusting the vSwitch settings to "Route based on IP hash" should resolve the connectivity issue.

Reference: VMware vSphere Networking documentation, Nutanix Bible LACP configuration

guidelines.

The failure to discover nodes during installation can often be attributed to the lack of IPv6 support on

the network, especially if the Foundation process relies on IPv6 for node discovery. If IPv6 is not

enabled on the customer’s switch, the discovery packets may not be properly routed, resulting in the

nodes not being discovered. Enabling IPv6 on the switch could resolve this discovery issue.

Reference:

Nutanix Foundation Troubleshooting Guide: Nutanix Support Portal

Network Configuration and Troubleshooting Documentation

Noticing a potential typo or error in the DNS server IP address notation:

D . New IPs provided should be verified to not conflict with the customer's network: It's crucial to

verify the accuracy and validity of the IP addresses provided, ensuring there are no typos and that

the IPs do not conflict with existing network configurations. The noted IP '192.1685.20' appears to be

incorrectly formatted and should be corrected and validated.

Reference:

Nutanix Bible (https://www.nutanixbible.com), where network preparation and IP address

configuration are covered.

Nutanix University: NCS-Core 6.8 Training (https://university.nutanix.com), which discusses network

planning and verification in cluster deployments.

If a consultant is unable to ping the CVM from the hypervisor using the external interface in a

network without VLAN tagging, and both are using the same subnet, the issue might be related to an

incorrect default gateway configuration. The default gateway must be correctly set to ensure proper

routing of packets between the CVM and the hypervisor. An incorrect gateway can prevent successful

communication even if both devices are on the same subnet.

Reference:

Nutanix University - NCS-Core 6.8 Learning Path

The Nutanix Bible, Networking chapter (https://www.nutanixbible.com/)