← HomeVMware
LoginSign UpGoogle Login
VMware · Advanced VMware Cloud Foundation 9.0 vSphere Kubernetes Service · 3V0-24.25 · Version V9.02

Question 9

Topic: VCF 9.0 VKS – 3V0-24.25 Study Bank

Question type: Drag Order · Difficulty: Medium

Drag and drop the three features into the correct order from Possible Features list on the left and place them into the Provided by Service Mesh on the right side. (Choose three.)

Sign in to save this question

Answer

  1. Federation
  2. Graphical User Interface
  3. Observability

Explanation

Provided by Service Mesh (choose three, in order): Federation Graphical User Interface Observability A service mesh is an application networking layer that manages service-to-service communication across Kubernetes clusters, providing consistent connectivity, policy enforcement, and visibility without requiring application code changes. Federation is 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). A Graphical User interface is commonly provided alongside the service mesh platform to centrally configure policies (traffic routing, access controls, security settings) and to visualize service topology and health. Observability is a core service-mesh outcome: by inserting sidecar proxies (or equivalent data plane components) into the data path, the mesh can generate consistent metrics, logs, and distributed traces for service traffic, enabling latency/error monitoring and dependency mapping. The other options are not service-mesh features: Autoscaling is handled by Kubernetes/HPA and metrics pipelines, application backup is typically provided by backup tools (e.g., Velero-like solutions), and database connection management is handled by application frameworks or database proxies rather than the service mesh itself.

ExamSim normalization: The source presents these three Service Mesh features in the stated order. Normalized to drag_order for ExamSim.