VMware Tanzu for Kubernetes Operations Professional

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

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 clusters 11.
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 policies 12. 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 correct procedure to attach a management cluster using the Tanzu Mission Control web console is to go to the Administration page, select the Management Clusters tab, click Register Management Cluster, and select the type of management cluster to register. A management cluster is a Kubernetes cluster that runs the Cluster API components and can be used to create and manage workload clusters 3. VMware Tanzu Mission Control supports registering two types of management clusters: Tanzu Kubernetes Grid management clusters and vSphere with Tanzu Supervisor Clusters4. By registering a management cluster with Tanzu Mission Control, you can enable lifecycle management of its workload clusters, assign them to cluster groups, apply policies, and monitor their health and performance 4.
References:
Register a Management Cluster with Tanzu Mission Control - VMware Docs, Management Clusters - The Cluster API Book

Velero is an open source tool that can safely backup and restore, perform disaster recovery, and migrate Kubernetes cluster resources and persistent volumes. Velero can capture both the Kubernetes objects and the persistent volumes associated with an application, and restore them in a different cluster or namespace. Velero also supports different storage providers to store its backups, such as AWS S3, Azure Blob Storage, Google Cloud Storage, and more.
References:
1: (https://middleware.io/blog/kubernetes-observability/)
2: (https://docs.vmware.com/en/VMware-Tanzu-Mission-Control/services/tanzumc-using/GUID-0A1AEC6A-3E5C-424F-8EBC-1DDFC14D2688.html)
3: (https://docs.vmware.com/en/VMware-Tanzu-Mission-Control/services/tanzumc-using/GUID-EB507AAF-5F4F-400F-9623-BA611233E0BD.html)

To create a vSphere Namespace, the correct steps are to use the vSphere web client, select Workload Management, select Namespaces tab, and click Create Namespace. A vSphere Namespace is a logical grouping of Kubernetes resources that can be used to isolate and manage workloads on a Supervisor Cluster1. To create a vSphere Namespace, a user needs to have the vSphere Client and the required privileges to access the Workload Management menu and the Namespaces tab 2. From there, the user can select the Supervisor Cluster where to place the namespace, enter a name for the namespace, configure the network settings, set the resource limits, assign permissions, and enable services for the namespace 2.
References:
Create and Configure a vSphere Namespace - VMware Docs, vSphere with Tanzu Concepts - VMware Docs

The Kubernetes RBAC API declares four kinds of Kubernetes object: Role, ClusterRole, RoleBinding and ClusterRoleBinding. These objects are used to define permissions and assign them to users or groups within a cluster. A Role or ClusterRole contains rulesthat represent a set of permissions on resources or non-resource endpoints. A RoleBinding or ClusterRoleBinding grants the permissions defined in a Role or ClusterRole to a set of subjects (users, groups, or service accounts). A RoleBinding applies only within a specific namespace, while a ClusterRoleBinding applies cluster-wide.
The other options are incorrect because: CloudPolicyObject is not a valid Kubernetes object type. It might be confused with NetworkPolicy, which is an object type that defines how pods are allowed to communicate with each other and other network endpoints. Container type and Container object are not valid Kubernetes object types. They might be confused with Pod, which is an object type that represents a group of one or more containers running on a node.
ClusterObject and ClusterNode are not valid Kubernetes object types. They might be confused with Cluster and Node, which are concepts that describe the logical and physical components of a Kubernetes cluster.
References:
Using RBAC Authorization, Kubernetes RBAC: Concepts, Examples & Top
Misconfigurations

The correct resource hierarchy order in VMware Tanzu Mission Control is Organization -> Cluster Groups
-> Clusters. An organization is the root of the resource hierarchy and represents a customer account in Tanzu Mission Control. A cluster group is a logical grouping of clusters that can be used to apply policies and manage access. A cluster is a Kubernetes cluster that can be attached or provisioned by Tanzu Mission Control. A cluster belongs to one and only one cluster group, and a cluster group belongs to one and only one organization.
References:
VMware Tanzu Mission Control Concepts, Resource Hierarchy

The Kubernetes project that vSphere with Tanzu Supervisor Cluster uses to automate the lifecycle management of Tanzu Kubernetes Grid Clusters is Cluster API. Cluster API is a Kubernetes project that provides declarative APIs for cluster creation, configuration, and management. 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 platforms 5. vSphere with Tanzu Supervisor Cluster uses Cluster API to deploy and manage Kubernetes clusters on vSphere 7 across multiple vCenter Server instances and/or multiple data centers via Tanzu Mission Control6.
References:
Taking Kubernetes to the People: How Cluster API Promotes Self ... - VMware, kubernetes-
sigs/cluster-api - GitHub

VMware Tanzu Mission Control (TMC) is a centralized management platform for consistently operating and securing your Kubernetes infrastructure and modern applications across multiple teams and clouds 1.
TMC provides a catalog of curated open-source software packages that you can deploy to your clusters with a few clicks 2. To deploy an application to a Kubernetes cluster using TMC catalog, you need to follow these steps3: From the TMC Console, navigate to Catalog.
Select the package that you want to install from the list of available packages. You can filter the packages by name, provider, or category. Click Install Package to start the installation wizard. On the Installation Settings page, specify the following information: Click Install to confirm the installation settings and start the installation process. Wait for the installation to complete. You can monitor the progress and status of the installation on the Package Instances page.
The other options are incorrect because: From the TMC Console, in Catalog, from Available Tanzu Packages, specify the target cluster and the package to install is false. There is no such option as Available Tanzu Packages in the TMC Console. The correct option is Install Package.
Using the Tanzu CLI, enter the command tanzu package install is false. The Tanzu CLI is a command-line tool that allows you to interact with Tanzu Kubernetes Grid clusters and packages 4. It is not related to TMC or its catalog. Using the TMC CLI, enter the command tmc cluster tanzupackage create is false.
There is no such command as tmc cluster tanzupackage create in the TMC CLI. The TMC CLI is a command-line tool that allows you to interact with TMC and its resources 5. It does not support installing packages from the catalog.
References:
VMware Tanzu Mission Control Overview, Catalog Overview, Install a Package from Catalog, Tanzu CLI Overview, TMC CLI Overview

Contour is an open-source Kubernetes ingress controller that provides dynamic configuration updates and makes use of the Envoy proxy as a data plane 1. Envoy is an open-source edge and service proxy that can handle large volumes of network traffic between services in a cloud-native environment 2. Contour leverages Envoy's advanced features such as load balancing, health checking, dynamic service discovery, circuit breaking, rate limiting, and more 3. Contour also integrates with Envoy's external authorization filter to support external authentication and authorization providers 4.
The other options are incorrect because: NSX Load Balancer is a VMware solution that provides L4 and L7 load balancing and ingress control for Kubernetes clusters 5. It is not the data plane for Contour. Istio is an open-source service mesh that provides a uniform way to connect, secure, control, and observe services in a distributed system 6. It is not the data plane for Contour.
Prometheus is an open-source systems monitoring and alerting toolkit that can collect metrics from various sources, including Kubernetes clusters 7. It is not the data plane for Contour.
References:
Contour Overview, Envoy Overview, Contour Architecture, External Authorization Support,
NSX Advanced Load Balancer, Istio Overview, Prometheus Overview