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

For a customer using an ESXi cluster with two 10GbE NICs on each node and a vSphere Distributed Switch, the recommended load balancing configuration, following Nutanix Best Practices for redundancy and efficiency, is "Route based on IP hash." This setting allows for optimal utilization of network bandwidth and redundancy by distributing the traffic based on the IP address pairings, ensuring a balanced load across the physical NICs.References: Nutanix Bible, Nutanix University NCS-Core 6.8 learning materials

In a Nutanix environment managed by Prism Central, protecting workloads and SQL servers from a disaster involves creating a recovery policy. A recovery policy in Nutanix is a set of rules that define how data is protected and recovered in the event of a disaster1.

Creating a new recovery policy involves selecting the virtual machines (VMs) that need to be protected and specifying the hardware requirements for the recovery environment1. This includes the compute and storage resources needed to run the protected VMs in the recovery site1.

Once the recovery policy is created, Nutanix’s built-in data protection and disaster recovery capabilities can ensure that the protected VMs can be quickly and efficiently recovered in the event of a disaster2. This includes capabilities such as efficient snapshot, cloning, and replication capabilities to provide a higher level of protection at a lower cost2.

Therefore, to meet the CEO’s request, the IT administrator should create a new Recovery policy by selecting the VM that needs to be protected and get hardware requirements.

References:

Designing, Optimizing and Scaling Microsoft SQL Server - Nutanix

Nutanix Data Disaster Recovery - Protect Apps & Data | Nutanix

Recommendations For Leap And Supported Service-level … - Nutanix

Cloud Disaster Recovery Services | Nutanix

Nutanix – High Availability and Data Protection

The most straightforward approach for increasing security by disabling password authentication and moving to key-based SSH on a Nutanix cluster involves:

C. Enable Cluster Lockdown and provide an RSA key: Cluster Lockdown mode restricts management access to the cluster, ensuring that only key-based SSH authentication is used to access the CVM and AHV hosts, enhancing security by eliminating the use of passwords.

References:

Nutanix Bible (https://www.nutanixbible.com ), particularly sections discussing secure access and authentication methods.

Nutanix University: NCS-Core 6.8 Training (https://university.nutanix.com ), where security features like Cluster Lockdown are covered.

According to Nutanix best practices for network configuration, it is recommended to use either:

10G uplinks only: This provides sufficient bandwidth for typical data center operations.

25G uplinks only: This option is suitable for higher bandwidth requirements. Mixing uplinks with different speeds, such as 10G and 25G, is not recommended as it can lead to non-optimal performance and complexity in handling traffic.

References:

Nutanix Bible (https://www.nutanixbible.com ), specifically sections discussing network interface configurations.

Nutanix Network Administration Guide, which details best practices for network setup.

Ref: https://portal.nutanix.com/page/documents/details?targetId=Files-v3_6:fil-file-server-manage-c.html

To meet the requirements of maximizing storage space savings while optimizing I/O performance for business-critical applications and general server workloads, enabling both compression and erasure coding on the storage containers is recommended. Compression reduces the data footprint on storage disks, while erasure coding provides data redundancy in an efficient manner, which not only saves space but also enhances data durability and I/O performance for read-intensive applications.References:

Nutanix University - NCS-Core 6.8 Learning Path

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

When configuring network settings for a hypervisor or accessing local services hosted on it, the IP address must be reachable from the network configuration you are currently using. Given the generic nature of the options, the correct choice typically depends on the subnet used for management purposes, which often uses a standard private address. "192.168.5.254" is a common choice for local network configurations and is likely set up as the gateway or a primary network interface on the hypervisor.References:

Nutanix University - NCS-Core 6.8 Learning Path

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

When facing connectivity issues between the host workstation and the Foundation VM, ensuring proper network configuration is crucial. Removing and re-importing the Foundation VM can help reset any configuration issues, particularly ensuring that the virtual NIC is set to the correct mode, such as Host-Only, to facilitate direct communication with the host. Confirming the IP addresses and subnet masks ensures that both the host and the VM are on the same network segment, which is essential for successful communication. This step verifies that there are no IP configuration errors causing the connectivity issue.

References:

Nutanix Bible: Foundation VM Setup and Configuration

Nutanix University: Foundation VM Networking Configuration

When Foundation VM and a laptop can ping each other but nodes are not being discovered, it suggests a network protocol issue. The consultant should enable IPv6 and multicast on the switch. Multicast is required for node discovery in many environments, especially when using Nutanix Foundation, as it helps in the detection and communication between nodes and the Foundation VM.References:

Nutanix University - NCS-Core 6.8 Learning Path

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