2V0-71.23 Online Practice Questions and Answers

Correct Answer: AE

The control plane nodes are the nodes that run the Kubernetes control plane components, such as the API server, the scheduler, the controller manager, and etcd. The control plane nodes are responsible for managing the cluster state and orchestrating workload operations. The possible counts of control plane nodes in a Tanzu Kubernetes Grid workload cluster are 1 or 3. The control plane must have an odd number of nodes to ensure quorum and high availability. A single control plane node is suitable for development or testing purposes, while three control plane nodes are recommended for production clusters23. References: Deploy Workload Clusters - VMware Docs, Concepts and References - VMware Docs

Correct Answer: B

A NetworkPolicy is a Kubernetes object that controls what traffic is allowed to and from selected pods and network endpoints6. NetworkPolicy objects contain the following information:

The pods that are affected by this policy (the pod selector) The traffic that is allowed for these pods (the ingress and egress rules) The network entities that are allowed or denied for this traffic (the selectors and IP blocks)

By default, all pods in a cluster can communicate with each other and with any external network endpoint. A NetworkPolicy allows you to restrict this behavior by defining rules for pod isolation and network access. A NetworkPolicy is enforced

by a network plugin that supports it6.

The other options are incorrect because:

An Ingress is a Kubernetes object that manages external access to services in a cluster, typically HTTP7. It does not control what traffic is allowed to and from selected pods and network endpoints.

A PodSecurityPolicy is a Kubernetes object that controls security-sensitive aspects of pod specification, such as running as privileged or using host networking8. It does not control what traffic is allowed to and from selected pods and network

endpoints.

A Secret is a Kubernetes object that stores sensitive information, such as passwords or keys, in an encrypted form9. It does not control what traffic is allowed to and from selected pods and network endpoints. References: Network Policies,

Ingress, Pod Security Policies, Secrets

Correct Answer: BD

Kubernetes observability is the ability to monitor and analyze the performance, health, and behavior of Kubernetes clusters and applications. It provides visibility into Kubernetes clusters for troubleshooting and impact assessment, by collecting logs, events, traces, and alerts from various sources. It also collects real-time metrics from all layers of Kubernetes, such as nodes, pods, containers, services, and network policies, and displays them in dashboards and charts. Kubernetes observability helps administrators and developers to identify and resolve issues, optimize resource utilization, and ensure service quality and reliability. References: VMware Tanzu Observability Documentation, What is Kubernetes Observability?

Correct Answer: ABD

VMware Tanzu Kubernetes Grid is an enterprise-ready Kubernetes runtime that streamlines operations across multi-cloud infrastructure1. Tanzu Kubernetes Grid natively integrates with the following VMware products: NSX Advanced Load Balancer: A solution that provides L4 and L7 load balancing and ingress control for Kubernetes clusters. NSX Advanced Load Balancer can be used as the default load balancer provider for both management and workload clusters on vSphere, AWS, Azure, and other platforms2. NSX-T Data Center: A network virtualization and security platform that provides consistent networking and security for applications running across private and public clouds. NSX-T Data Center can be used as the default network plugin for both management and workload clusters on vSphere, AWS, Azure, and other platforms3. vSphere with VMware Tanzu: A solution that enables you to run Kubernetes workloads natively on a vSphere cluster, and to provision and manage Kubernetes clusters using the vSphere Client. vSphere with VMware Tanzu can be used as the platform to deploy Tanzu Kubernetes Grid management clusters and workload clusters4. The other options are incorrect because: BOSH is an open-source tool that provides release engineering, deployment, lifecycle management, and monitoring of distributed systems. BOSH is not a VMware product, nor does it natively integrate with Tanzu Kubernetes Grid5. vRealize Network Insight is a solution that delivers intelligent operations for software-defined networking and security. It helps optimize network performance and availability with visibility and analytics across virtual and physical networks. vRealize Network Insight is not natively integrated with Tanzu Kubernetes Grid6. Tanzu Mission Control is a centralized management platform for consistently operating and securing your Kubernetes infrastructure and modern applications across multiple teams and clouds. Tanzu Mission Control is not natively integrated with Tanzu Kubernetes Grid, but rather works with it as a separate product7. References: VMware Tanzu Kubernetes Grid Overview, NSX Advanced Load Balancer, NSX-T Data Center, vSphere with VMware Tanzu, BOSH, vRealize Network Insight, Tanzu Mission Control Overview

Correct Answer: D

A tool that can be used to backup and restore workloads on clusters provisioned by the VMware Tanzu Kubernetes Grid Service is the Velero Plugin for VMware vSphere. The Velero Plugin for VMware vSphere is an extension of Velero, an open source tool that performs backup and restore of Kubernetes resources and persistent volumes5. The plugin leverages the snapshot capabilities of vSphere to create backups of Kubernetes workloads running on vSphere-managed infrastructure, such as VMware Cloud on AWS or VMware Cloud on Dell EMC5. The plugin also supports restoring backups to the same or different clusters, as well as migrating workloads across clusters5. References: Velero Plugin for VMware vSphere Documentation

Correct Answer: C

The statement that correctly describes a global namespace in VMware Tanzu Service Mesh is that it defines an application boundary and provides consistent traffic routing, connectivity, resiliency, and security for applications across multiple clusters. A global namespace is a logical abstraction of an application from the underlying infrastructure that spans across multiple clusters and clouds4. A global namespace connects the resources and workloads that make up the application into one virtual unit and manages their identity, discovery, connectivity, security, and observability4. A global namespace also enables automatic service discovery and cross-cluster communication within the application boundary4. References: Global Namespaces - VMware Docs

Correct Answer: C

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 tab2. 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 namespace2. References: Create and Configure a vSphere Namespace - VMware Docs, vSphere with Tanzu Concepts - VMware Docs

Correct Answer: BE

Two valid options for obtaining kubectl config file in Tanzu Kubernetes environment are:

Download from vSphere UI: For Tanzu Kubernetes clusters that are deployed on vSphere with Tanzu, you can download the kubeconfig file from the vSphere UI by selecting the cluster and clicking on the Download kubeconfig button1. This

file contains the credentials and connection information for the cluster, which you can use to access it with kubectl1.

Access from VMware Tanzu Mission Control: For Tanzu Kubernetes clusters that are attached or provisioned by VMware Tanzu Mission Control, you can access the kubeconfig file from the Tanzu Mission Control console by selecting the

cluster and clicking on the Access this cluster button2. This will generate a YAML file that you can download and use to connect to the cluster with kubectl2. References: Download a Kubeconfig File for a Tanzu Kubernetes Cluster - VMware Docs, Connect to a Managed Cluster with kubectl - VMware Docs

Correct Answer: A

To register the vSphere management cluster in VMware Tanzu Mission Control, an administrator can use either the web console or the CLI of VMware Tanzu Mission Control. The web console provides a graphical user interface to perform the registration, while the CLI provides a command-line interface to run a script that automates the registration process. Both methods require the administrator to have access to the vSphere management cluster and to provide some information such as the cluster name, context, and namespace. The registration process creates a service account and a secret in the vSphere management cluster, and generates a kubeconfig file that is used by VMware Tanzu Mission Control to connect to the cluster. References: VMware Tanzu Mission Control Documentation, Registering a vSphere Management Cluster

Correct Answer: CDF

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]