VMware Tanzu for Kubernetes Operations Professional (2V0-71.23) — Free Practice Questions
10 free sample questions from a bank of 67, with the correct answers and explanations. No signup required — start practising right now.
1What two steps are required to visualize API connectivity and enable API protection in VMware Tanzu Service Mesh? (Choose two.)
Activate API Discovery for the Global Namespace
Create API Security Policy for the Global Namespace
Enable Threat Detection Policy for the Global Namespace
Set a Distributed Firewall policy for the Global Namespace
Create an Autoscaling policy for API for the Global Namespace
Answer: A, B
The short version
Answer: A + B — Activate API Discovery for the Global Namespace, then create an API Security Policy.
Key concepts
Tanzu Service Mesh Global Namespace scopes discovery and policy.
API Discovery visualizes API connectivity/endpoints.
API Security Policy enables protection.
Why AB is correct
A: Discovery must be activated first to see APIs.
B: Security policy then protects those discovered APIs.
Why the others are wrong
C Threat Detection: not the API discovery/protection workflow.
D Distributed Firewall: NSX construct, not TSM API protection.
E Autoscaling: performance/scale, not API visibility/security.
2V0-7123 exam tip
Discovery first, protection second — if you see both choices, pick that pair.
2The Supervisor Service in Tanzu Kubernetes Grid exposes three layers of controllers to manage the lifecycle of a Tanzu Kubernetes Grid cluster.
Which layer of controllers is correct?
Virtual Machine Service, Tanzu Kubernetes Grid and Cluster API
Aria integration Service, Tanzu Cluster API and Tanzu Container Network Controller
VMware Tanzu Mission Control Connection agent, Cluster API and Kubernetes Connection Agent
Answer: A
The short version
A — Virtual Machine Service, Tanzu Kubernetes Grid and Cluster API are the three Supervisor Service controller layers.
Key concepts
Supervisor Service extends vSphere with Kubernetes controllers
VM Service manages VMs as Kubernetes objects
TKG controllers manage Tanzu cluster lifecycle
Cluster API is the upstream foundation
Why A is correct
VMware docs list exactly these three layers: Virtual Machine Service for VM management, Tanzu Kubernetes Grid Service for cluster provisioning, built on Cluster API controllers.
Why the others are wrong
B: Authentication webhook, CSI storage support, cloud provider are components, not the three lifecycle controller layers.
C: Aria integration, made-up Tanzu Container Network Controller are not Supervisor controller layers.
D: TMC connection agent / Kubernetes connection agent relate to Mission Control attach, not Supervisor on vSphere.
2V0-7123 exam tip
Memorize the trio: VM Service + TKG Service + Cluster API. If you see Mission Control agents or webhooks, eliminate.
3Which two Kubernetes Service types are fulfilled natively by Kubernetes without requiring external integrations? (Choose two.)
ExternalName
Ingress
LoadBalancer
NodePort
ClusterIP
Answer: D, E
The short version
Answer: D + E — NodePort and ClusterIP.
Key concepts
ClusterIP: internal-only virtual IP, no external dependency.
NodePort: exposes on each node port, built into kube-proxy.
E ClusterIP is the default native in-cluster type.
Why the others are wrong
A ExternalName: maps to an external DNS name, requires external target.
B Ingress: not a Service type; requires Ingress controller integration.
C LoadBalancer: requires external cloud load balancer integration.
2V0-7123 exam tip
Native = ClusterIP + NodePort. Anything needing cloud/LB/controller/DNS-out is external.
4What is the Kubernetes component that is responsible for workload creation?
API Server
Scheduler
etcd
Kubelet
Answer: B
The short version
Answer is B Scheduler.
Key concepts
API Server front-end, Scheduler placement, etcd store, Kubelet node agent.
Why B is correct
K8s docs define kube-scheduler as watching for newly created Pods with no node and selecting the best node, which is workload placement/creation.
Why the others are wrong
A API Server only exposes API and processes requests, does not place workloads; C etcd only stores cluster state; D Kubelet only runs already-assigned Pods on its node, it does not create/place workloads.
2V0-7123 exam tip
If asked who picks the node for a new Pod, choose Scheduler; if asked who ensures containers stay running on the node, choose Kubelet.
5Which two methods can be used to install Fluent Bit on a VMware Tanzu Kubernetes Grid cluster? (Choose two.)
Install Fluent Bit using Tanzu CLI login plugin
Install Fluent Bit using VMware Tanzu Kubernetes Grid Installer Interface
Install Fluent Bit from VMware Tanzu Mission Control
Install Fluent Bit from VMware vSphere Client
Install Fluent Bit using Tanzu CLI package plugin
Answer: C, E
The short version
Answer: C + E — from Tanzu Mission Control and via Tanzu CLI package plugin.
Key concepts
Fluent Bit is a TKG package.
Install via Tanzu package lifecycle or TMC catalog.
Installer Interface / vSphere Client are not Fluent Bit install paths.
Why CE is correct
C: TMC can deploy Fluent Bit to attached/managed clusters.
E: tanzu package install with package plugin is the CLI method.
Why the others are wrong
A login plugin: only authenticates, does not install packages.
B Installer Interface: deploys management/workload clusters, not Fluent Bit.
D vSphere Client: does not install Fluent Bit on TKG.
2V0-7123 exam tip
TKG packages = package plugin or TMC. Login plugin never installs.
6Which two resources can External DNS create records for? (Choose two.)
Virtual machines
Kubernetes pods
Kubernetes services
Kubernetes nodes
Contour HTTPProxy
Answer: C, E
The short version
C, E — External DNS creates records for Kubernetes Services and Contour HTTPProxy (Ingress).
Key concepts
External-DNS syncs K8s resources to DNS provider
Services of type LoadBalancer / NodePort are primary sources
Ingress resources including Contour HTTPProxy CRD are supported sources
It does not create records for Nodes, Pods, or VMs directly
Why CE is correct
External DNS watches Service and Ingress / HTTPProxy objects and creates A/CNAME records mapping hostnames to external IPs. Contour HTTPProxy is Contour's Ingress-equivalent CR that External DNS understands.
Why the others are wrong
A: Virtual machines are vSphere objects, not watched by External DNS.
B: Pods are ephemeral with unstable IPs — not DNS sources.
D: Nodes are not a supported External DNS source for TKG package.
2V0-7123 exam tip
For External DNS choose-two: think Service + Ingress/HTTPProxy. Never pick Pods, Nodes, or VMs.
7What is the correct resource hierarchy order in VMware Tanzu Mission Control?
Root -> Cluster Groups -> Clusters
Organization -> Cluster Groups -> Namespaces
Organization -> Clusters -> Cluster Groups
Organization -> Cluster Groups -> Clusters
Answer: D
The short version
Answer is D Organization -> Cluster Groups -> Clusters.
Key concepts
TMC hierarchy: Organization top, cluster groups organize clusters, workspaces organize namespaces.
Why D is correct
Broadcom docs require every cluster to belong to a cluster group under the organization, so Organization -> Cluster Groups -> Clusters is the correct cluster hierarchy order.
Why the others are wrong
A uses Root which is not a TMC level; B inserts Namespaces directly under Cluster Groups omitting Clusters; C reverses Clusters and Cluster Groups.
2V0-7123 exam tip
Remember clusters live inside cluster groups; namespaces live inside workspaces — do not mix the infrastructure view with the app view.
8Which set of tools can be used to attach a Kubernetes cluster to VMware Tanzu Mission Control?
Tanzu CLI and VMware vSphere Web UI
Tanzu CLI and VMware Tanzu Mission Control Web UI
kubectl and VMware vSphere Web UI
kubectl and VMware Tanzu Mission Control Web UI
Answer: D
The short version
D — kubectl and VMware Tanzu Mission Control Web UI.
Key concepts
Attach = register existing cluster with TMC
TMC console generates agent YAML / URL
kubectl applies the manifest on the target cluster
Tanzu CLI is for provisioning, not attach
Why D is correct
Official flow: open TMC Web UI, Attach Cluster, copy kubectl apply -f URL, run it against the cluster context. That pairs kubectl + TMC UI.
Why the others are wrong
A: vSphere Web UI plays no role in TMC attach.
B: Tanzu CLI is not used for attach; kubectl applies the agent manifest.
C: vSphere Web UI is wrong portal; must be TMC console.
2V0-7123 exam tip
Attach = TMC UI to get YAML + kubectl apply. Provision/upgrade = Tanzu CLI or tmc CLI. Don't mix them.
9A Tanzu Mission Control administrator would like to enforce the following container controls:
Only allows container images that match the specified names or tags.
Ensure that the container image is not tampered with.
Which type of policy can be used?
Only image registry policy provides name/tag allowlisting plus digest enforcement, exactly matching only-allow-matching-names/tags and anti-tamper requirements.
Why the others are wrong
A Access controls identity roles, not images; B Security controls pod securityContext, not registry allowlists; C Image Security is not a TMC policy type; E Network controls pod traffic, not image provenance.
10An administrator was requested to create a pod with two interfaces to separate the application and management traffic for security reasons.
Which two packages have to be installed in VMware Tanzu Kubernetes Grid cluster to satisfy the requirement? (Choose two.)
multus
external-dns
cert-manager
grafana
contour
Answer: A, C
The short version
A, C — multus + cert-manager.
Key concepts
Multus is meta-CNI for multiple pod interfaces
Separates app vs management traffic with second vNIC
Multus in TKG requires cert-manager for webhook certs
external-dns, grafana, contour are unrelated
Why AC is correct
To give a pod two interfaces you add the Multus CNI package. TKG docs state Multus depends on cert-manager, so both packages must be installed.
Why the others are wrong
B: external-dns manages DNS records, not interfaces.
D: grafana is observability, not networking.
E: contour is ingress/L7 routing, not multi-NIC.
2V0-7123 exam tip
Two pod interfaces = Multus. In TKG, always pair Multus with cert-manager prerequisite.