QUESTION: 29

An administrator is troubleshooting vDisk performance issues in a Nutanix cluster with hybrid disks.
The VMs all have Flash Mode enabled.

But users are reporting disk latency.

What could cause the performance issues?

Flash mode is disabled when a node fails.
Compression is disabled on the vDisk storage container.
The VMs vDisks are in multiple containers.
Data size for flash mode exceeds 25% of the SSD capacity.

Answer(s): D

Explanation:

data size for flash mode exceeds 25% of the SSD capacity could cause the performance issues. Flash mode is a feature that allows vDisks to be pinned to SSDs for faster access, but it has a limit of 25% of the SSD capacity per node. If this limit is exceeded, some vDisks may be evicted from flash mode and cause disk latency.

Reveal Solution Next Question

QUESTION: 30

An administrator is performing validation testing of a new-deploy cluster. During this test, the administrator disconnect each LAN interface from each of the nodes while pinging the hypervisor and guest VMs.

When the first interface is disconnected, pings continue as expected to the hypervisor, but pings stop responding from the guest. Pings continue when the interface is reconnected.
When the second interface is disconnected, pings continue to both the hypervisor and guest VMs.

What could be the cause of this error?

This is normal behavior for a LAN Failover
Switch ports are configured with different VLANs
Portfast is not enabled on the switch ports
One of the network interfaces has a bad patch cable.

Answer(s): B

Explanation:

switch ports are configured with different VLANs could be the cause of this error. If the switch ports are not configured with the same VLANs as the network interfaces on each node, then there could be a mismatch in network connectivity when one interface is disconnected. This could affect the guest VMs that are using a different VLAN than the hypervisor.

Reveal Solution Next Question

QUESTION: 31

What is the minimum time a newly created Deduplication storage policy takes to apply to the VMs in the container?

5 Minutes
10 minutes
30 minutes
60 minutes

Answer(s): C

Explanation:

https://portal.nutanix.com/page/documents/details?targetId=Prism-Central-Guide- vpc_2023_3:mul-cluster-storage-policy-pc-c.html

Reveal Solution Next Question

QUESTION: 32

Refer to the exhibit.

An administrator is adding a new node to a cluster. The node has been imaged to the same versions of AHV and AOS that the cluster running, configured with appropriate IP addresses, and br0-up has been configured the same the existing uplink bonds

When attempting to add the node to the cluster with the Expand Cluster function in Prism , the cluster is unable to find the new node.

Based on the above output from the new node, what is most likely the cause of this issue?

The ports on the upstream switch are not configured for LACP.
The existing and the expansion node are on different VLANs.
There is a firewall blocking the discovery traffic from the tlu
LACP configuration must be completed after cluster expansion

Answer(s): B

Explanation:

The correct answer is B. The existing and the expansion node are on different VLANs.

The output shows that the new node has a br0-up bond with four interfaces: eth0, eth1, eth2, and eth. The bond is configured with LACP active and LACP fallback set to false. This means that the bond will only work if the upstream switch supports LACP and is configured to form an LACP group with the four interfaces. However, the output also shows that the bond has no IP address assigned to it, which indicates that the bond is not operational. One possible reason for this is that the existing and the expansion node are on different VLANs, and the upstream switch is not configured to allow the VLAN traffic on the LACP group. This would prevent the new node from communicating with the cluster and being discovered by the Expand Cluster function in Prism.

To verify this, the administrator can check the VLAN configuration on the upstream switch and compare it with the existing nodes. Alternatively, the administrator can use the "manage_ovs show_uplinks" command on an existing node and compare the output with the new node. If there is a VLAN mismatch, the administrator can either change the VLAN configuration on the switch or on the new node to match the existing nodes.

Reference:

Multicloud Infrastructure (NCP-MCI) v6.5 - Nutanix

Reveal Solution Next Question

Free NCP-MCI Exam Braindumps (page: 8)

QUESTION: 29

Explanation:

QUESTION: 30

Explanation:

QUESTION: 31

Explanation:

QUESTION: 32

Explanation:

Reference: