Exam 3V0-24.25 Topic 1 Question 168 Discussion

Actual exam question for VMware's 3V0-24.25 exam
Question #: 168
Topic #: 1
A cloud operations team is managing multiple Supervisor Clusters across two regions. Each region hosts its own vSphere Kubernetes clusters, integrated through a federated service mesh to enable consistent service connectivity and policy enforcement across environments.
The application team wants to expose a multi-tier microservice named "GovApp", which includes front-end, API, and database services distributed between the two regions. Uniform traffic routing, identity, and security policies are also needed for these workloads regardless of the cluster or region in which they are deployed.
To meet these requirements, the architects decide to create a Global Namespace that spans both Supervisor Clusters.
Which two statements describe the requirements for a Global Namespace in a vSphere Kubernetes Service Mesh deployment? (Choose two.)

Suggested Answer: A,B Vote an answer

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.

by Ina at Feb 21, 2026, 02:01 AM

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
Nick name: Submit Cancel
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

0
0
0
10