An administrator has been tasked to create a virtual machine (VM) into a VMware vCenter Supervisor Namespace in an existing VMware vSphere Foundation (VVF) deployment. How would the administrator…

Question

Options

• ACreate a YAML file and deploy using kubectl.
• BDeploy using the vSphere Client.
• CUse VCF CLI to deploy the VM.
• DLog in to VCF Automation Service Broker and select the "Create a VM" catalog item.

• A
  92% (23)
• B
  4% (1)
• D
  4% (1)

Explanation

Deploying a VM into a Supervisor Namespace requires using Kubernetes-native tooling because the vSphere Supervisor exposes a Kubernetes API endpoint - VMs are defined as VirtualMachine custom resources in YAML and applied with kubectl apply, making A the correct workflow. Option B (vSphere Client) is used for traditional vSphere VM provisioning, not for creating objects within a Supervisor Namespace's Kubernetes API. Option C (VCF CLI) is scoped to VMware Cloud Foundation infrastructure operations like managing workload domains and SDDC components - not individual VM creation inside namespaces. Option D (VCF Automation Service Broker) is a self-service catalog portal that can provision resources, but it is not the direct method for deploying into a Supervisor Namespace and would add unnecessary abstraction layers. Memory tip: Whenever you see "Supervisor Namespace," think Kubernetes - the word "Supervisor" signals the vSphere-with-Tanzu layer where everything is managed as a Kubernetes object via kubectl and YAML manifests.

No community discussion yet for this question.