According to the Nutanix Support & Insights web search result1, erasure coding is a data savings technique that utilizes stripes and parity calculation in a Nutanix cluster. Erasure coding increases the usable capacity on a cluster by reducing the replication factor of data blocks. Instead of replicating data, erasure coding uses parity information to rebuild data in the event of a disk or node failure. Erasure coding can save up to 50% of storage space compared to replication factor 2, and up to 75% compared to replication factor 32.

Shadow Clones is a Nutanix feature that provides effective caching optimization in VDI environments. VDI stands for Virtual Desktop Infrastructure, which is a technology that allows users to access virtual desktops hosted on a centralized server. VDI environments typically have a high degree of similarity among desktop images, which means that many VMs access the same data blocks from the storage layer. Shadow Clones leverages this similarity by creating read-only copies of frequently accessed data blocks on each node's SSD tier, reducing network traffic and improving performance. Shadow Clones works automatically and transparently without any configuration or intervention from the administrator.
References: : [Fault Tolerance - Nutanix Bible] : [Block Awareness - Nutanix Bible] : [Block Awareness - Nutanix Support & Insights] : [Shadow Clones - Nutanix Bible] : [Shadow Clones - Nutanix Support & Insights] : [Shadow Clones - Nutanix Community]

These are the three steps that the administrator must take to increase throughput to the host. According to the network diagram, the host has two 10Gb interfaces and two 1Gb interfaces in the default bond, but only one of the 10Gb interfaces is connected to a switch. The other 10Gb interface is disconnected and has a red "X" on it.
The two 1Gb interfaces are also disconnected and have dotted lines. This means that the host is using only one
10Gb interface for all its network traffic, which limits its maximum bandwidth to 10 Gbps.
To increase the throughput, the administrator should connect both 10Gb interfaces to the physical switch, preferably to different switches for redundancy and high availability. This will allow the host to use both 10Gb interfaces for network traffic, which can increase its maximum bandwidth to 20 Gbps. However, this also requires changing the bond mode from active-backup to balance-slb or balance-tcp, which are load balancing modes that distribute network traffic across multiple interfaces based on source MAC address or TCP session1. The default bond mode of active-backup only uses one interface at a time and switches to another interface only when the active one fails2.
Finally, the administrator should remove any 1Gb interfaces still connected from the default bond, as they are not needed and may cause performance issues or conflicts with the load balancing modes. The 1Gb interfaces can be used for other purposes, such as management or backup networks, by creating separate bonds or bridges for them3. Alternatively, they can be left disconnected if they are not required.

According to the web search results, the two impacts on the cluster that will result from increasing the vCPU count on all of the VDI VMs are:
Increase CPU utilization%: CPU utilization is the percentage of time that a CPU is busy executing instructions5. By increasing the vCPU count on all of the VDI VMs, the administrator will increase the demand for CPU resources on the cluster, which will increase the CPU utilization percentage6.
Increase CPU ready%: CPU ready is the percentage of time that a vCPU is ready to run but is waiting for a physical CPU to become available5. By increasing the vCPU count on all of the VDI VMs, the administrator will increase the contention for physical CPU resources on the cluster, which will increase the CPU ready percentage6. A high CPU ready percentage can indicate performance issues such as latency or slowdowns5.