Free VMware 3V0-24.25 Practice Exam with Questions & Answers | Set: 3

VCF 9.0 explicitly documents thatVKS supports two CNI options: Antrea and Calico, and that thesystem-defined default CNI is Antrea. This directly eliminates Flannel and Cilium as default supported options for VKS clusters on Supervisor in this context. VCF 9.0 also describes how a vSphere administrator can view or change this setting in the vSphere Client underSupervisor Management → Configure → Kubernetes Service → Default CNI, further reinforcing that Antrea is the baseline/default choice.

From a policy perspective in the question, the requirement is Kubernetes-layer observability and control of pod communications “without additional licensing or overlay complexity.” Antrea is presented in VCF 9.0 as the default CNI and is implemented usingOpen vSwitch, with networking and network policy capabilities provided at the Kubernetes layer for pods and services. Because it is the documented default (and supported) option for new VKS clusters, selectingAntreabest aligns with the “default supported option” requirement.

Kubernetes Service

When adding a Kubernetes cluster to anexisting vSphere Namespace, the workflow is initiated from within that namespace’s context in the vSphere Client. The administrator first opens the target namespace (as shown in the left navigation where the namespace is selected), then uses theKubernetes Servicearea to create and manage Kubernetes clusters associated with that namespace. In the namespaceSummaryview, theKubernetes Servicetile/card provides the entry point for cluster lifecycle actions, typically via an action link such asManage(and from thereCreate Cluster). This is because the Kubernetes cluster is anamespace-scoped resourcein the Supervisor environment: it inherits namespace-level policies and configuration such as permissions/RBAC, resource limits, storage policies, and networking selections that have already been defined for that namespace. Navigating to other areas likeStorageorNetworkis used to validate or adjust prerequisites (for example, storage policy availability or network settings), but the actual “create cluster” operation is launched fromKubernetes Servicewithin the namespace to ensure the cluster is created under the correct tenant boundary and governance model.

Configure tab

In the context of VMware Cloud Foundation (VCF) 9.0 and vSphere with Tanzu, a vSphere Zone is a critical infrastructure object used to represent a failure domain. Specifically, it allows the vSphere Supervisor to span across multiple vSphere clusters (typically three) to provide high availability against a complete cluster failure. This " zoned " deployment model ensures that the Supervisor Control Plane and workload cluster nodes (VKS) are distributed across different physical racks or data centers.

To start the process of creating a new vSphere Zone, an administrator must navigate to the Configure tab. While the provided screenshot highlights a specific namespace (other-namespace), the creation of the underlying infrastructure zones is an administrative task performed at the vCenter Server or Cluster level. However, within any object’s view in the vSphere Client, the Configure tab serves as the primary gateway for all lifecycle management and setup tasks. For a vCenter-level configuration, the path is vCenter Server > Configure > vSphere Zones . Once a zone is created and mapped to a vSphere cluster, it can then be associated with a Supervisor. In the namespace-specific view shown, the Configure tab is also where the administrator would verify the placement of the namespace on a zoned Supervisor and manage the association with specific Supervisor Services. By clicking Configure , the administrator accesses the sub-menus required to define and modify these high-level SDDC constructs, bridging the gap between traditional vSphere resource management and the declarative Kubernetes environment provided by VKS.

A Supervisor upgrade impacts the lifecycle and compatibility of Supervisor Services (including Core Supervisor Services). VMware guidance emphasizes validating compatibility for the components that depend on the Supervisor and remediating any incompatibilities as part of the overall upgrade process. If a Core Supervisor Service remains stuck in“Configuring”after the Supervisor is upgraded, a common and expected cause is that the service version isnot compatiblewith the upgraded Supervisor/vCenter software state. In those cases, the upgrade workflow expects you toidentify and update incompatible Supervisor Servicesto versions that match the new supported software level. Ensuring the vSphere Kubernetes Service is at asupportedversion (for the upgraded Supervisor) aligns with the documented approach: run compatibility checks and thenupdate the versions of incompatible Supervisor Servicesso they can complete reconciliation and reach a healthy state.