3V0-24.25 Practice Questions

The VCF 9.0 documentation explicitly states that“the VKS exposes three layers of controllers to manage the lifecycle of a VKS cluster.”Those three controller layers map directly to the answer choices:

Cloud Provider Plug-in: VKS-provisioned clusters include components needed to integrate with vSphere Namespace resources, including aCloud Provider Plug-inthat integrates with the Supervisor and supports infrastructure-integrated functions (for example, passing persistent volume requests to the Supervisor which integrates with Cloud Native Storage).

Cluster API: The documentation describesCluster APIas providing declarative APIs for “cluster creation, configuration, and management,” including resources for the VMs and cluster add-ons.

Virtual Machine Service: TheVirtual Machine Serviceprovides declarative APIs to manage VMs and associated vSphere resources, and is used to manage the lifecycle of the control plane and worker node VMs that host a VKS cluster.

CNI and CSI are important cluster components, but the document distinguishes these from thethree controller layersresponsible for lifecycle management.

In VCF 9.0 Workload Management, avSphere Namespaceis the construct that “sets the resource boundaries” for workloads running on a Supervisor, includingCPU, memory, and storage. The documentation explicitly states that a vSphere Namespace “sets the resource boundaries forCPU, memory, storage, and also the number of Kubernetes objects that can run within the namespace.” In the operational procedure “Set Resource Limits to a vSphere Namespace,” VMware further lists the configurable limits as:CPU(“set a limit to the CPU consumption”),Memory(“set a limit to the memory consumption”), andStorage(“set a limit on the storage consumption… per storage policy that is used”).

By contrast,Containersare not a namespace “resource limit” category; VMware documents “Container Defaults” separately (defaults for container CPU/memory requests and limits) rather than a top-level resource limit type. Similarly,Servicesare governed under “Object Limits” (how many Kubernetes objects like Services can exist), which is distinct from resource limits. Therefore, the three resource limitations defined on a vSphere Namespace areCPU, Memory, and Storage.

A Global Namespace in a service-mesh-driven, multi-cluster design is fundamentally anorganizational and policy boundarythat lets platform teams treat multiple Kubernetes namespaces—across multiple clusters/regions—as one logical application domain. That is whyBis correct: it defines an application boundary spanning clusters, which is exactly what “GovApp” needs when its tiers are distributed across regions but must still behave as one application. It also explains whyAis correct: the value of a Global Namespace is that you can applyconsistent identity, security, and traffic policiesacross all member namespaces and clusters, rather than configuring them separately per cluster. This supports uniform mTLS/authorization posture, consistent service-to-service access rules, and standardized routing behaviors regardless of where a service instance runs.

The other options describe outcomes that may be enabled by additional service-mesh features, but they are not the corerequirementsthat define a Global Namespace: distributed ingress/egress is not guaranteed simply by the namespace construct, automatic workload placement is typically handled by schedulers/placement engines rather than the namespace boundary, and centralized logging is an observability capability outside the namespace requirement itself.