Weekend Special Limited Time 70% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code = simple70

Home
VMware
VMware Certified Specialist - vSphere with Tanzu 2022
5V0-23.20
VMware vSphere with Tanzu Specialist Questions and Answers

Pass the VMware Certified Specialist - vSphere with Tanzu 2022 5V0-23.20 Questions and answers with ExamsMirror

Practice at least 50% of the questions to maximize your chances of passing.

Exam 5V0-23.20 Premium Access

View all detail and faqs for the 5V0-23.20 exam

Go to Exam

378 Students Passed

97% Average Score

93% Same Questions

Viewing page 1 out of 4 pages

Viewing questions 1-10 out of questions

Questions # 1:

To which set of networks are the Supervisor Cluster nodes attached when deploying with an NSX-T network topology?

Options:

Frontend and Workload

Frontend and Management

Workload and Management

Management and NSX Overlay

Answer

Explanation

The Network Service has been extended to support the vSphere Distributed Switch (vDS). Start by configuring the switch with appropriate portgroups. Management will carry traffic between vCenter and the Kubernetes Control Plane (Supervisor Cluster control plane). As we will see in a moment, not having the built in Load Balancing capability of NSX means you will need to deploy your own load balancer externally from the cluster. We will give you a choice of integrated load balancers. The first one we support is HAProxy.

The Management network will also carry traffic between the supervisor cluster nodes and HAProxy. The Frontend network will carry traffic to the Load Balancer virtual interfaces. It must be routable from any device that will be a client for your cluster. Developers will use this to issue kubectl commands to the Supervisor cluster or their TKG clusters. You can have one or more Workload networks.

The primary Workload network will connect the cluster interfaces of the Supervisor cluster. Namespaces can be defined with their own Workload network allowing for isolation between development teams assigned different Namespaces. The Namespace assigned Workload Networks will connect the TKG cluster nodes in that Namespace.

Questions # 2:

When creating a Supervisor Namespace, which item must be added to ensure that the end user can consume the namespace?

Options:

Content Library

Permissions

Storage

Limits

Answer

Questions # 3:

The application development team plans to test a few CPU intensive applications. The virtualization team is concerned about these applications impacting other teams.

How should the team manage this problem?

Options:

Set a CPU reservation on the Namespace Resource Pool in vCenter.

Add a CPU limit to the Namespace Resource Pool in vCenter.

Set a network policy to limit network bandwidth within the vSphere Namespace.

Add a CPU limit to the vSphere Namespace for the development team.

Answer

Questions # 4:

Which is a valid version change for a Tanzu Kubernetes cluster running Kubernetes version 1.16.7?

Options:

Upgrade one major version (e.g.. 2.0.1)

Upgrade two minor versions (e.g., 1.18.0)

Downgrade one patch version (e.g.. 1.16.5)

Upgrade one minor version (e.g.. 1.17.0)

Answer

Explanation

Be aware of the following constraints when upgrading your cluster.

You can upgrade a cluster up to one minor version of Kubernetes from its current version. If necessary, you can perform subsequent upgrades to move the version forward.

Upgrading your version of Kubernetes is a one-way operation. You cannot subsequently downgrade the Kubernetes version, or undo an upgrade.

Questions # 5:

An organization is preparing to deploy vSphere with Tanzu and will be using the vSphere Networking stack.

How should the administrator allocate management network IP addresses for the Kubernetes Control Plane within the Supervisor Cluster?

Options:

Five IP addresses are required, one for each of the Control Plane VMs. one for the floating IP address of the Control Plane VM, and one spare for performing rolling cluster upgrades

Four IP addresses are required, one for each of the Control Plane VMs and one spare for performing rolling cluster upgrades

Three IP addresses are required, one for each of the Control Plane VMs

Six IP addresses are required, one for each of the Control Plane VMs, one for the floating IP address of the Control Plane VM. one for performing rolling cluster upgrades and one for the image Registry VM.

Answer

Explanation

Static IPs for Kubernetes control plane VMs

Block of 5A block of 5 consecutive static IP addresses to be assigned to the Kubernetes control plane VMs in the Supervisor Cluster.

Questions # 6:

Which step is necessary in order to allocate storage to a newly created namespace?

Options:

Assign a VM Storage Policy

Assign permissions to users

Define resource limits

Add a content library

Answer

Questions # 7:

Which two networks are used to attach Supervisor Cluster control plane VMs when using the vSphere networking stack? (Choose two.)

Options:

vMotion

Frontend

Primary workload

Management

Non-primary workload

Answer

D, E

Questions # 8:

Which two capabilities are associated with vSphere Pod? (Choose two.)

Options:

Compatibility with vSphere vMotion

Compatibility with vSphere performance charts

Compatibility with NSX-V Datacenter

Compatibility with vSphere HA and DRS

Compatibility with Windows and Linux kernels

Answer

C, D

Explanation

vSphere Pods are only supported on Supervisor Clusters that use NSX-T Data Center as their networking stack.

Resource Management. vSphere DRS handles the placement of vSphere Pods on the Supervisor Cluster.

Questions # 9:

Which two container network interfaces (CNIs) are supported with Tanzu Kubernetes clusters created by the Tanzu Kubernetes Grid Service? (Choose two )

Options:

NSX-T

Weave Net

Flannel

Antrea

Calico

Answer

D, E

Explanation

https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-A7756D67-0B95-447D-A645-E2A384BF8135.html

A Tanzu Kubernetes cluster provisioned by the Tanzu Kubernetes Grid Service supports two CNI options: Antrea (default) and Calico. Both are open-source software that provide networking for cluster pods, services, and ingress.

Tanzu Kubernetes clusters provisioned by the Tanzu Kubernetes Grid Service support the following Container Network Interface (CNI) options:

Antrea

Calico

Explanation

Tanzu Kubernetes Grid Service CNI

Tanzu Kubernetes Grid Service supports Antrea and Calico as container network interfaces (CNI).

The default CNI in vSphere 7 Update 1 is Antrea.

Antrea is a VMware-supported, open source, Kubernetes-native project that implements the container network interface (CNI) and Kubernetes network policy, providing network connectivity and security for pod workloads. Antrea extends the benefit of programmable networks from Open vSwitch (OVS) to Kubernetes.

For more information about Antrea, see https://antrea.io/

Questions # 10:

Which object provides user access to applications running on vSphere with Tanzu?

Options:

External load balancer

vSphere Distributed Switch

Round-robin DNS

Internal load balancer

Answer

Explanation

External HTTP(S) Load Balancing is a proxy-based Layer 7 load balancer that enables you to run and scale your services behind a single external IP address.