Diagnose and Resolve Supervisor and VKS Cluster Provisioning, Connectivity, or Namespace Errors VCAP-VCF-SUPPORT Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   During vSphere Supervisor provisioning, the workflow fails at the network step. Which component must be correctly configured for the Supervisor to obtain its API server endpoint and pod/service CIDR ranges?

   • AA distributed virtual switch with a VLAN-backed port group
   • BA standard virtual switch with a static port group
   • CA workload network with a configured IP address pool
   • DA NSX-T Data Center segment with DHCP enabled
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   A vSphere Supervisor provisioning attempt fails because the selected datastore does not meet the minimum requirements. Which property is most likely the cause?

   • AThe datastore is not backed by vSAN or VMFS
   • BThe datastore is VMFS 6 and is formatted with 1 MB block size
   • CThe datastore is vSAN and has a single disk group
   • DThe datastore is NFS 4.1 and is mounted with soft mount options
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   A namespace error is reported in vCenter. Which vCenter log would contain the most relevant events for this error?

   • AThe vSphere Web Client logs
   • BThe ESXi host's hostd logs
   • CThe vCenter Server's vpxd logs
   • DThe NSX-T Manager's controller logs
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   A DevOps team is attempting to provision a new VKS (vSphere Kubernetes Service) cluster from the Supervisor namespace. The provisioning fails with the error: 'Insufficient resources to create the requested cluster. The namespace has 4 CPU and 8 GB memory available, but the cluster requires 6 CPU and 12 GB memory.' The administrator checks the namespace's resource quotas and confirms they are set correctly. What is the most likely cause of this failure?

   • AThe namespace has other workloads running that are consuming the available CPU and memory resources.
   • BThe namespace's resource quota is configured with a limit that is lower than the requested cluster size.
   • CThe VKS cluster's Kubernetes version is not compatible with the Supervisor's version.
   • DThe Supervisor cluster's storage policy does not have enough capacity to accommodate the new VKS cluster's persistent volumes.
   Reveal Solution Discussion Select an answer first
6. 10expert · hard

   A vSphere administrator is trying to create a new namespace in a vSphere Supervisor. The creation fails with the error: 'Failed to create namespace: the namespace name is already in use.' The administrator has verified that the namespace does not exist in the Supervisor. What is the most likely cause of this issue?

   • AThe namespace name contains invalid characters that are not allowed by Kubernetes.
   • BThe namespace was recently deleted but is still in the 'Terminating' state.
   • CThe namespace name is too long and exceeds the Kubernetes naming limit.
   • DThe namespace name is reserved by the Supervisor for internal use.
   Reveal Solution Discussion Select an answer first