QUESTION: 33

Refer to the exhibit.

An administrator is trying to implement the solution that is shown in the exhibit, but has been unsuccessful.

Based on the diagram, what is causing the issue?

A remote Witness VM
Active containers in both sites
Network latency
Unsupported hypervisor

Answer(s): C

Explanation:

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 ms. If the network latency is higher than 5 ms, the synchronous replication will fail and the protection policy will be suspended.

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 sites. 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.

Reference:

Synchronous Replication Requirements

Reveal Solution Next Question

QUESTION: 34

The administrator recently had a node fail in an AHV Nutanix cluster. All of the VMs restarted on other nodes in the cluster, but they discovered that the VMs that make up a SQL cluster were running on the failed host. The administrator has been asked to take measures to prevent a SQL outage in the future.

What affinity option will prevent the SQL VMs from running on the same hos?

VM-VM anti-Affinity policy
Create Affinity Category
VM-Most Affinity policy
Create Affinity Project

Answer(s): A

Explanation:

Answer(s): A. VM-VM anti-Affinity policy

A VM-VM anti-Affinity policy is a rule that ensures that two or more VMs don't run on the same AHV host. It's useful when an application provides HA and an AHV host can't be an application's single point of failure. In this case, the SQL cluster VMs should have a VM-VM anti-Affinity policy configured to prevent them from running on the same host and causing an outage if that host fails. A VM-VM anti-Affinity policy can be created using the aCLI commands. The other options are not relevant for this scenario.

Reference:

1: Affinity Policies - Nutanix Support & Insights 2: Affinity Policies Help | Nutanix Community

Reveal Solution Next Question

QUESTION: 35

After logging into Prism Element, an administrator presses the letter A on the Keyboard.

What is the expected outcome of this input?

Alerts page will launch
Analysis will launch
About Nutanix page will launch
API Explorer page will launch

Answer(s): D

Explanation:

API Explorer page will launch when an administrator presses the letter A on the keyboard after logging into Prism Element. This is one of the keyboard shortcuts that Prism Element provides for accessibility and ease of use. API Explorer is a tool that allows users to explore and test Nutanix REST APIs within Prism Element.

https://www.nutanixbible.com/3b-book-of-prism-navigation.html

Reveal Solution Next Question

QUESTION: 36

An administrator needs to increase bandwidth available to the AHV host and to the CVM.

How should the administrator complete this task?

In Prism, update vs0 to change the configuration to Active-Active.
Use manage-ovs commands to update br0 change the configuration to Active-Active.
In Prism, create a vsl interface and add any remaining uplinks.
Use manage-ovs commands to create br1 and add any remaining uplinks

Answer(s): B

Explanation:

The default network configuration for AHV hosts and CVMs is a bond named br0-up with two or more uplinks in active-backup mode. This means that only one uplink is active at a time, while the others are in standby mode. This provides high availability, but not load balancing or increased bandwidth. To increase the bandwidth available to the AHV host and the CVM, the administrator can change the bond mode to Active-Active, which allows all uplinks to be used simultaneously. This can be done using the manage-ovs commands on each AHV host. The steps are as follows1:

Log in to the AHV host using SSH.

Enter maintenance mode on the CVM by running allssh 'cluster status | grep -i cvm | grep -i down'.

Change the bond mode to Active-Active by running manage_ovs --bond_mode active-active update_uplinks br0-up <uplink_list>, where <uplink_list> is a comma-separated list of uplink interfaces (for example, eth0,eth1).

Verify the bond mode by running manage_ovs show_uplinks.

Exit maintenance mode on the CVM by running allssh 'cluster start'.

Reference:

AHV Networking Best Practices

Reveal Solution Next Question

Free NCP-MCI Exam Braindumps

QUESTION: 33

Explanation:

Reference:

QUESTION: 34

Explanation:

Reference:

QUESTION: 35

Explanation:

QUESTION: 36

Explanation:

Reference: