What 3V0-24.25 Questions and Answers feature?

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.

Provided by Service Mesh (choose three, in order):

Federation

Graphical User Interface

Observability

A service mesh is an application networking layer that managesservice-to-service communicationacross Kubernetes clusters, providing consistent connectivity, policy enforcement, and visibility without requiring application code changes.Federationis a service-mesh capability because modern meshes (especially multi-cluster/enterprise implementations) can connect services across multiple clusters and environments, enabling shared identity, cross-cluster service discovery, and uniform policy application (often described as multi-cluster or federated service connectivity). AGraphical User Interfaceis commonly provided alongside the service mesh platform to centrally configure policies (traffic routing, access controls, security settings) and to visualize service topology and health.Observabilityis a core service-mesh outcome: by inserting sidecar proxies (or equivalent dataplane components) into the data path, the mesh can generate consistentmetrics, logs, and distributed tracesfor service traffic, enabling latency/error monitoring and dependency mapping.

The other options are not service-mesh features:Autoscalingis handled by Kubernetes/HPA and metrics pipelines,application backupis typically provided by backup tools (e.g., Velero-like solutions), anddatabase connection managementis handled by application frameworks or database proxies rather than the service mesh itself.

VCF 9.0 describes backing up workloads on VKS clusters usingVelero(Velero Plugin for vSphere) and shows the backup command pattern scoping backup content bynamespace(for example, velero backup create ... --include-namespaces=my-namespace). This demonstrates thatNamespacesare a primary object type within backup scope (you choose which namespace content is captured). The same section explains that after backup execution,Kubernetes metadata is uploaded to the object store. “Kubernetes metadata” in this context includes standard namespaced resources that represent running workloads and how they are exposed, such asServices(a core Kubernetes API object used to provide stable access to pods).

In addition to namespace scoping, Velero’s selection model commonly includes filtering backed-up Kubernetes objects using selectors (for example, selecting subsets of resources), which aligns with the “objects identified by a label selector” option as an object-selection mechanism within the scope of what Velero captures from Kubernetes APIs (metadata/resources) once the namespace is targeted.

Therefore, the best match to the documented Velero workload-backup model is:Namespace,Service, andlabel-selected objectswithin the included namespace(s).