CEF. Assuming it refers to Supervisor CP... A. Can resize from vsphere client, but not on the inventory view https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-with-tanzu-installation-configuration/GUID-338F03BE-777F-464A-8A4B-A3786934D504.html B. No. That's on esxi C. True on any CP D. Do not run ANY k8s pods? Not application pods but sure some components like etcd E. Depends on the deployment. Supervisor is on the same network as VC https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-with-tanzu-concepts-planning/GUID-B156CDA6-B056-4D1C-BBC5-07D1A701E402.html F. True

C & E is correct. E. Control Plane VMs are connected to management network, too. D. maybe wrong, there must be some k8s pods running on the control plane VM. So C, E, F

CEF Supervisor Cluster Control Plane: The supervisor cluster deploys a set of three control plane VMs that provide API access to the supervisor cluster. The control plane VM serves as an endpoint for users to manage their namespaces using the familiar kubectl CLI. Control Plane VM Role: The control plane VMs run infrastructure services and pods for the supervisor cluster, similar to Kubernetes master nodes. Control Plane Networking: The control plane VMs use management, production, and cluster networks: • They connect to the floating IP address on the management network. • etcd communication between each control plane VM uses the management network. • Developers access infrastructure using a virtual IP address from the production network. • Pod control plane communication uses the cluster network. From VMware Cloud Foundation: Deploy, Configure, Manage [V5.0] Lesson Book

C: CP VMs expose the K8S API They do run infra services and pods for the supervisor cluster, so D is out E: They are connected to a Mgt portgroup F: They are deployed via VC

CP VMs expose the K8S API They do run infra services and pods for the supervisor cluster, so D is out They are connected to a Mgt portgroup They are deployed via VC

Review the linked docs below. obeythefist is correct.

It looks like everyone is wrong here, so here's what I believe to be the correct answers (C, E and F). Most importantly, this is one of those questions where it is easiest to eliminate the wrong answers, leaving the three correct ones. > A. They can be resized by administrators directly through vCenter Inventory View. No, you have to resize them in other ways: https://williamlam.com/2021/08/quick-tip-resizing-vsphere-with-tanzu-supervisor-control-plane-vms.html > B. They each run the Spherelet. No, it's very important to understand that a Spherelet and a Control Plane VM are different things. There are three load balanced control plane VMs in each workload cluster, no more, no less. However, every node runs its own Spherelet. The Spherelet is a service distinct from the control plane VM. What if you have 4 hosts in your cluster? > C. They each expose the Kubernetes API. Yes, that is the job of the control plane VMs. > D. They do not run any Kubernetes Pods. Yes, their job is not to run workloads.

BCE The three characteristics that are true of Control Plane VMs are: B. They each run the Spherelet. C. They each expose the Kubernetes API. E. They are connected to a Management portgroup. Control Plane VMs are VMs that run on the infrastructure and host the Kubernetes control plane components. They are deployed as part of a Supervisor Cluster in vSphere with Tanzu.