Given a Scenario, Troubleshoot Issues with VMware Supervisor VCP-VCF-SUPPORT Practice Questions (Page 7)

Questions 31–35

1. 31expert · hard

   A Supervisor is experiencing intermittent pod scheduling failures. The control plane is healthy, and there are no resource constraints. The failures correlate with periods of high network traffic. Which troubleshooting step should you take first to isolate the root cause?

   • ARestart the Supervisor control plane VMs.
   • BReview the storage policy compliance status for the namespace.
   • CCheck the NSX-T distributed firewall logs for dropped packets between the scheduler and the API server.
   • DIncrease the resource quotas for the namespace.
   Reveal Solution Discussion Select an answer first
2. 32foundation · easy

   A user reports that they cannot access a service exposed via a LoadBalancer service on the Supervisor. Which integration is most likely to be involved?

   • AIntegration with vCenter
   • BIntegration with storage
   • CIntegration with NSX
   • DIntegration with the identity provider
   Reveal Solution Discussion Select an answer first
4. 33application · medium

   A vSphere administrator is upgrading a Supervisor from version 1.22 to 1.24. The upgrade fails with a compatibility error. The administrator has verified that vCenter and ESXi are at supported versions. What is the most likely cause of the failure?

   • AThe Kubernetes API server is not responding.
   • BThe NSX-T version is not compatible with the target Supervisor version.
   • CThe Supervisor's storage policy is set to a non-replicated policy.
   • DThe vSphere Namespace has too many running workloads.
   Reveal Solution Discussion Select an answer first
5. 34foundation · easy

   A pod on the Supervisor is in an ImagePullBackOff state. Which of the following is the most likely cause?

   • AThe image name is incorrect or the registry is unreachable
   • BThe storage policy is invalid
   • CThe NSX-T load balancer is misconfigured
   • DThe pod is requesting more CPU than available
   Reveal Solution Discussion Select an answer first
6. 35application · medium

   A DevOps team reports that a new deployment on a Supervisor is not scaling beyond two replicas. The deployment's replica count is set to five, and there are no resource constraints. What is the most likely cause?

   • AThe NSX-T load balancer is not configured.
   • BThe storage policy is not compatible with the deployment.
   • CThe namespace has a resource quota that limits the number of pods.
   • DThe image pull secret is invalid.
   Reveal Solution Discussion Select an answer first