VMware vSphere with Tanzu Specialist Exam Guide
The VMware vSphere with Tanzu Specialist exam validates whether you can understand and operate Kubernetes capabilities delivered through a vSphere environment, including the Supervisor Cluster, Control Plane VMs, core services, and kubectl fundamentals. It is intended for candidates who already understand vSphere, Kubernetes, containers, networking, and NSX-T. This guide helps you decide whether your current experience is sufficient, which skills need deliberate practice, and how to sequence study before scheduling exam 5V0-23.20.
What the exam validates
The exam validates practical knowledge of how vSphere with Tanzu orchestrates Kubernetes clusters and containerized applications in a vSphere environment. Its scope is not limited to Kubernetes syntax: the official objectives also cover the platform architecture, core services, Supervisor Cluster, Control Plane VMs, and the kubectl command-line interface.
Passing leads to the VMware Certified Specialist – vSphere with Tanzu certification. The exam code is 5V0-23.20, and the official exam guide identifies the assessment as a proctored exam delivered through Pearson VUE.
A useful way to interpret the certification is as a platform-operations credential. You should be able to connect vSphere concepts with Kubernetes administration rather than treating the two technologies as separate subjects. When reviewing a topic, ask what the component does, where it runs, how it is configured, and what symptom appears when it is unavailable or incorrectly configured.
Who should schedule it
Schedule the exam only after you can work comfortably across both vSphere and Kubernetes concepts. The minimally qualified candidate is expected to have basic knowledge of Kubernetes and containers, at least 12 months of vSphere experience, and experience with NSX-T plus network, virtualization, and operating-system experience or education.
The official exam guide recommends completing the recommended training courses and holding a valid VCP-DCV certification. Those recommendations matter because the exam assumes that core vSphere administration is familiar rather than newly learned. If vSphere networking, storage, or virtual-machine administration still requires extensive reference reading, address that gap before concentrating on Tanzu.
A candidate with strong Kubernetes knowledge but limited vSphere experience should not assume that Kubernetes practice alone is enough. Conversely, a vSphere administrator who has never created or inspected Kubernetes resources needs a Kubernetes fundamentals phase before attempting platform troubleshooting.
Use a simple readiness decision: schedule when you can explain the platform architecture without notes, perform basic kubectl work in a lab, trace a networking or storage symptom to a likely layer, and explain the purpose of the Supervisor Cluster and Control Plane VMs.
What the official objectives emphasize
The official objective list provides the safest study boundary. It includes introducing vSphere with Tanzu, vSphere with Tanzu core services, the purpose and role of a Supervisor Cluster, the characteristics of Control Plane VMs, and the characteristics and uses of kubectl.
Treat each objective as a capability statement, not as a vocabulary list. For example, identifying the role of a Supervisor Cluster should lead you to distinguish the vSphere Kubernetes control plane from workload clusters and to understand how it participates in the platform design. Identifying Control Plane VM characteristics should lead you to recognize their place in the architecture and their operational significance.
For kubectl, study both purpose and use. You should understand what the command-line interface is for, how it communicates with Kubernetes resources, and how it supports inspection and troubleshooting. Memorizing isolated commands without understanding the object being queried creates a fragile preparation strategy.
The official guide also names broader sections such as architecture and core services. Build a map of those sections using the current official guide rather than relying on an old third-party list. Product names, versions, and exam objectives can change, while unauthorized question banks may preserve obsolete material.
How to interpret blueprint percentages
Do not use the published percentage list for the Certified Kubernetes Administrator exam as a weighting model for this VMware exam. The supplied VMware Cloud Provider article labels those figures as the v1.21 CKA curriculum, not as domains for the VMware vSphere with Tanzu Specialist exam.
That article lists 25% Cluster Architecture, Installation & Configuration; 15% Workloads & Scheduling; 20% Services & Networking; 10% Storage; and 30% Troubleshooting for the CKA curriculum. Those percentages must remain attached to their CKA domain labels and should not be presented as VMware vSphere with Tanzu Specialist blueprint weights.
The official VMware exam research supplied here does not provide a percentage distribution for the VMware Specialist domains. Study priority should therefore come from the official objectives, your experience gaps, and the operational consequences of each topic—not from assigning unsupported percentages to VMware content.
Build the architecture model first
Start with a one-page architecture diagram before studying individual procedures. The diagram should show the vSphere layer, the Supervisor Cluster, Control Plane VMs, workload or Tanzu Kubernetes clusters where applicable, networking dependencies, storage, and the core Tanzu services named by the exam objectives.
The Supervisor Cluster is a central concept because the official objectives specifically require identifying its purpose and role. Your notes should answer four questions: what it represents in a vSphere with Tanzu deployment, which Kubernetes-related responsibilities it supports, how it relates to workload clusters, and which dependencies would prevent it from operating correctly.
Create a second note for Control Plane VMs. Record their characteristics, their architectural position, and why an administrator would care about them during deployment or troubleshooting. Avoid reducing the topic to a definition; operational questions usually require you to distinguish a component’s role from that of another control-plane or worker component.
Use a dependency chain when studying: vCenter and vSphere management, cluster configuration, networking and NSX-T, storage policies or classes, Supervisor Cluster services, and workload-cluster operations. This sequence helps you reason from a failed prerequisite to its visible symptom instead of guessing from a list of commands.
Close the Kubernetes and container gaps
Learn the Kubernetes fundamentals that the exam assumes before spending time on Tanzu-specific details. Focus on resources, namespaces, control-plane concepts, worker nodes, services, storage, scheduling, and the difference between desired state and observed state.
Basic container knowledge should include the relationship between an image, a container, a workload, and the resources used to run it. You do not need to turn this preparation into a separate application-development course, but you should understand enough container behavior to interpret a deployment or a failed workload.
For every Kubernetes concept, connect it to an administrator’s task. A namespace is not merely a definition; it affects resource organization and access boundaries. A service is not merely an object type; it provides a way for workloads to reach one another. A persistent volume is not merely storage terminology; it represents a dependency that can fail independently of compute.
Use kubectl as the bridge between theory and evidence. Practice retrieving resource information, viewing status and events, inspecting configuration, and reading logs in a controlled lab. The official objective is to identify the characteristics and uses of kubectl, so understand why a command is useful and what its output tells you rather than copying command strings mechanically.
Study networking as a dependency chain
Treat networking as a layered troubleshooting problem: vSphere connectivity, NSX-T and network configuration, control-plane reachability, workload-cluster communication, and service exposure. This approach is more reliable than memorizing isolated networking terms.
The official candidate profile specifically calls for NSX-T and network experience. Review how a networking decision affects the platform before moving to command-line diagnosis. Ask which component owns the configuration, which endpoints must communicate, and whether the problem is control-plane, node, service, or external connectivity.
Use the official Tanzu Mission Control and vSphere with Tanzu Services quick-start article as a conceptual exercise, not as a promise that every interface or workflow remains identical. It describes creating a cluster group, registering a vSphere with Tanzu Supervisor Cluster as a management cluster, deploying a Tanzu Kubernetes cluster, and applying a basic policy.
That article also identifies practical prerequisites for its walkthrough, including vCenter 7u3c with Tanzu Services enabled, a vSphere namespace, outbound internet connectivity from Supervisor and workload-cluster nodes, and dedicated virtual distributed switch networks for workload clusters. Treat these as requirements of that documented scenario, not universal exam requirements unless the current exam guide says so.
When practicing, deliberately break one dependency at a time. For example, inspect what evidence changes when connectivity is unavailable, a required network is misidentified, or a cluster registration step is incomplete. Record the symptom, the validation command or interface, and the corrective layer.
Review storage through workload behavior
Storage preparation should connect storage configuration to the behavior of a Kubernetes workload. Review storage policies or classes, claims, volumes, and the point at which a workload can remain pending because storage has not been provisioned or selected correctly.
The supplied official quick-start article includes a workflow in which the user selects a Kubernetes version, network settings, and desired storage classes. That detail is useful because it shows that cluster deployment decisions are interdependent: networking and storage are selected as part of the same provisioning path rather than treated as unrelated afterthoughts.
Make a small troubleshooting table with three columns: requested storage, observed state, and likely dependency. Include examples such as an unbound claim, an unavailable class, or a mismatch between the requested configuration and what the platform exposes. Keep the table focused on reasoning, not on unsupported product-version assumptions.
Do not spend most of your preparation reading storage theory while neglecting platform integration. The target skill is understanding how vSphere-backed infrastructure and Kubernetes storage expectations meet, and how to identify the layer that requires inspection.
Use hands-on labs deliberately
Hands-on work is most valuable when each lab session has a question to answer. Build, inspect, change, and troubleshoot a small environment or an official lab rather than watching demonstrations passively.
The VMware Cloud Provider article recommends the hands-on labs HOL-2113-01-SDC vSphere with Tanzu and HOL-2113-91-ISM vSphere with Tanzu – Lightning. Use those named labs where they are available through the official learning channels, and verify access and product versions before building your schedule around them.
A productive session has four stages. First, draw the expected state before making a change. Second, perform the documented configuration or deployment. Third, inspect the resulting state through the relevant interface and kubectl. Fourth, remove or alter one dependency and explain the resulting symptom. This converts a guided exercise into diagnostic practice.
Keep an evidence log. For each exercise, write the component, expected state, observed state, command or screen used to verify it, and the next action. This habit trains the same cross-layer thinking needed for scenario-based questions without relying on recalled exam items.
Use Tanzu Mission Control as a supporting scenario
Tanzu Mission Control is useful study context because the official quick-start article shows how a Supervisor Cluster can be registered as a management cluster and used in a broader cluster-management workflow. Study the relationship between the Supervisor Cluster, management-cluster registration, cluster groups, policies, and Tanzu Kubernetes cluster deployment.
The article describes selecting “vSphere with Tanzu (vSphere 7 with workload management enabled)” when registering the management cluster. It also explains that cluster groups provide logical organization and policy application. These details help you understand the operational boundary between platform registration and ongoing cluster governance.
Do not assume that familiarity with Tanzu Mission Control substitutes for vSphere with Tanzu administration. Use TMC as a scenario for understanding management relationships and policy organization, while keeping the exam’s explicitly named topics—Supervisor Cluster, Control Plane VMs, core services, and kubectl—at the center of revision.
If a lab exposes a registration URL, cluster group, or policy workflow, document the purpose of each object. The goal is to explain why an administrator performs the action and what capability it enables, not to memorize a particular console sequence that may vary by release.
Follow a four-stage study roadmap
A staged roadmap is more effective than alternating randomly between Kubernetes commands and product documentation. Move from prerequisites to architecture, then to operations, and finally to timed review based on evidence from your own weak areas.
Stage one is prerequisite repair. Confirm your vSphere administration, networking, NSX-T, operating-system, Kubernetes, and container foundations. If you cannot explain a prerequisite without immediately searching for a definition, put it on the study list before beginning full Tanzu workflows.
Stage two is architecture and service mapping. Read the official exam guide, extract every objective, and place each one on your architecture diagram. Add the Supervisor Cluster, Control Plane VMs, core services, and kubectl to a dependency map. Mark any objective for which you have only theoretical knowledge.
Stage three is guided implementation and inspection. Complete the recommended training identified in the official guide and use the named hands-on labs where accessible. Repeat key tasks from memory after the first pass. At the end of each session, explain what changed, how you verified it, and what would fail if a dependency were removed.
Stage four is troubleshooting and consolidation. Work through deliberately broken scenarios, review your evidence log, and revisit the official objectives rather than expanding into unrelated Tanzu products. Schedule only after you can explain the architecture and validate common states with appropriate tools.
Plan the final review around evidence
The final review should test whether you can choose the next diagnostic action, not whether you can recite a product glossary. Use short scenario prompts and answer each with the affected layer, the evidence you would collect, and the most defensible next step.
Create prompts around the official objectives: identify the role of the Supervisor Cluster; distinguish Control Plane VM characteristics; select an appropriate kubectl use; explain a core service; or determine whether a symptom points to networking, storage, cluster configuration, or workload state.
Separate certainty from assumptions in your notes. Label a statement as an official requirement, an objective, a lab observation, or your own study recommendation. This prevents a procedure from one older environment becoming an assumed exam rule.
Avoid exam dumps, leaked questions, and memorization schemes. They cannot establish that you understand the platform, may contain obsolete or inaccurate material, and do not guarantee a passing result. Use official objectives, training, documentation, and hands-on work instead.
Know the verified delivery details
The official exam guide states that this is a proctored Pearson VUE exam containing 62 items. It gives an exam duration of 125 minutes and identifies 300 as the passing score using a scaled scoring method.
The official guide was last updated on January 9, 2023, according to the supplied research. Because exam delivery policies and registration details can change, confirm the current appointment, identification, environment, and scheduling rules through the official certification and Pearson VUE channels before booking.
The supplied VMware Cloud Provider article contains conflicting timing and item details for related or earlier certification discussions, including other appointment and duration statements. For this guide, use the exam-specific figures from the official Broadcom exam-prep guide and do not combine figures from the older article.
The research also references a Linux command line with required commands for performance-based items in a related exam-experience account. Since the official exam guide supplied here confirms proctored Pearson VUE delivery but does not establish that exact environment for this exam, treat command-line practice as good preparation for the kubectl objective rather than as a guaranteed test-interface description.
Avoid the preparation mistakes that waste time
The most expensive preparation mistakes are usually sequencing errors: learning commands before architecture, studying Kubernetes without vSphere context, or reading every Tanzu product page instead of following the exam objectives.
Do not begin with kubectl syntax if you cannot explain what resource or control plane you are inspecting. Command practice becomes useful only when you can connect output to a platform decision. Start with the architecture diagram, then use kubectl to validate actual states.
Do not treat a completed guided lab as proof of readiness. Repeat the workflow with fewer prompts, change one setting, and diagnose the result. A candidate who can follow a deployment wizard may still struggle when a dependency is unavailable.
Do not assign the CKA percentages to this exam. The supplied percentage facts describe CKA domains and are not a VMware Specialist blueprint. Use the official VMware objective list and your diagnostic performance to set priorities.
Do not postpone vSphere fundamentals. The stated candidate profile includes at least 12 months of vSphere experience and NSX-T or related network knowledge. If those areas are weak, repair them before adding more product-specific reading.
Do not schedule solely because you have finished a video course. Schedule when your objective checklist is supported by hands-on evidence and when you can explain troubleshooting choices without relying on recalled questions.
Take these next actions
Your next action should be a gap assessment against the official guide, followed by one architecture exercise and one hands-on validation session. This gives you evidence about readiness before you commit to an appointment.
Download or open the official VMware vSphere with Tanzu Specialist exam-prep guide and record the exam code, objectives, prerequisites, delivery information, and recommended training. Mark each objective as confident, needs review, or needs lab practice.
Next, draw the platform dependency map from vSphere and networking through the Supervisor Cluster, Control Plane VMs, core services, workload clusters, storage, and kubectl-based inspection. Explain the map aloud or in writing without copying the source text.
Then complete an official vSphere with Tanzu lab such as HOL-2113-01-SDC or HOL-2113-91-ISM if available to you. Record what you configured and how you verified it. Add a second session focused only on troubleshooting and evidence collection.
Finally, recheck the current official scheduling information before booking. Bring unresolved objective gaps into a short final study cycle; do not fill that cycle with dumps or unsupported claims about what the exam will contain.
Conclusion
This exam is best approached as a platform-integration assessment: vSphere administration, Kubernetes fundamentals, networking, storage, Tanzu services, and disciplined diagnosis must fit together. Use the official objectives as the boundary, the stated candidate profile as a readiness test, and hands-on labs as evidence that you can operate rather than merely recognize terminology. Confirm current Pearson VUE details and the official guide before scheduling exam 5V0-23.20.
Related exams
- 1V0-21-20PSE exam — Associate VMware Data Center Virtualization Exam
- 1V0-31.21 exam — Associate VMware Cloud Management and Automation
- 1V0-41.20 exam — Associate VMware Network Virtualization
- 1V0-61.21 exam — Associate VMware Digital Workspace
- 2V0-31.21 exam — Professional VMware vRealize Automation 8.3
- 2V0-32.24 exam — VMware Cloud Operations 8.x Professional V2
