What open-source project enables automated lifecycle management of VMware vSphere Kubernetes Service (VKS) clusters?

• A.Cluster API
• B.Contour
• C.kubeadm
• D.Grafana

Comment: *

Name: *

Email: *

Verification: *

A Cloud Administrator initiates a Supervisor upgrade. The process hangs at 55% for an extended period.
The administrator checks the vCenter events and sees:
Event: Supervisor Upgrade Stalled
Detail: Waiting for Control Plane VM 'Supervisor-Control-Plane-VM-02' to power on.
Error: The operation failed due to a file lock on the datastore '[vsanDatastore]'.
Further investigation reveals that a backup job from a third-party tool is currently running on the old Control Plane VMs, holding a lock on the VM files.
What is the correct remediation to allow the upgrade to proceed? (Choose 2.)

• A.Migrate the Supervisor to a different datastore during the upgrade.
• B.Manually delete the 'Supervisor-Control-Plane-VM-02' from disk.
• C.Cancel the backup job to release the file locks.
• D.Restart the vCenter Server service.
• E.The upgrade process will automatically retry once the locks are released; no manual intervention is strictly required if the backup finishes within the timeout window, but cancelling is the immediate fix.

Comment: *

Name: *

Email: *

Verification: *

What is the standard procedure for upgrading the vSphere Supervisor Cluster to a newer version?

• A.The administrator must download an ISO image, mount it to each Control Plane VM, and run an upgrade script manually.
• B.The upgrade is initiated from the vSphere Client by selecting the Supervisor Cluster and choosing a target version, which triggers a rolling update of the Control Plane VMs and the Spherelet agents on the ESXi hosts.
• C.The upgrade requires a complete re-installation of the Supervisor Cluster; workload data must be backed up and restored manually.
• D.The upgrade is performed exclusively through the NSX Manager interface, as it controls the Supervisor networking.

Comment: *

Name: *

Email: *

Verification: *

A Cloud Administrator is optimizing the Supervisor configuration. They initially deployed the Supervisor with the NSX Advanced Load Balancer (Avi). However, users are reporting certificate warning errors when accessing the Supervisor Control Plane API endpoint.
Review the current status:
Status: Running
Config Status: Certificate Untrusted
[Certificate Details]
Subject: CN=192.168.10.50
Issuer: CN=192.168.10.50
Type: Self-signed
To resolve this and ensure compliance, the administrator needs to replace the machine SSL certificate.
Which specific actions are part of the correct procedure to replace the Supervisor certificate? (Choose
2.)

• A.Generate a new CSR (Certificate Signing Request) from the vSphere Client under "Workload Management" > "Supervisor" > "Configure" > "Certificates".
• B.Replace the certificate directly inside the Supervisor Control Plane VM using SSH and openssl commands.
• C.Upload the signed certificate chain and private key to the Supervisor configuration in the vSphere Client.
• D.Re-run the "Enable Workload Management" wizard to inject the new certificate.
• E.Replace the machine SSL certificate on the vCenter Server system; the Supervisor inherits this trust automatically.

Comment: *

Name: *

Email: *

Verification: *

A Platform Engineer is troubleshooting why a TKG cluster batch-processing is not scaling up, despite there being 50+ pods in the Pending state for over 30 minutes.
The engineer checks the autoscaler status annotations on the worker node pool: min-size: 3, max-size:
10. Current replicas: 5.
The engineer retrieves the logs from the CAPW (Cluster API Provider for vSphere) controller on the Supervisor and sees:
I1123 10:00:00.123 controller.go:100] Reconciling MachineSet "batch-processing-workers-md-0" E1123 10:00:00.125 controller.go:150] Failed to create Machine "batch-processing-workers-w9z4":
Quota "ns-resource-quota" exceeded.
Requested: cpu=4000m, memory=16Gi.
Used: cpu=20000m, memory=80Gi.
Limit: cpu=22000m, memory=88Gi.
Based on the logs, what is the root cause?

• A.The max-size annotation prevents scaling beyond 5 nodes.
• B.The Cluster Autoscaler is disabled.
• C.The pods are pending because they are requesting a Storage Class that does not exist.
• D.The vSphere Namespace resource limits (Quota) prevent the creation of new worker node VMs because the requested resources for the new node would exceed the defined Namespace limits.
• E.The ESXi hosts are physically out of capacity.

Comment: *

Name: *

Email: *

Verification: *