Question 1

Choose two supported functionalities when enabling Workload Management with a VMware vSphere Distributed Switch? (Choose two.)

Accepted Answer

A, C

Explanation: When enabling VMware Workload Management (vSphere with Tanzu) using a vSphere Distributed Switch (VDS) for networking, a specific set of functionalities is supported. This configuration requires an external load balancer, for which the NSX Advanced Load Balancer (formerly Avi Networks) is the supported solution to provide L4 load balancing for the Supervisor Cluster and Kubernetes services. The primary purpose of this configuration is to deploy and manage upstream-conformant Tanzu Kubernetes clusters (TKC). Notably, certain features, such as running vSphere Pods directly on ESXi hosts, are not available with the VDS networking stack and require the more advanced capabilities of NSX-T Data Center.

Question 2

What is the command to find out the available node base operating system images?

Accepted Answer

D

Explanation: In a vSphere with Tanzu environment, the base operating system images for creating Tanzu Kubernetes cluster nodes are managed as Kubernetes custom resources of the kind VirtualMachineImage. These images are synchronized from a vSphere Content Library that is subscribed to VMware's official repository. To list the OS images that are available for provisioning new nodes, an administrator connects to the Supervisor Cluster and uses the command kubectl get virtualmachineimages. This command queries the API server and returns a list of available images, their versions, and their readiness status.

Question 3

Which two options are supported use of Content Library in VMware vSphere with Tanzu? (Choose two.)

Accepted Answer

A, B

Explanation: VMware vSphere with Tanzu utilizes the Content Library to store and distribute Tanzu Kubernetes Grid (TKG) release images for provisioning clusters. There are two primary, supported methods depending on the environment's network connectivity. For internet-connected environments, the recommended approach is to use a Subscribed Content Library. This library subscribes to a VMware-hosted URL and automatically synchronizes the TKG images, which requires outbound internet access from the vCenter Server. For air-gapped or internet-restricted environments, a Local Content Library is used. In this scenario, the administrator manually downloads the TKG OVA files from the VMware Customer Connect portal and uploads them to the local library within the vCenter Server.

Question 4

Under Menu, which section to enable Tanzu Kubernetes Cluster in VMware vSphere for Tanzu on vSphere Client?

Accepted Answer

C

Explanation: The "Workload Management" section in the vSphere Client is the dedicated interface for enabling and managing vSphere with Tanzu. This is where an administrator initiates the wizard to configure and enable the Supervisor Cluster on a vSphere cluster. The Supervisor Cluster provides the foundation for running Kubernetes workloads natively in vSphere, including the provisioning of Tanzu Kubernetes Clusters (TKCs) through the integrated Tanzu Kubernetes Grid Service. This centralized location is the starting point for the entire configuration workflow.

Question 5

Refer to the exhibit. In the following StorageClass manifest, which field is used to specify the Volume Plugin driver used for underlying storage array? https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/VMware_2V0-71.21/page_3_img_1.jpg

Accepted Answer

D

Explanation: The provisioner field in a Kubernetes StorageClass manifest is mandatory and determines which volume plugin (driver) is used for dynamically provisioning PersistentVolumes. When a PersistentVolumeClaim requests this StorageClass, the Kubernetes control plane invokes the specified provisioner to create the underlying storage volume. For VMware environments, this value would typically be set to csi.vsphere.vmware.com to use the vSphere Container Storage Interface (CSI) driver. The other fields serve different purposes, such as naming the class or passing configuration details to the already-specified provisioner.

Question 6

What are the pre-requisites for installing the Harbor registry in Tanzu Kubernetes Grid (TKG)?

Accepted Answer

B

Explanation: To install Harbor, which is packaged as a TKG Extension, several prerequisites must be met. First, a Tanzu Kubernetes Grid (TKG) management cluster must be deployed, as it manages the lifecycle of workload clusters where extensions are installed. Second, the TKG extensions bundle, which contains the Harbor package and its dependencies, must be downloaded to the local machine. Finally, the Carvel tool suite (including ytt, kapp, kbld) must be installed. The Tanzu CLI uses these tools to process, customize, and deploy the extension manifests onto a workload cluster.

Question 7

Why is the port 6443 required in the boostrap machine to deploy Tanzu Kubernetes Grid on vSphere environment?

Accepted Answer

B

Explanation: During the deployment of a Tanzu Kubernetes Grid (TKG) management cluster, the bootstrap machine needs to communicate with the control plane of the new cluster it is creating. The central component of the Kubernetes control plane is the API server, which exposes the Kubernetes API. By default, the Kubernetes API server listens for secure HTTPS traffic on TCP port 6443. The bootstrap machine uses this port to send instructions and configurations to build and validate the management cluster on the vSphere environment.

Question 8

What are two ClusterAPI providers being used in Tanzu Kubernetes Grid? (Choose two.)

Accepted Answer

B, E

Explanation: Tanzu Kubernetes Grid (TKG) utilizes the open-source Cluster API (CAPI) framework to automate the lifecycle management of Kubernetes clusters across multiple infrastructure platforms. TKG bundles specific CAPI providers to interact with the underlying infrastructure. The Cluster API Provider for vSphere (CAPV) is a core component, enabling TKG to provision and manage clusters on VMware's vSphere platform. For public cloud deployments, TKG includes the Cluster API Provider for AWS (CAPA), which translates declarative Kubernetes-style API objects into the necessary actions within an Amazon Web Services environment. These providers are fundamental to TKG's multi-cloud capabilities.

Question 9

Which is the correct option to forward logs from Tanzu Kubernetes Grid clusters to Elastic, Kafka, Splunk or an HTTP endpoint?

Accepted Answer

D

Explanation: Tanzu Kubernetes Grid (TKG) integrates with external logging solutions by deploying a log forwarder onto the Kubernetes clusters. The officially documented and recommended method is to deploy Fluent Bit, a lightweight and extensible log processor and forwarder. Once deployed as a DaemonSet on the cluster, Fluent Bit can be configured with various output plugins to collect logs from all nodes and containers and forward them to a wide range of backends, including Elastic (Elasticsearch), Kafka, Splunk, and generic HTTP endpoints, as specified in the question.

Question 10

Which option provides a configuration blueprint to deploy Tanzu Kubernetes clusters?

Accepted Answer

D

Explanation: A Tanzu Kubernetes Cluster Plan is a standardized, versioned blueprint that defines the configuration for deploying Tanzu Kubernetes Grid (TKG) clusters. TKG includes default plans, such as dev (for a single control plane node) and prod (for a highly available, multi-control plane node setup). These plans specify the number and size of control plane and worker nodes, virtual machine types, and other infrastructure settings. Administrators can customize these plans or create new ones to enforce consistent cluster configurations across an organization, simplifying and standardizing the deployment process.

Question 11

Which step must be taken to enable Kubernetes auditing on a Tanzu Kubernetes cluster?

Accepted Answer

A

Explanation: In VMware Tanzu Kubernetes Grid (TKG), cluster features are configured declaratively using a cluster configuration file before deployment. To enable the Kubernetes API server audit logging feature, the ENABLEAUDITLOGGING configuration variable must be set to true in the cluster's YAML manifest. This setting instructs the TKG control plane to configure the Kubernetes API server on the cluster with the necessary flags to activate audit logging upon creation. This declarative approach ensures consistent and reproducible cluster configurations, which is a core principle of infrastructure-as-code.

Question 12

Which upgrade method can be used for an ‘in-place’ Kubernetes update?

Accepted Answer

A

Explanation: An in-place upgrade of a Tanzu Kubernetes cluster is performed by declaratively changing the desired Kubernetes version in the cluster's object manifest. The kubectl patch command is the standard method used to modify the tanzuKubernetesRelease (TKR) property within the TanzuKubernetesCluster object's specification. Once this change is applied, the Tanzu Supervisor controllers detect the modification and initiate a rolling upgrade of the control plane and worker nodes to the specified TKR version, ensuring a non-disruptive update process.

Question 13

Which command is used to upgrade a Tanzu Kubernetes Grid Cluster (TKG) to a different kubernetes version?

Accepted Answer

B

Explanation: The correct command to upgrade a Tanzu Kubernetes Grid (TKG) workload cluster is tkg upgrade cluster. This command initiates the upgrade process for the specified cluster. To target a specific Kubernetes release, the --kubernetes-version flag is used, followed by the desired version string (e.g., v1.23.8---vmware.1-tkg.1). The command first upgrades the control plane nodes and then proceeds to upgrade the worker nodes, ensuring a controlled and sequential update of the cluster's Kubernetes version.

Question 14

What is the command to recognize a cluster in a disconnected state to Tanzu Mission Control?

Accepted Answer

D

Explanation: The tmc cluster reattach command is used to re-establish the connection between a registered Kubernetes cluster and Tanzu Mission Control (TMC). This is necessary when the agents running on the cluster are in an unhealthy or disconnected state. The command effectively reinstalls the TMC agent components on the cluster, allowing it to reconnect and synchronize its state with TMC without needing to be de-registered and attached again. The -n flag specifies the cluster name as it is known in TMC.

Question 15

What is the advantage of connecting the Tanzu Kubernetes Grid (TKG) CLI to a vSphere with Tanzu Supervisor Cluster?

Accepted Answer

D

Explanation: The primary advantage of connecting the Tanzu Kubernetes Grid (TKG) CLI to a vSphere with Tanzu Supervisor Cluster is to enable the command-line-driven deployment and lifecycle management of Tanzu Kubernetes clusters (TKCs). Once authenticated to the Supervisor Cluster, an administrator or DevOps engineer can use tanzu commands (e.g., tanzu cluster create, tanzu cluster scale, tanzu cluster upgrade, tanzu cluster delete) to provision and manage workload clusters directly on vSphere. This provides a powerful, scriptable, and declarative method for managing Kubernetes infrastructure, which is the core function of the TKG CLI in this context.

Free VMware 2V0-71.21 Actual Exam Questions