2V0-71.23 VMware Tanzu for Kubernetes Operations Professional Questions and Answers

To enable workload management in vSphere using NSX Advanced Load Balancer, an administrator needs to prepare two components on NSX Advanced Load Balancer in advance: the Service Engine Group and the NSX Advanced Load Balancer Controller1.

• The Service Engine Group is a logical group of Service Engines that share the same configuration and resources. A Service Engine is a virtual machine that handles the data plane operations of NSX Advanced Load Balancer, such as load balancing, health monitoring, SSL termination, and more2. The administrator needs to configure a Service Engine Group for each Supervisor Cluster that will use NSX Advanced Load Balancer as the load balancer provider1.
• The NSX Advanced Load Balancer Controller is a virtual machine that handles the control plane operations of NSX Advanced Load Balancer, such as configuration, analytics, orchestration, and management2. The administrator needs to deploy and configure the NSX Advanced Load Balancer Controller VM in the management network of the vSphere environment where workload management will be enabled1.

The other options are incorrect because:

• The NSX Controller is not a component of NSX Advanced Load Balancer, but rather a component of NSX-T Data Center. The NSX Controller is a clustered virtual appliance that provides the control plane functions for logical switching and routing3. It is not required for enabling workload management in vSphere using NSX Advanced Load Balancer.
• Providing connectivity to NSX Manager is not a component of NSX Advanced Load Balancer, but rather a prerequisite for enabling workload management in vSphere using NSX-T Data Center. The NSX Manager is a virtual appliance that provides the management plane functions for NSX-T Data Center3. It is not required for enabling workload management in vSphere using NSX Advanced Load Balancer.
• The Avi Kubernetes Operator is not a component of NSX Advanced Load Balancer, but rather an optional tool that can be used to automate the installation and configuration of NSX Advanced Load Balancer on Kubernetes clusters4. It is not required for enabling workload management in vSphere using NSX Advanced Load Balancer.

References: Install and Configure the NSX Advanced Load Balancer for vSphere with Tanzu with NSX, NSX Advanced Load Balancer Architecture, NSX-T Data Center Architecture, Avi Kubernetes Operator

Prometheus is an open-source systems monitoring and alerting toolkit that can collect metrics from target clusters at specified intervals, evaluate rule expressions, display the results, and trigger alerts if certain conditions arise8. Tanzu Kubernetes Grid includes signed binaries for Prometheus that users can deploy on workload clusters to monitor cluster health and services9. Prometheus uses a pull model to scrape metrics from various sources, such as Kubernetes nodes, pods, services, and endpoints. Prometheus stores the collected metrics in a time-series database and allows users to query them using PromQL, a powerful query language. Prometheus also supports defining alert rules based on metric values and sending notifications to external systems, such as Alertmanager8.

The other options are incorrect because:

• Provide the functionality of a lightweight log processor and forwarder that allows you to collect data and logs from different sources is a description of Fluent Bit, which is an open-source log processor and forwarder that can be used to collect data and logs from Kubernetes clusters and send them to various destinations10. Fluent Bit is not part of Tanzu Kubernetes Grid.
• Inject time-series database (TSDB) data into high-quality graphs and visualizations is a description of Grafana, which is an open-source visualization and analytics software that can be used to query, visualize, alert on, and explore metrics from various sources, including Prometheus11. Grafana is not part of Tanzu Kubernetes Grid.
• Extend the open-source Docker distribution by adding the functionalities usually required by users such as security and identity control and management is a description of Harbor, which is an open-source cloud native registry that can be used to store, sign, and scan container images for vulnerabilities12. Harbor is not part of Tanzu Kubernetes Grid.

References: Prometheus Overview, Implement Monitoring with Prometheus and Grafana, Fluent Bit, What is Grafana?, Harbor Overview

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]

Two services that require Transport Layer Security (TLS) certificates to provide encryption in VMware Tanzu Service Mesh are:

• Certificate Authority (CA) Service: A service that issues certificates to services in the service mesh to enable mutual TLS (mTLS) communication between them. The CA service uses a root certificate to sign the certificates for the services, and verifies the identity of the services using the certificates. The CA service also rotates the certificates periodically to ensure security8.
• Public Service: A service that exposes an internal service in the service mesh to external clients over HTTPS. The public service uses a TLS certificate to encrypt the traffic between the external clients and the internal service, and to authenticate itself to the clients. The TLS certificate must match the domain name of the public service9.

The other options are incorrect because:

• Internal Service: A service that runs inside the service mesh and communicates with other services using mTLS. The internal service does not require a TLS certificate, but rather uses a certificate issued by the CA service to enable mTLS10.
• Proxy Service: A service that acts as an intermediary between an internal service and an external service, such as a database or an API. The proxy service does not require a TLS certificate, but rather uses a certificate issued by the CA service to enable mTLS with the internal service. The proxy service also uses the external service’s certificate to verify its identity11.
• External Service: A service that runs outside the service mesh and communicates with an internal service over HTTPS or TCP. The external service does not require a TLS certificate from Tanzu Service Mesh, but rather uses its own certificate to encrypt the traffic with the internal service, and to authenticate itself to the internal service.

References: Certificate Authority (CA) Service, Public Services, Internal Services, Proxy Services,

Contour is an open-source Kubernetes ingress controller that provides dynamic configuration updates and makes use of the Envoy proxy as a data plane1. Envoy is an open-source edge and service proxy that can handle large volumes of network traffic between services in a cloud-native environment2. Contour leverages Envoy’s advanced features such as load balancing, health checking, dynamic service discovery, circuit breaking, rate limiting, and more3. Contour also integrates with Envoy’s external authorization filter to support external authentication and authorization providers4.

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 clusters5. 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 system6. 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 clusters7. 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

A Deployment is a Kubernetes object that allows you to perform a rolling update without disrupting services. A Deployment manages a ReplicaSet or a Pod and provides declarative updates for them. You can describe the desired state of your application using a Deployment, and it will change the actual state to the desired state at acontrolled rate. A Deployment also allows you to roll back to a previous version if something goes wrong during the update14.

The other options are incorrect because:

• A ReplicaSet is a Kubernetes object that ensures that a specified number of pod replicas are running at any given time. It does not provide any mechanism for updating or rolling back pods15.
• A Service is a Kubernetes object that defines a logical set of pods and a policy to access them. It does not provide any mechanism for updating or rolling back pods16.
• A Container is not a Kubernetes object, but rather a component of a Pod. A Pod is the smallest deployable unit of computing in Kubernetes. A Pod can contain one or more containers that share storage and network resources. A Pod does not provide any mechanism for updating or rolling back itself or its containers17.

References: Deployments, ReplicaSets, Services, Pods

Two components that are installed on the target cluster when VMware Tanzu Mission Control Data Protection is enabled are Velero and data protection extension. VMware Tanzu Mission Control Data Protection is a feature that allows users to backup and restore Kubernetes resources and persistent volumes across clusters using a centralized management platform6. To enable data protection for a cluster, users need to install Velero and data protection extension on the cluster7. Velero is an open source tool that performs backup and restore operations using custom resource definitions and controllers6. Data protection extension is a component that enhances Velero’s functionality by providing additional features such as backup scheduling, retention policy, backup hooks, restore hooks, and backup encryption8. References: Data Protection - VMware Docs, Protecting Data - VMware Docs, Enable Data Protection for a Cluster - VMware Docs

The Tanzu CLI is a command-line tool that enables users to interact with VMware Tanzu products and services. It must be installed upfront to deploy VMware Tanzu Kubernetes Grid management cluster, as it provides commands to create, configure, scale, upgrade, and delete management clusters on different platforms. The Tanzu CLI also allows users to create workload clusters from the management cluster, and to perform various operations on both types of clusters. References: VMware Tanzu CLI Documentation, [Deploying Management Clusters with the Tanzu CLI]

To visualize API connectivity and enable API protection in VMware Tanzu Service Mesh, the administrator needs to perform two steps:

• Activate API Discovery for the Global Namespace. This allows Tanzu Service Mesh to automatically discover the APIs signatures between microservices running inside or outside the mesh. API Discovery creates a custom API schema for each API that is close to OpenAPI spec 3.0. Tanzu Service Mesh graph renders the detected APIs in the Enforcing mode by default, which means that any new API is considered as a violated API unless accepted by the administrator1
• Create API Security Policy for the Global Namespace. This allows the administrator to block or allow layer 4 and layer 7 traffic, as well as create granular policies that provide API and data segmentation, OWASP 10 attack defense, schema validation, geofencing, data compliance, and egress controls. The administrator can create the API Security policy through the Tanzu Service Mesh Console UI or by using the Tanzu Service Mesh API Explorer2

References: 1: https://docs.vmware.com/en/VMware-Tanzu-Service-Mesh/services/tanzu-service-mesh-enterprise/GUID-E6FB9FB3-FDB3-4D2B-B5CB-614608EEF537.html  2: https://docs.vmware.com/en/VMware-Tanzu-Service-Mesh/services/tanzu-service-mesh-enterprise/GUID-5B635420-3BD2-4EC1-B67E-2015F991A91C.html

Two configurations that are valid for Zonal Supervisor Deployment are three-zone and one-zone. A Zonal Supervisor Deployment is a way of deploying the vSphere with Tanzu Supervisor Cluster across multiple vSphere clusters that are mapped to vSphere Zones1. A vSphere Zone is a logical grouping of vSphere clusters that share common characteristics, such as network connectivity, power source, or physical location2. A Zonal Supervisor Deployment provides high availability and fault tolerance for Kubernetes workloads by distributing them across different zones1. The supported configurations for Zonal Supervisor Deployment are:

• Three-zone: The Supervisor Cluster spans three vSphere clusters, each mapped to a different vSphere Zone. This configuration provides the highest level of availability and fault tolerance, as it can tolerate the failure of any one zone1.
• One-zone: The Supervisor Cluster runs on a single vSphere cluster that is mapped to a single vSphere Zone. This configuration is suitable for development or testing purposes, but does not provide any availability or fault tolerance guarantees1.

References: Requirements for Zonal Supervisor Deployment - VMware Docs, Create vSphere Zones for a Multi-Zone Supervisor Deployment - VMware Docs

The command that can be used to upgrade a VMware Tanzu Kubernetes Cluster that is managed by VMware Tanzu Mission Control is tmc cluster upgrade [version] . This command allows you to upgrade a managed cluster to a newer version of Kubernetes that is supported by Tanzu Mission Control5. The version flag is optional and specifies the target version of Kubernetes. If not specified, the command upgrades the cluster to the latest available version5. The clustername argument is required and specifies the name of the cluster to upgrade5. References: Upgrade Kubernetes on Your Cluster - VMware Docs

ClusterIP and NodePort are two Kubernetes Service types that are fulfilled natively by Kubernetes without requiring external integrations. ClusterIP exposes a service on a cluster-internal IP address that can only be accessed from within the cluster. NodePort exposes a service on a static port on each node’s IP address, and forwards the traffic to the corresponding ClusterIP service. Both ClusterIP and NodePort services are created by Kubernetes using iptables rules on the nodes, and do not depend on any external load balancers or DNS providers. References: Kubernetes Service Types Overview, Service | Kubernetes

VMware Aria Operations for Applications (formerly VMware Tanzu Observability) is a SaaS solution that collects and analyzes traces, metrics, and logs from various sources, including Tanzu Kubernetes Grid clusters, applications, and services. It provides a single source of truth for actionable insights into the performance, availability, and behavior of the entire application stack. It also enables users to create dashboards, alerts, and reports based on the collected data.

The other options are incorrect because:

• Watches defined infrastructure systems to keep track of health of resources is a description of VMware Tanzu Mission Control, which is another SaaS solution that provides centralized management and governance for Tanzu Kubernetes Grid clusters across multiple platforms.
• Automates the remediation of Kubernetes platform resources based on collected data is a description of VMware Tanzu Service Mesh, which is a service thatcreates an enterprise-class service mesh for consistent control and security for microservices, end users, and data.
• Tracks metrics, logs, and alerts based on specified thresholds is a partial description of VMware Aria Operations for Applications, but it does not mention the trace analysis and the single source of truth features.

References: VMware Tanzu for Kubernetes Operations Getting Started, VMware Aria Operations for Applications Documentation

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

Two statements about the NSX Advanced Load Balancer are correct:

• It can be configured as the VIP endpoint for the management cluster on vSphere. The VIP endpoint is the IP address that clients use to access the Kubernetes API server on the management cluster. By default, this IP address is assigned by DHCP, but it can also be configured manually or by using a load balancer. Using a load balancer provides high availability and scalability for the VIP endpoint. NSX Advanced Load Balancer can be used as the load balancer provider for the VIP endpoint by creating a virtual service that points to the control plane nodes of the management cluster5.
• It can be configured as a load balancer for workloads in the clusters that are deployed on vSphere. Workload clusters are Kubernetes clusters that run user workloads on vSphere with Tanzu. Workload clusters require a load balancer to expose services of type LoadBalancer to external clients. NSX Advanced Load Balancer can be used as the load balancer provider for workload clusters by deploying an Avi Kubernetes Service (AKS) pod on each cluster node. The AKS pod acts as an ingress controller that communicates with the NSX Advanced Load Balancer Controller and creates virtual services for each service of type LoadBalancer6.

The other options are incorrect because:

• It can only be used if Antrea CNI is installed on the workload cluster is false. Antrea is one of the supported Container Network Interface (CNI) plugins for workload clusters on vSphere with Tanzu, but it is not mandatory to use it with NSX Advanced Load Balancer. Other CNI plugins, such as Calico or Flannel, can also work with NSX Advanced Load Balancer7.
• It only supports the service type LoadBalancer is false. NSX Advanced Load Balancer supports other service types as well, such as ClusterIP and NodePort. These service types can be used to expose services within or across clusters without requiring an external load balancer8.
• It is natively integrated with Tanzu Kubernetes Grid Amazon Web Services EC2 deployments is false. NSX Advanced Load Balancer is not natively integrated with Tanzu Kubernetes Grid Amazon Web Services EC2 deployments. Tanzu Kubernetes Grid on AWS uses the AWS Elastic Load Balancing service as the default load balancer provider for both management and workload clusters9.

References: Configure the VIP Endpoint for the Management Cluster, Deploy and Configure NSX Advanced Load Balancer as a Load Balancer for Workload Clusters, Supported CNI Plugins, Service Types, Load Balancing on AWS