An administrator needs to increase bandwidth available to the AHV host and to the CVM.How should the administrator complete this task?
Answer(s): B
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'.
AHV Networking Best Practices
Which inefficient VM Profile can be used to identify a VM that consumes too many resources and causes other VMs to starve?
Answer(s): C
A bully VM is a VM that consumes too many resources and causes other VMs to starve. A bully VM can affect the performance and availability of other VMs on the same host or cluster by hogging CPU, memory, disk, or network resources. A bully VM can be identified by using the VM Profile feature in Prism Central. The VM Profile feature analyzes the resource utilization of each VM and assigns it a profile based on its efficiency and impact on other VMs. The profiles are as follows3:Efficient: The VM is well-provisioned and has optimal resource utilization.Over-provisioned: The VM has more resources than it needs and has low resource utilization.Constrained: The VM has less resources than it needs and has high resource utilization.Inactive: The VM has no resource utilization and is idle or powered off.Bully: The VM has high resource utilization and causes contention for other VMs.To identify a bully VM, the administrator can use Prism Central to view the VM Profile dashboard and filter by profile type. The dashboard shows the number of VMs in each profile type, as well as their resource consumption and efficiency score. The administrator can also drill down into each VM to see its detailed metrics and recommendations for optimization.
VM Profile
What is he recommended approach for a constrained VM?
A constrained VM is one that does not have enough resources for the demand and can lead to performance bottlenecks. A VM is considered constrained when it exhibits one or more of the following baseline values, based on the past 21 days: CPU usage > 90% (moderate), 95% (severe) CPU ready time > 5%, 10% Memory usage > 90%, 95% Memory swap rate > 0 Kbps. To provide adequate host resources, resize (increase) the constrained VMs.
An administrator wants to expand the Failure Domain level of a cluster.What two options are available? (Choose two.)
Answer(s): C,D
Nutanix clusters are resilient to a drive, node, block, and rack failures because they use redundancy factor 2 by default, allowing Nutanix clusters to self-heal. Failure scenarios can be thought of in terms of fault domains, which are the physical or logical parts of a computing environment or location that are adversely affected when a device or service experiences an issue or outage. There are four fault domains in a Nutanix cluster: Disk, Node, Block, and Rack. Block and Rack are two options that are available for expanding the failure domain level of a cluster. Block fault tolerance is enabled by default and ensures that data is replicated across different blocks in a cluster5. Rack fault tolerance has to be configured manually and ensures that data is replicated across different racks in a cluster4.
1: Behavioral Learning Tools - Prism Central Resource Management - Nutanix 2: How Nutanix Handles Failures | Node Failure 3: Failure Domain Considerations - Nutanix Support & Insights 4: [Understanding Fault Domains and Rack Awareness - Nutanix] 5: [Nutanix Cluster Architecture Overview - Nutanix Bible]
What is a requirement to enable Flow Networking?
Flow Networking is a feature that enables software-defined networking for AHV clusters. It allows users to create and manage virtual private clouds (VPCs), subnets, and network services such as NAT, DHCP, routing, and VPN. Flow Networking also supports service insertion and chaining, which enables integration with third-party network functions such as firewalls and load balancers. Flow Networking is built on top of the microservices infrastructure (MSP) in Prism Central, which provides the platform for running various Nutanix services such as Calm, Karbon, and Objects. Therefore, to enable Flow Networking, the MSP must be enabled first on Prism Central1. The MSP can be enabled from the Prism Central settings page or from the command line interface (CLI) of the Prism CentralVM2. Enabling the MSP will also enable Flow Microsegmentation, which is another feature that provides network security and visibility for AHV clusters.
Flow Networking Overview
Post your Comments and Discuss Nutanix NCP-MCI exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the NCP-MCI content, but please register or login to continue.