Free Nutanix NCP-MCI-6.5 Practice Exam with Questions & Answers

The critical alerts listed are indicating that the default passwords are still in use for IPMI, the host, and the Controller Virtual Machine (CVM). This suggests that the passwords for these components were not changed from the default during the initial cluster configuration and deployment process, which is a critical security practice.

A. CVM password changes: The alert for the CVM using the default password indicates that the CVM password has not been changed. It is a standard security measure to change default passwords to prevent unauthorized access.

C. Host password changes: Similarly, the alert for the host using the default password indicates that the default password for the host has not been updated. This applies to the passwords used to access the hypervisor host directly.

Changing default passwords is a critical step in securing the Nutanix environment. This is highlighted in Nutanix's best practices and security guidelines, which recommend changing default passwords as part of the initial configuration to ensure that the environment is not left vulnerable to unauthorized access due to known default credentials. This process is typically part of the initial setup procedures outlined in the Nutanix documentation for cluster deployment and security configuration.

The IPMI alert also points to the need for changing default passwords, but since IPMI (Intelligent Platform Management Interface) is not specifically mentioned in the provided options, it falls under the broader category of host-level password changes, which would be covered by option C.

BIOS password changes (Option B) and Password policy changes (Option D) are also important but were not directly flagged by the alerts mentioned. BIOS password changes are usually a separate task and not indicated by the alerts given, while password policy changes are related to the policies governing password complexity and rotation rather than the initial password setup.

http://www.vstellar.com/2019/01/10/ahv-networking-part-1 -basics/#:~:text=AHV%20Network%20Architecture&text=virbr0%20is%20an%20internal%20switch,virbr0)%20have%20IP%20address%20192.168.

A native VLAN is a VLAN that is assigned to untagged traffic on a trunk port of a switch. A trunk port can carry traffic from multiple VLANs, but it needs to have a native VLAN to handle traffic that does not have a VLAN tag. The native VLAN is usually VLAN 1 by default on most switches, but it can be changed to any other VLAN number2. When creating a network profile on Nutanix, the administrator needs to specify the VLAN ID that matches the VLAN configuration on the physical switch. However, if the network profile uses the same VLAN ID as the native VLAN on the switch, it will cause network connectivity issues for the VMs connected to that network profile. This is because Nutanix AHV uses 802.1Q tagging for all network traffic, including traffic in the native VLAN. The switch will expect untagged traffic in the native VLAN and will drop any tagged traffic in that VLAN3. To fix this issue, the administrator needs to change the VLAN field from vlan. 1 to vlan. 0 in the network profile on Nutanix. This will tell Nutanix AHV to send untagged traffic for that network profile and match the native VLAN configuration on the switch4.

According to the Nutanix Support & Insights, in a two-node ROBO cluster with a witness VM, if one node goes down, the other node sends a leadership request to the witness VM and goes into single-node mode. The cluster remains available and can tolerate another failure of either the witness VM or the network link.

According to the Network File System web search result3, NFS (Network File System) is a distributed file system protocol that allows a user on a client computer to access files over a network in a manner similar to how local storage is accessed. NFS is one of the access protocols supported by Files. According to the [MS-WPO]: File Access Services Protocols web search result4, SMB (Server Message Block) is a Windows file sharing protocol that enables applications to discover, access, and share files that are hosted on or made available by a file server, using a network between them, in a secure and managed environment. SMB is another access protocol supported by Files. Therefore, SMB and NFS are two access protocols supported by Files.

The correct answer is C. Network latency.

The diagram shows a solution that uses synchronous replication between two remote protection domains, cluster site A and cluster site B. Synchronous replication is a feature that allows near-zero RPO (recovery point objective) by replicating data to the remote site before acknowledging writes to the local site. However, synchronous replication has some requirements and limitations that must be met for it to work properly. One of these requirements is that the network latency between the two sites must be less than or equal to 5 ms1. If the network latency is higher than 5 ms, the synchronous replication will fail and the protection policy will be suspended2.

Therefore, based on the diagram, the most likely cause of the issue is that the network latency between cluster site A and cluster site B is higher than 5 ms, which prevents the synchronous replication from working. To verify this, the administrator can use the “ncli cluster ping” command to measure the network latency between the two sites3. If the network latency is indeed higher than 5 ms, the administrator can either improve the network performance or switch to a different replication mode, such as near-synchronous or asynchronous.

 When a node with Erasure Coding fails, the cluster will automatically rebuild the missing data using replication factor (RF) 2 or 3, depending on the cluster configuration. This means that the data that was previously stored using Erasure Coding will now be stored using full copies, which may increase the amount of data stored in the SSD tier1.