QUESTION: 57

A recently configured cluster is leveraging NearSync with a recovery schedule of 15 minutes. It is noticed that the cluster is consistently transitioning in an Out of NearSyne.

What action should be taken to potentially address this issue?

Increase network bandwidth
Change the NearSync schedule to 30 minutes.
Add a vCPUs to the user VMs.
Configure a secondary schedule in the same Protection Domain.

Answer(s): A

Explanation:

One of the possible reasons for a cluster to transition out of NearSync is insufficient network bandwidth between the source and target clusters. NearSync requires a minimum network bandwidth of 10 Mbps per VM for replication3. If the network bandwidth is lower than the required amount, the replication of recovery points may take longer than the configured RPO, resulting in an Out of NearSync condition. To address this issue, you can increase the network bandwidth between the clusters or reduce the number of VMs protected by NearSync4.

Reference:

1: Stargate - Nutanix Bible 2: Nutanix Cluster Architecture Overview - Nutanix Bible 3: NearSync Disaster Recovery (RPO <= 15 minutes) - Nutanix Support & Insights 4: Transitioning in and out of NearSync - Nutanix Support & Insights

Reveal Solution Next Question

QUESTION: 58

Which scenario would benefit most from Erasure Coding being enabled on a container?

Long term storage of data which is written once and read infrequently
High performance database where all is relatively hot.
VDI use cases where a single VM is cloned 100's of times
WEB and API Servers

Answer(s): A

Explanation:

The correct answer is A. Long term storage of data which is written once and read infrequently.

Erasure Coding is a feature that increases the usable capacity on a Nutanix cluster by reducing the amount of data replication. Instead of replicating data, Erasure Coding uses parity information to rebuild data in the event of a disk failure. The capacity savings of Erasure Coding is in addition to deduplication and compression savings1.

Erasure Coding is most beneficial for scenarios where the data is written once and read infrequently, such as long term storage of archival data, backup data, or cold data. This is because Erasure Coding has some trade-offs and limitations that may affect the performance and availability of the cluster.
Some of these trade-offs and limitations are2:

Erasure Coding requires more CPU and memory resources than replication, as it involves more complex calculations for encoding and decoding data.

Erasure Coding increases the network bandwidth consumption, as it involves more data transfers between nodes for encoding and decoding data.

Erasure Coding reduces the resiliency of the cluster, as it can tolerate fewer node failures than replication. For example, a cluster with redundancy factor 2 can tolerate one node failure with replication, but only two disk failures with Erasure Coding.

Erasure Coding is not effective for workloads that have many overwrites or random writes, as it involves more overhead for updating the parity information.

Erasure Coding is not supported for some features, such as volume groups, file server VMs, or Metro Availability.

Therefore, if an administrator needs to configure a container on a Nutanix cluster, they should enable Erasure Coding only if the container will store data that is written once and read infrequently. This way, they can maximize the capacity savings of Erasure Coding without compromising the performance and availability of the cluster.

Reference:

Erasure Coding | Nutanix Community

Reveal Solution Next Question

QUESTION: 59

An administrator logs into the Nutanix Support Portal and notices there is a new version of the LCM Framework available. In an effort ensure LCM is providing the latest features, the administrator would like to upgrade LCM.

How can the LCM Framework be upgraded?

Perform an LCM inventory
Upload the latest LCM Framework as an image in the image Configuration in Prism
Upload the latest LCM Framework bundle via Upgrade Software in Prism
Upgrade AOS

Answer(s): A

Explanation:

LCM (Life Cycle Manager) is a feature that allows Nutanix administrators to perform one-click firmware and software upgrades for Nutanix clusters and components. LCM fetches inventory and update information from a pre-configured URL that contains the latest versions of firmware and software packages. However, upgrading Nutanix AOS does not automatically update the fetch URL. To update the fetch URL, the administrator needs to update the LCM framework. The LCM framework is the core component of LCM that provides the logic and functionality for inventory, download, and upgrade operations1.

To upgrade the LCM framework, the administrator needs to perform an LCM inventory. An LCM inventory is a process that scans the cluster and its components for their current firmware and software versions and compares them with the available versions from the fetch URL. If there is a newer version of the LCM framework available, it will be shown as an update option under Cluster Software Component in the Available Updates page. The administrator can then select and apply the LCM framework update to upgrade it to the latest version2.

The administrator can perform an LCM inventory using Prism Element or Prism Central. The steps are as follows3:

In Prism Element, go to the Network Configuration page and click Life Cycle Management.

In Prism Central, go to the Services page and click Life Cycle Management.

Click Inventory in the toolbar and select Perform Inventory from the drop-down menu.

Wait for the inventory process to complete and check for any available updates.

Reference:

LCM: Upgrade process and Path for LCM

Reveal Solution Next Question

QUESTION: 60

An administrator has been asked to enable block awareness and increase the fault tolerance to FT2

on a Nutanix AHV cluster with the following configuration:

Four blocks

One node per block

Will the administrator be able to accomplish these tasks?

No-Fault tolerance changes are not supported.
Yes-FT2 requires a minimum of three nodes.
Yes-Block awareness requires a minimum of three blocks.
No-FT2 requires a minimum of five nodes.

Answer(s): D

Explanation:

Fault tolerance (FT) is the ability of a cluster to withstand node failures and maintain data availability. FT is determined by the replication factor (RF) of the data, which is the number of copies of each data block stored on different nodes. FT = RF - 1, meaning that the cluster can tolerate as many node failures as one less than the RF. Block awareness is a feature that enhances fault tolerance by ensuring that data copies are distributed across different blocks, which are groups of nodes that share a power source and network switch. Block awareness requires a minimum of three blocks and a minimum of six nodes in the cluster.

In this scenario, the administrator has been asked to enable block awareness and increase the fault tolerance to FT2 on a Nutanix AHV cluster with the following configuration: Four blocks, One node per block. The administrator will not be able to accomplish these tasks because:

To enable block awareness, the cluster needs at least six nodes, but it only has four nodes.

To increase the fault tolerance to FT2, the cluster needs at least five nodes per RF3 or seven nodes per RF4, but it only has four nodes.

Therefore, the administrator will need to add more nodes to the cluster before enabling block awareness and increasing the fault tolerance to FT2.

Reveal Solution Next Question

Free NCP-MCI Exam Braindumps (page: 16)

QUESTION: 57

Explanation:

Reference:

QUESTION: 58

Explanation:

Reference:

QUESTION: 59

Explanation:

Reference:

QUESTION: 60

Explanation:

NCP-MCI Exam Discussions & Posts