2V0-71.23 Exam Dumps : VMware Tanzu for Kubernetes Operations Professional

A VM class in VMware vSphere with Tanzu specifies the CPU, memory, and resource reservations for a VM10. vSphere with Tanzu offers several preconfigured VM classes which you can use as is, edit, or delete. You can also create custom VM classes in your vCenter Server instance and it will be available to all Supervisor Clusters and the namespaces created in these clusters11.

When you create or edit a VM class, you can configure the following attributes:

• Name: A unique DNS compliant name that identifies the VM class.
• vCPU Count: The number of virtual CPUs (vCPUs) for a VM. This is a VM hardware configuration.
• CPU Resource Reservation: The guaranteed minimum CPU resource allocation for a VM. This value is expressed in percentage (%).
• Memory: The memory configured for a VM in MB, GB, or TB. This is a VM hardware configuration.
• Memory Resource Reservation: The guaranteed minimum memory resource allocation for a VM. This value is expressed in percentage (%).
• Storage: The storage configured for a VM in MB, GB, or TB. This is a VM hardware configuration.

The other options are incorrect because:

• Network is not an attribute that can be configured in a VM class. Network configuration is done at the namespace level by using network policies12.
• Operating system is not an attribute that can be configured in a VM class. Operating system configuration is done at the image level by using content libraries.
• PCI devices are not an attribute that can be configured in a VM class. PCI devices are not supported by vSphere with Tanzu.

References: VM Classes, Create a Custom VM Class, Network Policies, [Content Libraries]

A rolling upgrade is a method of upgrading a Kubernetes cluster without downtime by gradually replacing nodes or components with newer versions. A rolling upgrade ensures that there is no disruption to the availability and functionality of the cluster during the upgrade process. A rolling upgrade can be performed manually or using tools such as kubeadm or kops5.

The other options are incorrect because:

• In-place upgrade of each node is a method of upgrading a Kubernetes cluster by stopping each node or component and updating it to the newer version. This method can cause downtime and disruption to the cluster during the upgrade process.
• Use canary upgrade is not a valid method of upgrading a Kubernetes cluster. A canary upgrade is a technique for deploying new versions of applications or services by gradually exposing them to a subset of users or traffic before rolling them out to everyone6. It is not applicable to cluster upgrades.
• Deploy a new cluster with upgraded Kubernetes release is not a method of upgrading a Kubernetes cluster, but rather creating a new one. This method canbe costly and time-consuming, as it requires migrating all the resources and configurations from the old cluster to the new one.

References: Upgrade A Cluster, Canary deployments

The statement that correctly describes the Cluster API is that it is a specialized toolset to bring declarative, Kubernetes-style APIs to cluster creation, configuration, and management in theKubernetes ecosystem. Cluster API is a Kubernetes sub-project that provides declarative APIs and tooling to simplify provisioning, upgrading, and operating multiple Kubernetes clusters5. Cluster API uses a set of custom resource definitions (CRDs) to represent clusters, machines, and other objects. Cluster API also relies on providers to implement the logic for interacting with different infrastructure platforms5. References: Introduction - The Cluster API Book