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 create the VM?
Reveal answer details Close answer details
Correct answerA
In a VMware vSphere Foundation (VVF) deployment with vCenter Supervisor Namespaces enabled, the method for creating VMs inside a Supervisor Namespace relies on the vSphere VM Service.
The VM Service exposes VMs as Kubernetes-native objects that are managed using kubectl.
Administrators (or DevOps engineers with appropriate permissions) must write a VM YAML manifest file, which specifies parameters such as apiVersion, kind: VirtualMachine, spec.imageName, spec.className, spec.storageClass, and spec.networkInterfaces.
The YAML manifest is then applied with kubectl to the Supervisor context.
This approach is documented as the supported method:
"As a DevOps engineer, provision a VM and its guest OS in a declarative manner by writing VM deployment specifications in a Kubernetes YAML file."
Why the other options are incorrect:
Option B: Deploy using the vSphere Client
The vSphere Client is used to configure Namespaces, permissions, and VM classes, but actual VM creation in Supervisor Namespaces is done via kubectl + YAML.
Option C: Use VCF CLI to deploy the VM VCF CLI (kubectl vsphere login) is used only to authenticate and obtain context, not to create VMs.
Option D: Log in to VCF Automation Service Broker This is used for vRealize Automation/Aria Automation integration, not for direct Supervisor Namespace VM creation.
References VMware Cloud Foundation 9.0.4 Documentation - Deploy a Virtual Machine on a Namespace in a Supervisor VMware Cloud Foundation 9.0.4 Documentation - Prepare a VM YAML file for Supervisor VMware Docs: VM Service in vSphere with Tanzu