VMware VMware Certifications 2V0-71.23 Questions & Answers

• Question 61:

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

  A. API Sep/er

  B. Scheduler

  C. etcd

  D. Kubelel

  Correct Answer: B

  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 62:

  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.

  Correct Answer: D

  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 63:

  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

  Correct Answer: A

  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