VMware 2V0-71.23 Online Practice Questions and Exam Preparation

VMware 2V0-71.23 Online Questions & Answers

• Question 51:

  What is the object in Kubernetes used to grant permissions to a cluster wide resource?

  A. ClusterRoleBinding
  B. RoleBinding
  C. RoleReference
  D. ClusterRoleAccess
  A. ClusterRoleBinding

  ---

  Explanation/Reference:

  The object in Kubernetes used to grant permissions to a cluster-wide resource is ClusterRoleBinding. A ClusterRoleBinding is a cluster-scoped object that grants permissions defined in a ClusterRole to one or more subjects, such as users, groups, or service accounts5. A ClusterRole is a cluster-scoped object that defines a set of permissions on cluster-scoped resources (like nodes) or namespaced resources (like pods) across all namespaces5. For example, a ClusterRoleBinding can be used to allow a particular user to run kubectl get pods --all-namespaces by granting them the permissions defined in a ClusterRole that allows listing pods in any namespace6. References: Using RBAC Authorization | Kubernetes, Cluster Roles and Cluster Roles Binding in Kubernetes | ANOTE.DEV

• Question 52:

  Which statement is true about Tanzu package CLI plugin?

  A. It cannotbe used to add additional package repositories apart from tanzu-standard.
  B. It can be used to manage packages in public repositories.
  C. It is intended only for CLI-managed packages.
  D. It can be used to install auto-managed packages.
  C. It is intended only for CLI-managed packages.

  ---

  Explanation/Reference:

  The Tanzu package CLI plugin is a tool that allows users to install and manage Tanzu packages on their clusters. Tanzu packages are Kubernetes resources that encapsulate the deployment and configuration of software components, such as Contour, Prometheus, Grafana, and more1. The Tanzu package CLI plugin is intended only for CLI- managed packages, which are packages that users can install and update manually using the Tanzu CLI commands2. The Tanzu package CLI plugin cannot be used to install or manage auto-managed packages, which are packages that are automatically installed and updated by Tanzu Kubernetes Grid as part of the cluster lifecycle2. The other options are incorrect because: It cannot be used to add additional package repositories apart from tanzu-standard is false. The Tanzu package CLI plugin can be used to add, list, update, or delete package repositories, which are sources of Tanzu packages3. Users can add custom package repositories or use the default tanzu-standard repository that comes with Tanzu Kubernetes Grid4. It can be used to manage packages in public repositories is false. The Tanzu package CLI plugin can only be used to manage packages in the repositories that are added to the target cluster3. Users cannot use the Tanzu package CLI plugin to manage packages in public repositories that are not added to the cluster. It can be used to install auto-managed packages is false. As mentioned above, the Tanzu package CLI plugin cannot be used to install or manage auto-managed packages. References: Tanzu Packages, Tanzu Package Types, tanzu package repository, Add a Package Repository

• Question 53:

  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/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 54:

  Which two methods can be used to install Fluent Bit on a VMware Tanzu Kubernetes Grid cluster? (Choose two.)

  A. Install Fluent Bit using Tanzu CLI login plugin
  B. Install Fluent Bit using VMware Tanzu Kubernetes Grid Installer Interface
  C. Install Fluent Bit from VMware Tanzu Mission Control
  D. Install Fluent Bit from VMware vSphere Client
  E. Install Fluent Bit using Tanzu CLI package plugin
  C. Install Fluent Bit from VMware Tanzu Mission Control
  E. Install Fluent Bit using Tanzu CLI package plugin

  ---

  Explanation/Reference:

  VMware Tanzu Mission Control and Tanzu CLI package plugin are two methods that can be used to install Fluent Bit on a VMware Tanzu Kubernetes Grid cluster. VMware Tanzu Mission Control is a centralized management platform for Kubernetes clusters across different environments. It allows users to install Fluent Bit on any attached cluster from the web console or the CLI, and configure the output plugins for log forwarding. Tanzu CLI package plugin is a command-line tool that enables users to interact with VMware Tanzu packages and services. It allows users to install Fluent Bit from a package repository on any standalone management or workload cluster, and configure the output plugins for log forwarding. References: Install Fluent Bit for Log Forwarding - VMware Docs, Implement Log Forwarding with Fluent Bit - VMware Docs

• Question 55:

  What are two services that require Transport Layer Security (TLS) certificates to provide encryption in VMware Tanzu Service Mesh? (Choose two.)

  A. Internal Service
  B. Proxy Service
  C. Certificate Authority (CA) Service D Public Service
  D. External Service
  C. Certificate Authority (CA) Service D Public Service
  D. External Service

  ---

  Explanation/Reference:

  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,

• Question 56:

  What Kubernetes objects are vSphere with Tanzu storage polices converted to?

  A. Quota policies
  B. Storage classes
  C. Persistent volumes
  D. Storage claims
  B. Storage classes

  ---

  Explanation/Reference:

  vSphere with Tanzu storage policies are converted to storage classes when they are assigned to namespaces. A storage class is a Kubernetes object that defines a set of parameters for provisioning persistent volumes1. A storage policy is a vSphere object that defines thecharacteristics of the underlying storage for a given workload2. When a vSphere administrator assigns a storage policy to a namespace, vSphere with Tanzu automatically creates a corresponding storage class in the namespace with the same name as the storage policy3. The storage class references the storage policy ID and allows DevOps engineers to use the storage policy for dynamic provisioning of persistent volumes3. References: Storage Classes - Kubernetes, Create Storage Policies for vSphere with Tanzu - VMware Docs, Assign Storage Policies to Namespaces - VMware Docs

• Question 57:

  Which command can be used to upgrade a VMware Tanzu Kubernetes Cluster that is managed by VMware Tanzu Mission Control?

  A. tmc cluster upgrade [version]
  B. tmc cluster update [clustername] [flags]
  C. tmc cluster tanzupackage install update [version]
  D. tmc cluster upgrade [version]
  A. tmc cluster upgrade [version]

  ---

  Explanation/Reference:

  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

• Question 58:

  Which two statements describe Kubernetes observability characteristics? (Choose two.)

  A. It provides network insight and detailed Kubernetes network topology view
  B. Provides visibility into Kubernetes clusters for troubleshooting and impact assessment
  C. It observes the code of the applications running in Kubernetes environment
  D. Collects real-time metrics from all layers of Kubernetes
  E. Automatically heals Kubernetes workloads after an issue has been observed
  B. Provides visibility into Kubernetes clusters for troubleshooting and impact assessment
  D. Collects real-time metrics from all layers of Kubernetes

  ---

  Explanation/Reference:

  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?

• Question 59:

  Which two StorageClass objects are supported by the VMware Tanzu Kubernetes Grid? (Choose two.)

  A. Azure Glacier
  B. vSphere Cloud Native Storage (CNS)
  C. Linux Remote File Services
  D. Samba
  E. Amazon EBS
  B. vSphere Cloud Native Storage (CNS)
  E. Amazon EBS

  ---

  Explanation/Reference:

  VMware Tanzu Kubernetes Grid supports StorageClass objects for different storage types, provisioned by Kubernetes internal ("in-tree") or external ("out-of-tree") plug- ins. Two of the supported storage types are vSphere Cloud Native Storage (CNS) and Amazon EBS. vSphere Cloud Native Storage (CNS) is a vSphere feature that provides persistent storage for Kubernetes clusters running on vSphere 6.7 or later. CNS integrates with the vSphere Container Storage Interface (CSI) driver to dynamically provision persistent volumes backed by First Class Disks on a datastore1. Amazon EBS is a block storage service that provides persistent storage for Amazon EC2 instances. EBS volumes can be attached to EC2 instances as block devices, and can be used to create persistent volumes for Kubernetes clusters running on AWS2. Both CNS and EBS support dynamic provisioning of persistent volumes using StorageClass objects with the provisioner field set to csi.vsphere.vmware.com and kubernetes.io/aws-ebs respectively12. References: Back Up and Restore Cluster Workloads - VMware Docs, Amazon Elastic Block Store (EBS) - Amazon Web Services

• Question 60:

  Which VMware product UI allows browsing Global Namespace Topology?

  A. NSX Advanced Load Balancer
  B. NSX
  C. Tanzu Service Mesh Advanced
  D. Tanzu Mission Control
  C. Tanzu Service Mesh Advanced

  ---

  Explanation/Reference:

  VMware Tanzu Service Mesh Advanced is the VMware product UI that allows browsing Global Namespace Topology. A Global Namespace is a logical group of services that span multiple clusters and clouds, providing consistent service

  discovery, security, and observability10. A Global Namespace Topology is a graphical representation of the services and their connections in a Global Namespace, showing the key metrics and health status of each service11. To browse the

  Global Namespace Topology, an administrator can use the Tanzu Service Mesh Console, which is the web-based user interface for managing Tanzu Service Mesh12.

  The other options are incorrect because:

  NSX Advanced Load Balancer is a VMware product that provides load balancing, web application firewall, and container ingress services for applications across various data centers and clouds13. It does not allow browsing Global

  Namespace Topology.

  NSX is a VMware product that provides network virtualization and security for applications across various data centers and clouds. It does not allow browsing Global Namespace Topology.

  Tanzu Mission Control is a VMware product that provides centralized management and governance for Kubernetes clusters across multiple teams and clouds. It does not allow browsing Global Namespace Topology.

  References: Global Namespaces, View the Topology of Services in a Global Namespace or a Cluster, Tanzu Service Mesh Console Overview, NSX Advanced Load Balancer Overview, [NSX-T Data Center Overview], [Tanzu Mission Control

  Overview]