Free NCS-CORE Practice Test

To survive the concurrent loss of two nodes, the cluster's storage must be configured with Replication Factor 3 (RF3), which maintains three copies of all data. This ensures data availability if two nodes fail. For compute resource availability in an ESXi environment, VMware High Availability (HA) admission control must be configured to reserve sufficient resources for restarting the failed nodes' VMs. In a 20-node cluster, the loss of two nodes represents 10% of the total cluster resources (2 / 20 = 0.10). Therefore, HA admission control should be set to reserve 10% of the cluster's CPU and memory resources to guarantee successful VM failovers.

B. This option uses RF2, which can only tolerate a single node failure, and reserves insufficient HA resources (5%) for a two-node failure scenario.
C. While this option correctly specifies RF3, the HA admission control of 5% is insufficient, as it would only reserve enough resources to handle the failure of one node (1/20).
D. This option uses RF2, which cannot tolerate the failure of two nodes concurrently, making the HA setting irrelevant for the customer's requirement.

1. Nutanix. (2023). vSphere Administration Guide for AOS 6.7. Section: Configuring High Availability and DRS. "To tolerate n host failures, set the Percentage of Cluster Resources Reserved policy to (n / totalhosts) 100. For 2 failures in a 20-node cluster, this is 10%."

2. Nutanix. (2023). Prism Web Console Guide v6.7. Section: Updating Cluster Details. "To ensure availability after two simultaneous node failures, the cluster must be configured with redundancy factor 3."

3. Nutanix Bible. (2023). Section: Data Protection - Replication Factor. "Replication Factor 3 (RF3) provides the ability to tolerate up to two simultaneous component (e.g., node or disk) failures."

The Nutanix Support Portal organizes documentation by category. Information about the physical layout of hardware, including port locations, is essential for maintenance and replacement tasks. Therefore, documents detailing component replacement procedures are the correct source. These guides contain detailed diagrams of the front and rear panels of each node type, explicitly identifying the location of all ports, including the dedicated and shared IPMI ports. This ensures technicians can correctly identify physical connections for installation or troubleshooting.

A. Solutions Documentation: This focuses on software solutions (like VDI or databases) running on Nutanix, not the physical hardware layout.
C. Software Documentation: This covers software products like AOS and Prism and does not contain detailed hardware diagrams or port locations.
D. Knowledge Base: While a specific article might exist, it is not the primary, structured source for hardware specifications; hardware guides are.

1. Nutanix Support Portal, Documentation > Hardware > Hardware Replacement Documentation. (e.g., "NX-8155-G7 Component Replacement" guide, Section: "Replacing the Motherboard", includes detailed diagrams of rear panel ports).

2. Nutanix University, Nutanix Hybrid Cloud Fundamentals course, Module: "Nutanix Hardware Platforms". This module describes the physical characteristics of nodes, and directs students to the hardware-specific documentation for detailed layouts.

A Nutanix cluster is composed of nodes, and each node runs a Controller VM (CVM). For a node to be discovered, imaged by Foundation, and participate in the cluster, its CVM must have a unique IP address on the management network. This IP address is the fundamental requirement for all internode communication, cluster services, and management. While a cluster name is also required during the creation process, the CVM IP is a prerequisite for the node's basic network connectivity, making it the most critical hard requirement.

A. Nutanix cluster name: While required to create the cluster, it's a logical identifier applied after the nodes are already communicating via their CVM IPs.
B. Cluster Virtual IP: This is a highly recommended best practice for management high availability but is an optional configuration during cluster creation.
C. Motion IP address: This is not a standard Nutanix term. The CVM and hypervisor communicate over a private, internal network, not a "Motion IP."

1. Nutanix University. (2023). Nutanix Hybrid Cloud Fundamentals Course. Section: Cluster Architecture. The courseware explains that each CVM requires an IP address to form the storage fabric and communicate with other nodes.

2. Nutanix. (2023). Field Installation Guide. Version 5.5. Section: "Information to Collect Before You Begin". This guide lists the CVM IP address, Hypervisor IP address, and IPMI IP address as mandatory information required for each node before starting Foundation.

3. Nutanix Prism Element Web Console Guide. (2023). Section: "Creating a Cluster". The cluster creation wizard in Foundation explicitly requires an IP address to be assigned to each CVM.

--- QUESTION #185 --- A customer is running out of storage in an ESXi cluster. The customer wants to add storage without paying for an additional hypervisor license. Which option should the consultant recommend to meet the requirement?

A. Convert the cluster to AHV to support storage-only node requirements.
B. Select the storage-only checkbox during Foundation and then expand the cluster in Prism.
C. Buy a new node to meet the requirements of the storage-only node specifications.
D. Edit the factoryconfig.json file to configure the node as storage-only and then expand the cluster in Prism
Answer: A Correct Answer: A

Explanation: Storage-only nodes added to an ESXi cluster still require a valid VMware vSphere license. The only way to add a storage-only node to a Nutanix cluster without incurring an additional hypervisor license cost is to use the license-free Nutanix AHV hypervisor. Since a Nutanix cluster cannot have mixed hypervisors (e.g., ESXi and AHV), the entire cluster must be converted to AHV. This meets the strict requirement of adding storage without paying for another hypervisor license.

Why Incorrect Options are Wrong: B: This correctly describes how to image a storage-only node, but it does not solve the ESXi licensing requirement for that new node.

C: Buying a new node is a necessary step but does not address the core problem of avoiding the hypervisor license cost.

D: Manually editing factoryconfig.json is an unsupported and incorrect method for configuring a node's role.

References:
1. Nutanix Prism Web Console Guide v6.5, "Hardware Management" section, subsection "Adding a Storage-Only Node to a Cluster". It states, "For ESXi clusters, a vSphere license is required for a storage-only node."
2. Nutanix University - Nutanix Cluster Administration (NCA) v6.5, Module "Cluster and Node Management". The courseware clarifies that storage-only nodes participate in the storage tier but do not run guest VMs, and licensing depends on the underlying hypervisor.

When a vSphere High Availability (HA) advanced setting, such as das.ignoreInsufficientHbDatastore, is modified, the change is not applied dynamically. The vSphere HA service, which runs on each ESXi host in the cluster, must be reconfigured to read and apply the new setting. The standard administrative procedure to force this reconfiguration is to disable HA on the vCenter cluster object and then immediately re-enable it. This action pushes the updated configuration, including the new advanced setting, to all hosts in the cluster, which should then clear the alert.

B. Make sure the DRS setting is turned on: DRS is for workload balancing and is a separate feature from HA. Enabling it will not re-read or apply changes made to HA advanced settings.
C. Create a second container: This would resolve the underlying HA warning but directly violates the customer's requirement to have only a single datastore. The goal is to suppress the warning, not re-architect.
D. Whitelist the vCenter IP address within Prism: This is a Nutanix security feature for API access control and has no interaction with or influence on the internal operations of VMware's vSphere HA feature.

1. Nutanix, vSphere Administration Guide for AOS 6.5, Section: "Creating a vSphere HA Cluster", Sub-section: "Configuration". The guide notes that for single datastore configurations, das.ignoreInsufficientHbDatastore should be set, and implies that HA must be configured for this to take effect. The standard procedure for re-reading such settings is to toggle the service.

2. VMware, vSphere Availability Guide (vSphere 8), Chapter 4: "vSphere HA Cluster Settings". This document details that changes to advanced options require HA to be reconfigured on the hosts, which is accomplished by turning the feature off and on.

Network Visualization in Nutanix requires both LLDP (Link Layer Discovery Protocol) and SNMP (Simple Network Management Protocol) to be properly configured. While LLDP enables the discovery of directly connected devices and their capabilities, SNMP is essential for retrieving detailed switch information, port configurations, and network topology data. Without proper SNMP configuration (including community strings, access permissions, and network connectivity), the cluster cannot query and display comprehensive switch information even when LLDP is functioning.

A. ISL configuration affects inter-switch communication, not cluster-to-switch visibility for Network Visualization.

C. br0 and br1 are default bridges in AHV; their absence would cause broader networking issues beyond visualization.

D. RDMA-enabled NICs don't prevent Network Visualization from displaying switch information when properly configured.

1. Nutanix AHV Administration Guide v6.5 - Network Management section, pages 89-92

2. Nutanix Best Practices Guide - Network Configuration chapter, section 4.3

3. Nutanix Port Reference Guide - SNMP requirements, page 15

4. Nutanix Knowledge Base Article KB-7892 - Network Visualization Requirements

5. Nutanix Security Guide v6.5 - SNMP Configuration section, pages 134-136

The issue is a VLAN configuration mismatch. The customer's switch is configured to use VLAN 23 as the native VLAN, which means it expects traffic for this VLAN to be untagged. The consultant incorrectly configured the host and CVM to tag traffic for VLAN 23. When the tagged frames from the Nutanix node arrive at the switch port, the switch, expecting untagged frames for its native VLAN, will likely drop them, causing a loss of connectivity. The host and CVM network configuration must match the switch port configuration.

A. LACP fallback would allow a non-LACP device to connect; it does not cause a connectivity failure when LACP is configured on both ends, and it is not the root cause here.
B. A vSphere Distributed Switch (vDS) is not a prerequisite for basic network connectivity or LACP; this can be configured on a standard vSwitch.
C. "Route based on IP hash" is the correct load balancing policy for LACP, but the fundamental VLAN tagging mismatch would prevent connectivity before this policy even matters.

1. Nutanix University. (2023). Nutanix Hybrid Cloud Fundamentals Course. Section: Networking. "When configuring VLANs, the settings on the Nutanix host's virtual switch must match the physical switch port configuration. If a switch port is configured with a native VLAN, the corresponding virtual switch port group should not have a VLAN ID assigned (or be set to 0 for an access port)."

2. VMware vSphere Documentation. (2023). ESXi and vCenter Server Documentation. Section: vSphere Networking, "VLAN Configuration". "A native VLAN ID on a trunk port is untagged. If the ESXi host vSwitch port group is configured with a VLAN ID that matches the native VLAN, the host will tag the frames, causing the switch to drop them."

3. Nutanix. (2023). AHV Best Practices Guide. Section: Network Switch Configuration. "Ensure that the VLAN configuration on the host matches the physical switch. A common misconfiguration is tagging a VLAN on the host that the switch expects to be untagged (as a native VLAN)."

--- QUESTION #181 --- Correct Answer: A
Explanation: The Nutanix Foundation discovery process relies on IPv6 link-local multicast messages to find new, unconfigured nodes on the same Layer 2 network. The nodes broadcast their presence, and the Foundation VM listens for these broadcasts. If the switch connecting the nodes and the Foundation VM does not have IPv6 enabled or is configured to block IPv6 multicast traffic (e.g., via MLD snooping without a querier), the Foundation VM will never receive the discovery packets, and the nodes will not appear. Why Incorrect Options are Wrong:
B. IPMI port is not plugged in: IPMI is used for power management and the imaging process itself, but initial node discovery occurs over the 10GbE data ports.

C. Foundation VM is running on a Windows host: The Foundation Applet and VM are supported on Windows, macOS, and Linux; the host OS is not the cause.

D. 10GbE ports are configured with the incorrect duplex setting: 10GbE interfaces typically auto-negotiate correctly, and a duplex mismatch is highly unlikely to cause a complete failure of IPv6 multicast discovery.
References: Nutanix Field Installation Guide v4.5, "Network Requirements", Page 10. It states, "Foundation uses IPv6 link-local discovery to find unconfigured Nutanix nodes in the same broadcast domain... Ensure that your network switches allow IPv6 multicast traffic between the Foundation VM and the nodes to be imaged." Nutanix University, "Nutanix Hybrid Cloud Fundamentals" courseware, Module "Installing Nutanix Software". The module describes the node discovery process as being dependent on IPv6 link-local addressing.

Nutanix clusters require IP addresses for various components including CVMs, hypervisor management, and cluster virtual IPs. When deploying in an environment using the common 192.168.x.x range, there's a risk of IP address conflicts between the new cluster components and existing infrastructure. The consultant must verify that all IP addresses allocated for the Nutanix deployment don't conflict with existing devices on the customer's network, including these DNS servers and any other systems in the 192.168.5.0/24 subnet.

A. Not everything is accounted for - IP conflict verification is still needed.

B. Internal Nutanix networking uses link-local addresses and won't interfere with installation completion.

C. CVMs don't need a separate network; they just need non-conflicting IPs on the existing network.

1. Nutanix Bible - Network Design section, specifically IP addressing requirements

2. Nutanix Installation Guide (AOS 6.x) - Pre-installation network requirements chapter

3. Nutanix Best Practices Guide - Network Planning section on IP allocation

4. Official Nutanix Documentation Portal - Foundation deployment prerequisites

5. Nutanix University courseware - NCS Core module on cluster deployment planning

The scenario describes a layer 2 connectivity issue on a single subnet. The key information is that the network is configured "without VLAN tagging." This means the hypervisor and CVM are sending untagged Ethernet frames. If the physical switch port they connect to is configured as a trunk port (which expects tagged frames for specific VLANs), it will handle untagged traffic according to its "native VLAN" setting. If the native VLAN is not the VLAN associated with the 10.3.12.0/24 subnet, the untagged frames from the host will be placed in the wrong network segment, breaking communication.

A. The 1GbE and 10GbE NICs have not been separated: Mixing NIC speeds is a performance and best practice issue; it does not typically prevent basic IP ping connectivity on a correctly configured network.
B. The default gateway is incorrect: A default gateway is used for routing traffic between different subnets. It is not involved in communication between two devices on the same subnet.
D. The CVM/hypervisor only communicates over 192.168.5.0/24: This is false. The 192.168.5.0/24 network is a private backplane for internal services, but all external communication uses the configured external IP addresses.

1. Nutanix, AHV Networking Best Practices Guide, "VLAN Configuration" section. This guide details the proper configuration of switch ports for AHV hosts, explaining the difference between access ports (for untagged traffic) and trunk ports (for tagged traffic) and the concept of a native VLAN.

2. Nutanix University, Nutanix Hybrid Cloud Fundamentals Course, "Module 4: Networking," Section: Acropolis Networking Overview. This section covers the interaction between the AHV host's virtual switch and the physical network infrastructure, including VLANs.