Pass the Nutanix NCS Professional NCS-Core Questions and answers with ValidTests

Ref: https://next.nutanix.com/how-it-works-22/rf2-rf3-requirements-37206#:~:text=Controller%20VMs%20must%20be%20configured,for%20the%20feature)%20of%20memory .

To meet the customer requirements for automatic failover and resource balancing in a vSphere environment, two specific features need to be enabled: vSphere High Availability (HA) and Distributed Resource Scheduler (DRS). vSphere HA ensures that VMs automatically restart on other hosts in the event of a host failure, providing high availability. vSphere DRS balances computing workloads with available resources in a vSphere environment, ensuring that resources are used efficiently and that new VMs are placed on hosts with the most available resources.

References:

Nutanix Bible: vSphere Integration

Nutanix University: Configuring vSphere Features

For a customer with 12 Nutanix blocks distributed across three racks and an additional datacenter 400 kilometers away, achieving the highest level of resiliency involves ensuring both local and remote data protection.

Option B, "Async DR to a remote site," is essential for protecting against site failures by asynchronously replicating data to a branch office. This method is suitable for long-distance replication where latency and bandwidth are concerns.

Option C, "Rack awareness," is crucial in a multi-rack setup to ensure that data is distributed in such a way that a failure of a single rack does not lead to data loss or significant downtime. Rack awareness configures the placement of data replicas across different racks, improving fault tolerance within the primary datacenter.

References:Nutanix documentation on disaster recovery and data resilience strategies, such as those found in the Nutanix Bible and official Nutanix training materials, supports these recommendations, emphasizing the importance of both remote site replication and local redundancy configurations.

To execute the command manage_ovs --bridge_name br0 show_uplinks in a Nutanix cluster, the appropriate prompt is:

A. nutanix@CVM-$: This command is intended for execution within the Controller Virtual Machine (CVM) environment, and "nutanix@CVM-$" is the standard user prompt in the CVM where such network commands are run.

References:

Nutanix Bible (https://www.nutanixbible.com ), especially sections on managing virtual bridges and networking commands.

Nutanix University: NCS-Core 6.8 Training (https://university.nutanix.com ), which includes details on command-line operations within the CVM.

The customer's requirements for automatic failover and resource balancing in a new Hyper-V cluster can be met with the use of Failover Clustering and High Availability. Failover Clustering allows VMs to automatically failover to another host in the event of a host failure, fulfilling the requirement for resilience. High Availability ensures that VMs restart on available hardware in the cluster, maintaining service continuity and balancing CPU and memory resources across the hosts.References: Microsoft Hyper-V documentation, Nutanix Bible, and NCS-Core 6.8 course materials on virtualization platforms.

ref: https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v510:upg-hypervisor-upgrade-esxi-c. html

For troubleshooting issues with Foundation Portable on Mac not locating new nodes, the consultant should check the ~/data/logs/foundation.out log. This log file contains detailed operational entries that describe the activities of the Foundation tool, including any errors encountered during the node discovery process. This can provide insights into why the nodes are not being detected and guide the consultant on the necessary corrective actions.

References:

Nutanix Bible: Foundation Deployment and Troubleshooting

Nutanix University: Foundation Tool Usage

When using active-backup bonding, failover delay can occur due to Spanning Tree Protocol (STP) reconvergence. STP places ports in a learning and listening state before forwarding traffic, causing packet loss during failover.

To minimize failover time, Spanning-tree PortFast should be enabled on the switch ports connected to the Nutanix hosts. PortFast immediately transitions ports to the forwarding state, avoiding the default 30-50 second delay caused by STP reconvergence.

Jumbo frames (A) only optimize network performance by allowing larger packet sizes but do not impact failover speed.

PAGP (B) is a Cisco-specific link aggregation protocol and is not applicable to Nutanix AHV bonding.

LACP on switch (C) is used for link aggregation, which is not relevant here as the default mode is active-backup, not LACP-based bonding.

Ref:

rx_crc_errors are caused either by faults in layer 1 (in the past, we have seen failed twinax cables and incorrect types of fibre being used), or issues with jumbo frames on the network. In an environment with 10 Gig switches that use cut-through forwarding (Cisco Nexus, Arista, Cisco devices using IOS default to Store and Forward switching), any packets that come into the switch will get forwarded out the destination interface once the switch has read the destination MAC address. If that packet has an MTU over what is configured on the interface, it will cut off the packet at the designated MTU, causing the server to receive a malformed packet, which will throw a CRC error.

If you have a layer 1 issue, you will see rx_crc_errors, not on all but one or two nodes.