Restart or Recover Failed VKS Upgrades VCAP-VCF-VKS Practice Questions (Page 1)

Questions 1–5

1. 1application · medium

   A VKS administrator is upgrading a cluster from v1.28 to v1.29. The upgrade progress bar in the VKS UI stalls at 60% for over 30 minutes, and the vSphere Client shows that the control plane VM is still powered on but the kube-apiserver process is not responding to health checks. Which action should the administrator take FIRST to determine the cause of the failure?

   • AForce-power off the control plane VM and power it back on to restart the kube-apiserver process.
   • BCheck the VKS upgrade logs on the Supervisor Cluster for the specific error message and the last completed step.
   • CImmediately re-run the upgrade command from the beginning to overwrite the stalled state.
   • DDelete the control plane VM and let the Supervisor Cluster recreate it automatically.
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   Which action is appropriate to recover from a partial VKS upgrade where the control plane is upgraded but the worker nodes are not?

   • ARoll back the control plane to the previous version
   • BRe-run the upgrade to complete the worker node upgrade
   • CDelete the worker nodes and recreate them
   • DManually upgrade each worker node using kubectl
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   After recovering a failed VKS cluster upgrade, the administrator needs to validate that the environment is fully operational. The cluster is now running version v1.29.0. Which set of checks should the administrator perform to confirm post-recovery integrity?

   • AVerify all nodes are Ready, all control plane pods are Running, and the VKS UI shows the cluster as Healthy.
   • BVerify that all worker nodes are Ready and that the kubelet is running on each node.
   • CVerify that the etcd cluster is healthy and that the kube-apiserver is responding to requests.
   • DVerify that the cluster version is v1.29.0 and that no error messages appear in the VKS UI.
   Reveal Solution Discussion Select an answer first
5. 4application · medium

   A VKS administrator is monitoring a cluster upgrade and notices that the upgrade has been in the 'Upgrading' state for 45 minutes, which is longer than expected. The VKS UI does not show an error, but the cluster's worker nodes are all showing as 'NotReady'. Which symptom BEST indicates that the upgrade has failed?

   • AThe VKS UI does not show an error message.
   • BThe cluster version is still showing the old version in the VKS UI.
   • CThe worker nodes are all showing as 'NotReady'.
   • DThe upgrade has been in the 'Upgrading' state for 45 minutes.
   Reveal Solution Discussion Select an answer first
6. 5expert · hard

   A VKS cluster upgrade failed, and the cluster is in a partial state. The control plane VMs are running the new version, but the worker nodes are still running the old version. The administrator attempts to re-run the upgrade, but it fails immediately with an error indicating that the cluster is in an inconsistent state. What is the BEST next step?

   • ARestore the cluster from a backup taken before the upgrade.
   • BDelete the cluster and recreate it with the target version.
   • CCheck the upgrade logs to identify the specific inconsistency and follow the recommended recovery procedure.
   • DManually upgrade all worker nodes using kubeadm.
   Reveal Solution Discussion Select an answer first