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

To troubleshoot physical network mis-cabling without physical access to the data center and connected to Cisco Nexus 9k switches, the appropriate command to run from the Nutanix AHV host is lldpctl. This command allows the consultant to view the Link Layer Discovery Protocol (LLDP) information about directly connected devices. LLDP is supported on Nexus switches and provides detailed network topology information, which is crucial for identifying how the AHV nodes are connected to the switches, and to verify correct physical connections.References: Nutanix Command Reference Guide, Cisco Nexus 9000 Series documentation.

Ref: https://kb.vmware.com/s/article/1009465

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.

Given the reported RX errors on eth2 and the intermittent ping loss as observed from the CVM logs, the best initial troubleshooting step that avoids VM disruption is to inspect the switch port for errors. Option C, "Check the port on the switch side for any errors," is the most direct and non-invasive approach to determining if the issue lies with the network infrastructure rather than the server hardware itself or the configuration.

This action helps identify whether the problem is related to the physical connection (e.g., port issues, switch configuration errors) without altering the current active network setup on the Nutanix node. If errors are found on the switch port, adjustments or repairs can be made accordingly, potentially resolving the RX errors without impacting the running VMs.

References:This recommendation follows Nutanix's best practices for network troubleshooting, focusing first on external network components before altering host configurations.

Before expanding the cluster with the new NX-3235-G9 block, it is critical to ensure that all components are running supported and recommended versions due to compatibility and support issues. Therefore, the necessary actions include: A. Upgrade vCenter, AOS, and ESXi to supported and recommended versions. This step ensures compatibility across all components, particularly important as the new G9 hardware does not support the currently installed version of ESXi. Upgrading these components will also ensure continued vendor support and the stability of the environment. Options B, C, and D do not adequately address the need for vCenter upgrades or the fact that ESXi 6.7 U3b is unsupported for G9, highlighting the necessity for a comprehensive upgrade.References: Nutanix Hardware Compatibility List, Nutanix Support Portal.

Ref: https://next.nutanix.com/server-virtualization-27/iops-latency-issue-1 168

The make and model of the systems should be verified during the Tech Review Call. This step is essential to ensure that all necessary information is collected and verified before any physical interaction with the hardware. Verifying these details during the call helps in preparing adequately for the cluster deployment, allowing the consultant to anticipate and mitigate any compatibility or configuration issues before arriving onsite.References: Nutanix Foundation Guide, Pre-installation Checklist Documents.

Given that the customer’s security policy prohibits connecting a consultant’s laptop within the corporate datacenter, the consultant can complete the deployment using: A. The Controller VM-based Foundation process, which allows the consultant to configure and deploy the cluster using the software tools provided within the Controller VM itself. This method does not require direct laptop connection to the network. C. Run the Network Crashcart Script to manually configure IP addresses on the hosts and then proceed to create the cluster manually. This approach involves using available scripts and utilities that can be executed from within the data center's management interfaces without needing direct laptop access. Options B and D would typically require direct network connection capabilities not permissible under the security constraints.References: Nutanix Foundation Documentation, Nutanix Deployment Best Practices.

https://portal.nutanix.com/page/documents/details?targetId=Prism-Central-Guide-Prism-v510:mul-security-policy-management-pc-c.html