VMware 2V0-71.23 Online Practice Questions and Exam Preparation

VMware 2V0-71.23 Online Questions & Answers

• Question 31:

  Which two groups can be created to collect and manage objects in VMware Tanzu Service Mesh? (Choose two.)

  A. Node groups
  B. Cluster groups
  C. Security groups
  D. API groups
  E. Service groups
  A. Node groups
  E. Service groups

  ---

  Explanation/Reference:

  Node groups and service groups are two kinds of resource groups that can be created to collect and manage objects in VMware Tanzu Service Mesh. A resource group is a collection of cluster resources of a specific type that share specific characteristics. Resource groups help enforce policies and monitor the performance of resources in a single global namespace or across your entire organization7. A node group collects nodes that meet certain criteria, such as running in a specific region or having certain labels. A service group collects services that meet certain criteria, such as having a specific name prefix or belonging to a specific namespace. The other options are incorrect because: Cluster groups are not a valid kind of resource group in VMware Tanzu Service Mesh. Clusters are not considered as resources in Tanzu Service Mesh. Security groups are not a valid kind of resource group in VMware Tanzu Service Mesh. Security groups are used to define network access rules for resources in some cloud platforms8, but they are not part of Tanzu Service Mesh. API groups are not a valid kind of resource group in VMware Tanzu Service Mesh. API groups are used to organize Kubernetes resources into categories based on their API versions9, but they are not part of Tanzu Service Mesh. References: Resource Groups, Security Groups, API Groups

• Question 32:

  Which two are valid options for obtaining kubectl config file in Tanzu Kubernetes environment? (Choose two.)

  A. Use the command tubeccl vsphere login
  B. Download from vSphere Ul
  C. Download on the Supervisor Cluster Webpage
  D. Access from vCenter Server Appliance Management Interface
  E. Access from VMware Tanzu Mission Control
  B. Download from vSphere Ul
  E. Access from VMware Tanzu Mission Control

  ---

  Explanation/Reference:

  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

• Question 33:

  Which two Kubernetes Service types are fulfilled natively by Kubernetes without requiring external integrations? (Choose two.)

  A. ExternalName
  B. Ingress
  C. LoadBalancer
  D. NodePort
  E. ClusterIP
  D. NodePort
  E. ClusterIP

  ---

  Explanation/Reference:

  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

• Question 34:

  An administrator has a VMware Tanzu Kubernetes Grid management cluster named tanzu- mc0l which needs to be upgraded.

  Which command can be used to upgrade this cluster?

  A. kubectl management-cluster upgrade
  B. tanzu mc upgrade
  C. tanzu config use-context tanzu-mc01-admin@tanzu-mc01
  D. kubectl tanzu-mc01 upgrade
  B. tanzu mc upgrade

  ---

  Explanation/Reference:

  The tanzu mc upgrade command is used to upgrade a management cluster to a newer version of Tanzu Kubernetes Grid. The command requires the name of the management cluster as an argument, and optionally the version to upgrade to.

  For example, toupgrade the management cluster named tanzu-mc01 to version v1.4.0, the command would be:

  tanzu mc upgrade tanzu-mc01 --version v1.4.0

  The other options are incorrect because:

  kubectl management-cluster upgrade is not a valid command. The kubectl command is used to interact with Kubernetes clusters, not to upgrade them.

  tanzu config use-context tanzu-mc01-admin@tanzu-mc01 is a command to switch the current context to the admin context of the management cluster named tanzu- mc01. It does not upgrade the cluster.

  kubectl tanzu-mc01 upgrade is not a valid command. The kubectl command does not accept a cluster name as an argument, and there is no upgrade subcommand. References: VMware Tanzu for Kubernetes Operations Getting Started,

  Upgrading Management Clusters

• Question 35:

  Which statement about Tanzu Mission Control policies is correct?

  A. Policies can be configured using a tag selector to restrict the scope of the policy.
  B. Policies can only be applied to clustergroups.
  C. Policies allow management and operation of the security posture of Kubernetes clusters, and other organizational objects.
  D. Policies can be enforced using Kubernetes resources (NetworkPolicy, ResourceQuota etc) or using the Kyverno admission controller.
  C. Policies allow management and operation of the security posture of Kubernetes clusters, and other organizational objects.

  ---

  Explanation/Reference:

  Policies are one of the features of Tanzu Mission Control that allow you to manage the operation and security posture of your Kubernetes clusters and other organizational objects. Policies allow you to provide a set of rules that govern your

  organization and all the objects it contains. The policy types available in Tanzu Mission Control include access policy, image registry policy, network policy, quota policy, security policy, and custom policy. Policies can be applied at the

  individual, group, or organizational level to control access, image registries, networking, resource consumption, security context, and more18.

  The other options are incorrect because:

  Policies can be configured using a tag selector to restrict the scope of the policy is false. Policies can be configured using a label selector, not a tag selector, to include or exclude certain objects from the policy. A label is a key/value

  pairattached to a Kubernetes object that allows you to specify identifying attributes for that object. A selector provides the means to identify the objects that have a given label18.

  Policies can only be applied to clustergroups is false. Policies can be applied to various levels of the Tanzu Mission Control resource hierarchy, such as organization, cluster group, workspace, cluster, and namespace18. Policies can be

  enforced using Kubernetes resources (NetworkPolicy, ResourceQuota etc) or using the Kyverno admission controller is false. Policies are enforced by Tanzu Mission Control using its own admission controller and webhook server. Kyverno is

  an open-source policy engine for Kubernetes that is not related to Tanzu Mission Control.

  References: Policy-Driven Cluster Management, [Kyverno]

• Question 36:

  What are four policy types supported by VMware Tanzu Mission Control? (Choose four.)

  A. Security policy
  B. Pod security policy
  C. Access policy
  D. Cluster group policy
  E. Network policy
  F. Custom policy
  G. Workspace policy
  A. Security policy
  C. Access policy
  E. Network policy
  F. Custom policy

  ---

  Explanation/Reference:

  Four policy types that are supported by VMware Tanzu Mission Control are:

  Security policy: Security policies allow you to manage the security context in which deployed pods operate in your clusters by imposing constraints on your clusters that define what pods can do and which resources they have access to6.

  Access policy: Access policies allow you to use predefined roles to specify which identities (individuals and groups) have what level of access to a given resource7. Network policy: Network policies allow you to use preconfigured templates to

  define how pods communicate with each other and other network endpoints8. Custom policy: Custom policies allow you to implement additional business rules, using templates that you define, to enforce policies that are not already

  addressed using the other built-in policy types9.

  References: Policy-Driven Cluster Management - VMware Docs

• Question 37:

  Which steps are required to create a vSphere Namespace?

  A. In the vSghere web client, select Supervisor, select Namespaces tab. and click Create Namespace
  B. Create the Namespace usinq the Tanzu CLI
  C. In the vSphere web client, select Workload Management, select Namespaces tab. and click Create Namespace
  D. In the vSghere web client, select Supervisor, select Workload, select Namespaces tab.and click Create Namespace
  C. In the vSphere web client, select Workload Management, select Namespaces tab. and click Create Namespace

  ---

  Explanation/Reference:

  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

• Question 38:

  Which Kubernetes object must be used to be able to upgrade a pod without disrupting services?

  A. ReplicaSet
  B. Service
  C. Container
  D. Deployment
  D. Deployment

  ---

  Explanation/Reference:

  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

• Question 39:

  Which two are installed on the target cluster when VMware Tanzu Mission Control Data Protection is enabled? (Choose two.)

  A. VMware Tanzu Mission Control agent
  B. Velero
  C. FluentBit
  D. Data protection extension
  E. Antrea
  B. Velero
  D. Data protection extension

  ---

  Explanation/Reference:

  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

• Question 40:

  Which method describes how Kubernetes clusters are upgraded?

  A. Use rolling upgrade
  B. In-place upgrade of each node
  C. Use canary upgrade
  D. Deploy a new cluster with upgraded Kubernetes release
  A. Use rolling upgrade

  ---

  Explanation/Reference:

  A rolling upgrade is a method of upgrading a Kubernetes cluster without downtime by gradually replacing nodes or components with newer versions. A rolling upgrade ensures that there is no disruption to the availability and functionality of the cluster during the upgrade process. A rolling upgrade can be performed manually or using tools such as kubeadm or kops5. The other options are incorrect because: In-place upgrade of each node is a method of upgrading a Kubernetes cluster by stopping each node or component and updating it to the newer version. This method can cause downtime and disruption to the cluster during the upgrade process. Use canary upgrade is not a valid method of upgrading a Kubernetes cluster. A canary upgrade is a technique for deploying new versions of applications or services by gradually exposing them to a subset of users or traffic before rolling them out to everyone6. It is not applicable to cluster upgrades. Deploy a new cluster with upgraded Kubernetes release is not a method of upgrading a Kubernetes cluster, but rather creating a new one. This method canbe costly and time-consuming, as it requires migrating all the resources and configurations from the old cluster to the new one. References: Upgrade A Cluster, Canary deployments