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

Questions 16–19

1. 16expert · medium

   A vSphere administrator is enabling Workload Management on a vSphere cluster. The deployment fails with the error: 'Failed to create the Supervisor Cluster: The specified network is not a vSphere Distributed Switch (VDS) portgroup'. The administrator has already created a VDS and a portgroup for the Supervisor cluster. What is the most likely cause of this error?

   • AThe portgroup is not associated with the correct VLAN ID.
   • BThe VDS is not in the same vSphere cluster as the hosts.
   • CThe portgroup is a standard portgroup on a vSphere Standard Switch (VSS), not a VDS portgroup.
   • DThe VDS is not configured with the correct MTU size.
   Reveal Solution Discussion Select an answer first
2. 17foundation · easy

   A VKS cluster cannot reach the Supervisor cluster's API server. Which component is most likely to be misconfigured?

   • AThe load balancer settings for the Supervisor cluster API server.
   • BThe Kubernetes version of the VKS cluster.
   • CThe DNS settings for the VKS cluster nodes.
   • DThe storage class used by the VKS cluster.
   Reveal Solution Discussion Select an answer first
4. 18foundation · easy

   A VKS cluster provisioning fails because the specified storage policy cannot be applied to the datastore. Which configuration is most likely to be the cause?

   • AThe storage policy is set to a thin provisioning type.
   • BThe storage policy is not associated with any storage container.
   • CThe datastore is not mounted on all ESXi hosts in the cluster.
   • DThe datastore is an NFS datastore that does not support the storage policy.
   Reveal Solution Discussion Select an answer first
5. 19expert · medium

   A VKS cluster is experiencing intermittent connectivity issues between the control plane and worker nodes. The administrator suspects a network policy is blocking traffic. What is the most efficient way to diagnose this issue?

   • AReview the network policy configurations in the namespace and check the NSX-T Data Center security logs.
   • BVerify the storage class used by the VKS cluster.
   • CCheck the VKS cluster's kubeconfig file for errors.
   • DRestart the VKS cluster nodes to reset the network connections.
   Reveal Solution Discussion Select an answer first