VMware 2V0-71.23 Online Practice Questions and Exam Preparation

VMware 2V0-71.23 Online Questions & Answers

• Question 1:

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

  Which layer of controllers is correct?

  A. Virtual Machine Service, Tanzu Kubernetes Grid and Cluster API
  B. Authentication webhook. Container Storaqe Support, Cloud Provider Implementation
  C. Aria integration Service, Tanzu Cluster API and Tanzu Container Network Controller
  D. VMware Tanzu Mission Control Connection agent. Cluster API and Kubernetes Connection Agent
  A. Virtual Machine Service, Tanzu Kubernetes Grid and Cluster API

  ---

  explanation:

  Explanation/Reference:

  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

• Question 2:

  What is the purpose of a service mesh?

  A. Provides dynamic application load balancing and autoscaling across multiple clusters and multiple sites.
  B. Provides a centralized, global routing table to simplify and optimize traffic management.
  C. Provides service discovery across multiple clusters.
  D. Provides an infrastructure layer that makes communication between applications possible, structured, and observable.
  D. Provides an infrastructure layer that makes communication between applications possible, structured, and observable.

  ---

  explanation:

  Explanation/Reference:

  A service mesh is a dedicated infrastructure layer that you can add to your applications to provide capabilities like observability, traffic management, and security, without adding them to your own code. A service mesh consists of network proxies paired with each service in an application and a set of management processes. The proxies are called the data plane and the management processes are called the control plane. The data plane intercepts calls between different services and processes them; the control plane is the brain of the mesh that configures and monitors the data plane1. A service mesh makes communication between applications possible, structured, and observable by providing features such as load balancing, service discovery, encryption, authentication, authorization, routing, retries, timeouts, fault injection, metrics, logs, and traces2. The other options are incorrect because: Provides dynamic application load balancing and autoscaling across multiple clusters and multiple sites is a description of VMware Tanzu Service Mesh Global Namespaces feature3, which is built on top of a service mesh. It is not the purpose of a service mesh in general. Provides a centralized, global routing table to simplify and optimize traffic management is a description of VMware Tanzu Service Mesh Global Mesh Network feature4, which is also built on top of a service mesh. It is not the purpose of a service mesh in general. Provides service discovery across multiple clusters is a partial description of a service mesh, but it does not capture the full scope of its purpose. Service discovery is one of the features that a service mesh provides, but it is not the only one. References: What's a service mesh?, The Istio service mesh, Service mesh - Wikipedia

• Question 3:

  What is the Kubernetes component that is responsible for workload creation?

  A. API Sep/er
  B. Scheduler
  C. etcd
  D. Kubelel
  B. Scheduler

  ---

  explanation:

  Explanation/Reference:

  The Scheduler is the Kubernetes component that is responsible for workload creation. The Scheduler is responsible for assigning pods to nodes based on various factors, such as resource availability, node affinity, taints and tolerations, and pod priority. The Scheduler watches for newly created pods that have no node assigned, and selects a suitable node for them to run on. The Scheduler then informs the API server of its decision, and the API server binds the pod to the node. References: Scheduling | Kubernetes, Kubernetes Components | Kubernetes

• Question 4:

  Which three can be configured in a VM Class in VMware vSphere with Tanzu? (Choose three.)

  A. Network
  B. Operating system
  C. CPU
  D. Memory
  E. PCI devices
  F. Storage
  C. CPU
  D. Memory
  F. Storage

  ---

  explanation:

  Explanation/Reference:

  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]

• Question 5:

  What are three capabilities of VMware Aria Operations for Applications (formerly known as Tanzu Observability)? (Choose three.)

  A. Create Alerts
  B. Set Application Container security policy
  C. Set Service Level Objectives
  D. Create Kubernetes Clusters
  E. Create Charts and Dashboards
  F. Create Queries
  A. Create Alerts
  E. Create Charts and Dashboards
  F. Create Queries

  ---

  explanation:

  Explanation/Reference:

  VMware Aria Operations for Applications (formerly known as Tanzu Observability) is a unified observability platform that provides full-stack visibility using metrics, traces, and logs across distributed applications, application services, container services, and multi-cloud environments. Some of the capabilities of VMware Aria Operations for Applications are: Create alerts: Users can monitor for certain behaviors and get smart notifications based on query conditions. Users can create alerts independently or directly from charts, and use advanced and accurate alerting powered by AI/analytics and query language1. Create charts and dashboards: Users can visualize their data based on query results in various chart types (such as line plot, point plot, table, pie chart, etc.) and organize them in dashboards. Users can also interact with charts and dashboards in real time, such as zoom in, zoom out, change the time window, change the focus, and so on1. Create queries: Users can use the Wavefront Query Language (WQL) to extract the information they need from their data. Users can use the Chart Builder for easy query creation or the Query Editor for advanced query editing. Users can also use functions, operators, variables, macros, and expressions to manipulate their data1. References: VMware Aria Operations for Applications Documentation, Unified Observability Platform by VMware Aria Operations for Applications

• Question 6:

  What Kubernetes project does vSphere with Tanzu Supervisor Cluster use to automate the lifecycle management of Tanzu Kubernetes Grid Clusters?

  A. Grafana
  B. Cluster API
  C. Contour
  D. Kubeadm
  B. Cluster API

  ---

  explanation:

  Explanation/Reference:

  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 platforms5. 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

• Question 7:

  What project does Contour leverage for the data plane?

  A. NSX Load Balancer
  B. Istio
  C. Envoy
  D. Prometheus
  C. Envoy

  ---

  explanation:

  Explanation/Reference:

  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

• Question 8:

  A Tanzu Mission Control administrator would like to enforce the following container controls:

  1.

  Only allows container images that match the specified names or tags.

  2.

  Ensure that the container image is not tampered with.

  Which type of policy can be used?

  A. Access
  B. Security
  C. Image Security
  D. Image Registry
  E. Network
  C. Image Security

  ---

  explanation:

  Explanation/Reference:

  The type of policy that can be used to enforce the container controls is image security. Image security policies allow users to define rules for validating container images before they are deployed on clusters. Users can specify image names, tags, signatures, or digests to whitelist or blacklist images based on their source and integrity. Users can also enable or disable image scanning for vulnerabilities and configure the severity threshold for admission decisions. References: Image Security Policy - VMware Docs, Image Policy - VMware Docs

• Question 9:

  Which two statements about the NSX Advanced Load Balancer are correct? (Choose two.)

  A. It can only be used if Antrea CNI is installed on the workload cluster.
  B. It can be configured as the VIP endpoint for the management cluster on vSphere.
  C. It only supports the service type LoadBalancer.
  D. It is natively integrated with Tanzu Kubernetes Grid Amazon Web Services EC2 deployments.
  E. It can be configured as a load balancer for workloads in the clusters that are deployed on vSphere.
  B. It can be configured as the VIP endpoint for the management cluster on vSphere.
  E. It can be configured as a load balancer for workloads in the clusters that are deployed on vSphere.

  ---

  explanation:

  Explanation/Reference:

  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

• Question 10:

  Where can an administrator register the vSphere management cluster in VMware Tanzu Mission Control?

  A. In the VMware Tanzu Mission Control web console or CLI
  B. In the vSphere Management Cluster with Jcubeccl
  C. In the vSphere Client - Workload Cluster settings
  D. In the vSphere Namespace with Jcubeccl
  A. In the VMware Tanzu Mission Control web console or CLI

  ---

  explanation:

  Explanation/Reference:

  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