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]

The set of tools that can be used to attach a Kubernetes cluster to VMware Tanzu Mission Control are kubectl and VMware Tanzu Mission Control Web Ul. kubectl is a command-line tool that allows users to interact with Kubernetes clusters. VMware Tanzu Mission Control Web Ul is a graphical user interface that allows users to manage their clusters and policies. To attach a cluster, users need to use both tools. First, they need to use the web console to select the cluster group and generate a YAML manifest for the cluster. Then, they need to use kubectl to apply the manifest on the cluster and install the cluster agent extensions that enable communication with Tanzu Mission Control. References: Attach a Cluster - VMware Docs, What Happens When You Attach a Cluster

The Supervisor Service in Tanzu Kubernetes Grid exposes three layers of controllers to manage the lifecycle of a Tanzu Kubernetes Grid cluster:

• Virtual Machine Service (VMS) controllers provide an abstraction layer for managing virtual machines on vSphere. They allow users to create and manage VM classes, VM images, content libraries, and VM services.
• Tanzu Kubernetes Grid (TKG) controllers provide an abstraction layer for managing Kubernetes clusters on vSphere. They allow users to create and manage TKG service configurations, TKG service plans, TKG service instances, and TKG service bindings.
• Cluster API (CAPI) controllers provide an abstraction layer for managing Kubernetes clusters on any platform. They allow users to create and manage cluster objects, machine objects, machine deployment objects, machine set objects, and machine health check objects.

The other options are incorrect because:

• Authentication webhook, Container Storage Support, Cloud Provider Implementation are components of vSphere with Tanzu that enable authentication integration with vCenter Server, persistent storage provisioning forKubernetes workloads, and cloud provider functionality for vSphere respectively. They are not part of the Supervisor Service controllers.
• Aria integration Service, Tanzu Cluster API and Tanzu Container Network Controller are not valid components of Tanzu Kubernetes Grid or vSphere with Tanzu. Aria integration Service is a typo for Aria Operations for Applications (formerly VMware Tanzu Observability), which is a SaaS solution that collects and analyzes traces, metrics, and logs from various sources. Tanzu Cluster API is a typo for Cluster API (CAPI), which is one of the Supervisor Service controllers. Tanzu Container Network Controller is a typo for Antrea Controller, which is part of VMware Container Networking with Antrea, which is a solution that streamlines Kubernetes networking with a unified networking stack across multiple managed Kubernetes providers.
• VMware Tanzu Mission Control Connection agent, Cluster API and Kubernetes Connection Agent are not valid components of the Supervisor Service controllers. VMware Tanzu Mission Control Connection agent is a component of VMware Tanzu Mission Control, which is a SaaS solution that provides centralized management and governance for Tanzu Kubernetes Grid clusters across multiple platforms. Cluster API (CAPI) is one of the Supervisor Service controllers, but it is not specific to Tanzu Mission Control. Kubernetes Connection Agent is not a valid component of Tanzu Kubernetes Grid or vSphere with Tanzu.

References: VMware Tanzu for Kubernetes Operations Getting Started, vSphere with Tanzu Configuration and Management