Free VMware 5V0-31.22 Practice Exam with Questions & Answers | Set: 4

According to VMware Cloud Foundation Specialist (v2) Exam1, one of the objectives is to “Describe how to expand an existing NSX-T Edge cluster”. The exam guide also states that “SDDC Manager provides a single point of management for password rotation” and that “password rotation must be performed through SDDC Manager”.

This is because an ingress is a Kubernetes resource that exposes HTTP and HTTPS routes from outside the cluster to services within the cluster1. An ingress can use a routable CIDR range to assign IP addresses to the ingress controllers that handle the traffic routing.

https://docs.vmware.com/en/VMware-Cloud-Foundation/services/vcf-developer-ready-infrastructure-v1/GUID-AF178A31-D09A-4265-89FD-5987D1B36757.html

This is because according to VMware documentation2, these are some of the components that are configured as part of the Supervisor Cluster control plane after enabling Workload Management on a VMware Cloud Foundation Workload Domain:

• Tanzu Kubernetes Grid Service: This service enables you to create and manage Tanzu Kubernetes clusters on vSphere with Tanzu.
• Kubernetes Grid Orchestrator: This component manages the lifecycle of Tanzu Kubernetes clusters on vSphere with Tanzu.
• Spherelet: This component runs on each ESXi host and acts as a kubelet agent that communicates with the Supervisor Cluster control plane.

https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/com.vmware.vcf.vxrail.doc/GUID-E8D0A432-8573-4DF5-9330-A4FE15F74128.html

Prerequisites

A VI workload domain must be deployed.

An Workload Management ready NSX Edge cluster must be deployed on the workload domain.

You must select Workload Management on the Use Case page of the Add Edge Cluster wizard. See step 6 in Deploy an NSX Edge Cluster.

All hosts in the vSphere cluster for which you enable Workload Management must have a vSphere with Tanzu license.

Workload Management requires a vSphere cluster with a minimum of three ESXi hosts.

The following IP address subnets must be defined:

A non-routable subnet for pod networking, minimum of a /22 subnet.

A non-routable subnet for Service IP addresses, minimum of a /24 subnet

A routable subnet for ingress, minimum of a /27 subnet

A routable subnet for egress, minimum of a /27 subnet