VMware 2V0-71.23 Online Practice Questions and Exam Preparation

VMware 2V0-71.23 Online Questions & Answers

• Question 1:

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

  Which is a prerequisite for cert-manager installation?

  A. Download the latest Tanzu Kubernetes Grid OVAs for the OS and Kubernetes version
  B. Obtain the admin credentials of the target workload cluster
  C. Run the canzu login command tosee an interactive list of management clusters
  D. After importing the cert-manager OVA, a conversion into virtual machine template must be performed
  B. Obtain the admin credentials of the target workload cluster

  ---

  Explanation/Reference:

  A prerequisite for cert-manager installation is to obtain the admin credentials of the target workload cluster. Cert-manager is a tool that automates the management and issuance of TLS certificates within Kubernetes clusters3. To install cert-manager, users need to have access to the cluster where they want to deploy it, and have the necessary permissions to create resources such as namespaces, custom resource definitions, deployments, services, and secrets3. Users can obtain the admin credentials of the target workload cluster by using the tanzu cluster kubeconfig get command with the --admin option4. This command generates a kubeconfig file that contains the admin credentials for the cluster, which can be used to authenticate with the cluster and perform cert-manager installation4. References: Installation - cert-manager Documentation, Deploy Workload Clusters - VMware Docs

• Question 3:

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

  What are three VMware products that VMware Tanzu Kubernetes Grid natively integrates with? (Choose three.)

  A. NSX Advanced Load Balancer
  B. NSX-T Data Center
  C. BOSH
  D. vSphere with VMware Tanzu
  E. vRealize Network Insight
  F. Tanzu Mission Control
  A. NSX Advanced Load Balancer
  B. NSX-T Data Center
  D. vSphere with VMware Tanzu

  ---

  Explanation/Reference:

  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

• Question 5:

  Which Kubernetes object controls what traffic is allowed to and from selected pods and network endpoints?

  A. Ingress
  B. NetworkPolicv
  C. PodSecurityPolicy
  D. ISecret
  B. NetworkPolicv

  ---

  Explanation/Reference:

  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

• Question 6:

  Which statement describes a Global Namespace in VMware Tanzu Service Mesh?

  A. Apply a single policy to multiple namespaces across multiple clusters.
  B. Automatic placement of the workload to any global cluster based on traffic demand.
  C. Define an application boundary and provides consistent traffic routing, connectivity, resiliency, and security for applications across multiple clusters.
  D. Provide distributed ingress and egress services to support multiple namespaces across multiple clusters.
  C. Define an application boundary and provides consistent traffic routing, connectivity, resiliency, and security for applications across multiple clusters.

  ---

  Explanation/Reference:

  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

• Question 7:

  Which set of tools can be used to attach a Kubernetes cluster to VMware Tanzu Mission Control?

  A. Tanzu CLI and VMware vSphere Web Ul
  B. Tanzu CLI and VMware Tanzu Mission Control Web Ul
  C. kubectl and VMware vSphere Web Ul
  D. kubectl and VMware Tanzu Mission Control Web Ul
  D. kubectl and VMware Tanzu Mission Control Web Ul

  ---

  Explanation/Reference:

  The set of tools that can be used to attach a Kubernetes cluster to VMware Tanzu Mission Control are kubectl and VMware Tanzu Mission Control Web Ul. kubectl is a command-line tool that allows users to interact with Kubernetes clusters. VMware Tanzu Mission Control Web Ul is a graphical user interface that allows users to manage their clusters and policies. To attach a cluster, users need to use both tools. First, they need to use the web console to select the cluster group and generate a YAML manifest for the cluster. Then, they need to use kubectl to apply the manifest on the cluster and install the cluster agent extensions that enable communication with Tanzu Mission Control. References: Attach a Cluster -VMware Docs, What Happens When You Attach a Cluster

• Question 8:

  Which two configurations are valid for Zonal Supervisor Deployment? (Choose two.)

  A. five-zone
  B. seven-zone
  C. three-zone
  D. two-zone
  E. one-zone
  C. three-zone
  E. one-zone

  ---

  Explanation/Reference:

  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

• Question 9:

  An administrator set the following value:ENABLE_AUDIT_LOGGING=trueduring a cluster deployment. What was the purpose of this setting?

  A. Log metadata about all requests made to the Kubernetes API server.
  B. Enable log redirection to external logging server by Fluent Bit.
  C. Run scripts that collect Kubernetes API output,node logs, and node command-line output.
  D. Activate the kubectl describe command for CustomResourceDefinitions (CRDs) introduced byCluster API.
  A. Log metadata about all requests made to the Kubernetes API server.

  ---

  Explanation/Reference:

  The purpose of setting ENABLE_AUDIT_LOGGING=true during a cluster deployment is to log metadata about all requests made to the Kubernetes API server. This enables auditing of the cluster activities and helps with security and compliance. The audit logs are stored in /var/log/kubernetes/audit.log on the control plane node and can be accessed by the cluster administrator. The audit logs are generated based on an audit policy file that defines what events should be recorded and what data they should include12 References: 1: https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-Grid/1.6/vmware- tanzu-kubernetes-grid-16/GUID-troubleshooting-tkg-audit-logging.html 2: https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/

• Question 10:

  What is the role of the Tanzu Kubernetes Grid Service?

  A. It provides declarative, Kubernetes-style APIs for cluster creation, configuration, and management.
  B. It provides a declarative, Kubernetes-style API for management of VMs and associated vSphere resources.
  C. It provisions an extension inside the Kubernetes cluster to validate user authentication tokens.
  D. It provisions Kubernetes clusters that integrate with the underlying vSphere Namespace resources and Supervisor Services.
  D. It provisions Kubernetes clusters that integrate with the underlying vSphere Namespace resources and Supervisor Services.

  ---

  Explanation/Reference:

  The role of the Tanzu Kubernetes Grid Service is to provision Kubernetes clusters that integrate with the underlying vSphere Namespace resources and Supervisor Services. The Tanzu Kubernetes Grid Service is a component of vSphere with Tanzu that provides self-service lifecycle management of Tanzu Kubernetes clusters3. A Tanzu Kubernetes cluster is an opinionated installation of Kubernetes that runs on top of the Supervisor Cluster and inherits its capabilities, such as storage integration, pod networking, load balancing, authentication, and authorization4. The Tanzu Kubernetes Grid Service exposes three layers of controllers to manage the lifecycle of a Tanzu Kubernetes cluster: Cluster API, Virtual Machine Service, and Tanzu Kubernetes Release Service3. References: Tanzu Kubernetes Grid Service Architecture - VMware Docs, What Is a Tanzu Kubernetes Cluster? - VMware Docs