Troubleshoot Container Deployment, Registry, and Trusted CA Errors VCAP-VCF-SUPPORT Practice Questions (Page 1)

Questions 1–5

1. 1foundation · easy

   A container deployment in a vSphere Supervisor namespace fails with an 'x509: certificate signed by unknown authority' error when pulling an image from an internal registry. What is the most likely cause?

   • AThe registry's CA certificate is not trusted by the container runtime
   • BThe registry credentials are incorrect
   • CThe container image is corrupted
   • DThe registry's DNS name resolves to the wrong IP address
   Reveal Solution Discussion Select an answer first
2. 2application · medium

   A container deployment fails with an authentication error when pulling from a private registry. The administrator confirms the registry credentials are correct. What is the most likely cause?

   • AThe namespace's resource quota is exceeded
   • BThe image pull secret is not correctly referenced in the pod specification
   • CThe registry's certificate is not trusted
   • DThe container image is not compatible with the Supervisor's runtime
   Reveal Solution Discussion Select an answer first
4. 3expert · hard

   An organization is deploying containers to a vSphere Supervisor namespace. The registry uses a certificate signed by an internal CA. The CA certificate is added to the Supervisor cluster's trusted bundle, but image pulls still fail with an x509 error. The administrator discovers the registry's certificate has a hostname mismatch. What is the correct course of action?

   • AConfigure the Supervisor to skip hostname verification
   • BUse the registry's IP address in the image pull URL
   • CRegenerate the registry's certificate with the correct SANs and update the trusted bundle if needed
   • DAdd the registry's hostname to the Supervisor cluster's DNS
   Reveal Solution Discussion Select an answer first
5. 4foundation · easy

   A vSphere Supervisor cluster is failing to deploy a containerized workload. The deployment status shows a persistent 'Pending' state with no image pull errors. Which resource is the most likely cause of this deployment failure?

   • AUntrusted CA certificate for the registry
   • BIncorrect container registry credentials
   • CMisconfigured network policy blocking pod-to-pod communication
   • DInsufficient CPU or memory resources in the Supervisor cluster
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   A DevOps team is deploying a containerized application to a vSphere Supervisor namespace. The image is stored in a private Harbor registry that uses a self-signed certificate. The image pull fails with an x509 certificate error. The registry credentials are confirmed correct. What should the administrator configure to resolve the issue?

   • AConfigure the namespace to use the registry's IP address instead of its hostname
   • BAdd the Harbor CA certificate to the Supervisor cluster's trusted CA bundle
   • CSet the image pull policy to IfNotPresent
   • DRecreate the Harbor registry with a publicly trusted certificate
   Reveal Solution Discussion Select an answer first