VMware vSphere with Tanzu Specialist Exam Guide
The VMware vSphere with Tanzu Specialist exam validates whether you can understand and operate Kubernetes capabilities integrated with a vSphere environment, including Supervisor Clusters, Control Plane VMs, core services, and kubectl fundamentals. It is aimed at professionals who already understand vSphere and have working knowledge of Kubernetes, containers, networking, NSX-T, virtualization, and operating systems. This guide helps you decide whether your experience is deep enough to schedule the exam now, or whether you should first close specific knowledge and hands-on gaps.
What does the certification validate?
Passing exam 5V0-23.20 leads to the VMware Certified Specialist – vSphere with Tanzu certification. The associated specialist badge recognizes knowledge of how vSphere with Tanzu can orchestrate the delivery of Kubernetes clusters and containerized applications in a vSphere environment.
This is not simply a Kubernetes vocabulary test. The official objectives include identifying the purpose and role of a Supervisor Cluster, identifying the characteristics of Control Plane VMs, understanding vSphere with Tanzu core services, and identifying the characteristics and uses of the kubectl command-line interface.
The practical boundary of the exam is the platform operator’s view: how Kubernetes capabilities fit into vSphere, which components provide control, how workloads use platform services, and how an administrator investigates problems. Your preparation should therefore connect product architecture with operational actions rather than treating every topic as an isolated definition.
Who should take this exam?
The best candidate is a vSphere administrator, platform operator, consultant, or solution professional who already works with virtualization and is extending that background into Kubernetes-enabled infrastructure. The official minimum profile includes basic Kubernetes and container knowledge, at least 12 months of vSphere experience, and experience with NSX-T plus network, virtualization, and operating-system experience or education.
The exam guide recommends completing the recommended training courses and holding a valid VCP-DCV certification. Treat those recommendations as readiness signals, not as substitutes for understanding. A VCP-DCV holder who has never configured or investigated Tanzu components may still need substantial lab work; a strong vSphere operator may need to formalize certification and training requirements before scheduling.
A separate VMware Cloud Provider article recommends at least 6 to 12 months of experience with Tanzu Standard and the ability to describe VMware Tanzu Standard Edition components, including vSphere with Tanzu, Tanzu Kubernetes Grid, and Tanzu Mission Control. That recommendation is especially relevant if your role includes broader Tanzu operations rather than only the vSphere integration layer.
What are the exam facts to verify before booking?
The official exam guide identifies the exam as 5V0-23.20. It contains 62 items, uses a scaled passing score of 300, has a duration of 125 minutes, and is delivered as a proctored exam through Pearson VUE. Confirm the current registration and delivery information in the official certification system before making a booking decision.
The official exam guide was last updated on January 9, 2023. That date matters when planning: use the guide as the controlling reference for the documented exam objectives, but check the current Broadcom or VMware certification pages for any later scheduling, delivery, or policy changes. Do not rely on an older blog post for conflicting administrative details.
The time allocation works out to slightly more than two minutes per item on average, but that average is only a planning aid, not an official item rule. Build a pace that lets you answer straightforward recognition questions promptly, mark uncertain items, and return to them without sacrificing review time.
How is the blueprint weighted?
The published curriculum information for the v1.21 exam describes five domains: Cluster Architecture, Installation & Configuration is 25%; Workloads & Scheduling is 15%; Services & Networking is 20%; Storage is 10%; and Troubleshooting is 30%. Use the domain labels every time you prioritize study, because the percentages only make sense when attached to their official subjects.
Troubleshooting is the largest domain at 30%, so it deserves more than a final review session. Cluster Architecture, Installation & Configuration accounts for 25%, while Services & Networking accounts for 20%; together, these areas require a clear mental model of how the platform is assembled and connected. Workloads & Scheduling is 15%, and Storage is 10%, but neither should be ignored because smaller domains can expose foundational gaps.
The official exam guide also presents sections such as introducing vSphere with Tanzu and vSphere with Tanzu core services, while the published curriculum names the weighted domains. Map both views in your notes. For example, place Supervisor Cluster and Control Plane VM concepts under architecture, then connect them to the networking, storage, workload, and troubleshooting consequences you would investigate in practice.
How should the percentages change your study time?
A useful recommendation is to assign the largest block of study to Troubleshooting, followed by Cluster Architecture, Installation & Configuration and Services & Networking. This is a preparation choice, not an official allocation requirement. Increase the troubleshooting share further if you can describe components but cannot explain what evidence would distinguish a network fault from a storage or configuration fault.
Do not interpret the 10% Storage domain as permission to memorize a short glossary. Storage choices affect workload placement and application behavior, so study storage in relation to namespaces, classes, persistent workloads, and failure diagnosis. Likewise, Workloads & Scheduling becomes easier when you understand what the platform is scheduling and which services must be healthy first.
Which architecture concepts must be clear?
Start by being able to explain the purpose and role of a Supervisor Cluster in plain operational language. Then relate that role to Control Plane VMs, the vSphere environment, workload clusters, and the services that make Kubernetes operations possible. If you can only recite component names, your architecture preparation is incomplete.
Create a one-page dependency map with four columns: component, responsibility, configuration dependency, and failure symptom. Include the Supervisor Cluster, Control Plane VMs, core Tanzu services, networking, storage, workload clusters, and kubectl access. The goal is not to reproduce an undocumented design; it is to make each relationship explicit enough that you can reason through a scenario.
A common mistake is to treat the Supervisor Cluster as interchangeable with every Tanzu Kubernetes cluster. Your notes should distinguish the platform control plane from the clusters used to run workloads. Then test yourself with questions such as: Which layer is being described? What does it control? Which user or administrator action would interact with it? What would be affected if it were unavailable?
How should you study installation and configuration?
Study installation as a sequence of prerequisites and dependencies, not as a list of screens. Review the required vSphere foundations, network decisions, storage choices, Kubernetes integration points, and validation steps. The official preparation material recommends the relevant training courses; use course exercises and product documentation to confirm why each setting exists.
Build a configuration worksheet before entering a lab. Record the vSphere objects involved, the selected networks, storage classes, identity or access decisions, and the expected result after each major step. This turns a lab into a repeatable diagnostic exercise and makes it easier to identify whether a later failure came from an earlier prerequisite.
Do not spend all your time clicking through a successful deployment. Deliberately revisit the points at which configuration can be invalid, incomplete, or inconsistent. For each step, write down what you would verify if the next operation failed. That habit supports both the Installation & Configuration domain and the larger Troubleshooting domain.
What should you know about workloads, services, and networking?
Prepare to connect workload behavior with platform services and network design. The blueprint assigns 15% to Workloads & Scheduling and 20% to Services & Networking, so study how applications and clusters consume the environment rather than memorizing isolated Kubernetes terms.
Review basic Kubernetes objects and scheduling concepts until you can explain them without depending on a command reference. Then relate those concepts to the vSphere with Tanzu implementation you are studying. Practice identifying whether a scenario is primarily about placement, service exposure, connectivity, policy, or an underlying platform dependency.
Networking deserves special attention because the minimum candidate profile includes NSX-T and network experience. Make a troubleshooting tree that begins with the observed symptom and checks scope: one workload, one node, one cluster, or the shared platform. Next separate name resolution, reachability, service exposure, and infrastructure connectivity. This is a practical study method, not a claim about a specific exam scenario.
The official quick-start material for Tanzu Mission Control and vSphere with Tanzu services illustrates a broader operational workflow: create a cluster group, register a vSphere Supervisor Cluster as a management cluster, deploy a Tanzu Kubernetes cluster, and apply a basic policy. Use that workflow to understand how centralized management and policy organization relate to cluster operations.
How much Kubernetes and kubectl knowledge is needed?
The official objectives include identifying the characteristics and uses of the kubectl command-line interface, while the minimum candidate profile includes basic Kubernetes and container knowledge. You should be comfortable explaining what kubectl is used for, recognizing the purpose of common command categories, and interpreting basic resource or status information.
Study commands by task rather than by memorized alphabetic lists. Organize your notes around inspecting resources, reviewing events or logs, describing configuration, and checking workload state. For every command family, record the object it targets, the information it reveals, and the operational question it answers. Avoid inventing or memorizing flags that you cannot explain.
A useful drill is to begin with a symptom, choose the least invasive inspection step, and then decide what evidence would justify the next command. This builds the reasoning expected of an operator. It also reduces a common mistake: running commands randomly until something looks familiar, without linking the output to a hypothesis.
How should storage and troubleshooting be practiced?
Storage accounts for 10% of the published curriculum, while Troubleshooting accounts for 30%. Study storage as a dependency that can affect provisioning, scheduling, application persistence, and recovery. Study troubleshooting as a method: define the symptom, identify the affected layer, collect evidence, test the most likely cause, and verify the result.
Use a fault matrix with rows for architecture, configuration, networking, storage, workload state, and command-line access. For each row, write the observable symptom, the first evidence to collect, one likely cause, and one misleading explanation. This prevents a shallow approach in which every failure is treated as a generic Kubernetes problem.
When a lab works, break it carefully and document what changed. Examples of useful practice include altering a noncritical configuration, making a dependency unavailable in a controlled environment, or starting with an incomplete prerequisite and observing the resulting behavior. Only perform changes in an authorized lab. The value comes from documenting the diagnosis and recovery logic, not from creating disruption.
Do not prepare Troubleshooting by reading only solution steps. Hide the explanation, inspect the evidence, state your hypothesis, and explain why alternative causes are less likely. Then restore the environment and repeat the exercise from a different entry point.
Which labs and learning resources are worth using?
Hands-on practice is strongly supported by the supplied VMware Cloud Provider guidance, which recommends labs for vSphere with Tanzu and related Tanzu technologies. The listed examples include HOL-2113-01-SDC vSphere with Tanzu, HOL-2113-91-ISM vSphere with Tanzu – Lightning, HOL-2132-91-ISM VMware Tanzu Mission Control Simulation, HOL-2133-01-MAP VMware Tanzu Kubernetes Grid, and HOL-2133-81-ODY VMware Odyssey – Tanzu Kubernetes Grid – Getting Started.
Use each lab for a different purpose. A vSphere with Tanzu lab should anchor architecture, installation, configuration, and lifecycle understanding. Tanzu Mission Control practice should help you understand management and policy workflows. Tanzu Kubernetes Grid exercises should strengthen cluster operations and the relationship between platform services and workload clusters. Do not count a lab as complete merely because you reached the final screen; write a short explanation of every major action.
The quick-start article shows a concrete Tanzu Mission Control workflow. It describes creating a cluster group, registering a vSphere with Tanzu Supervisor Cluster, deploying a Tanzu Kubernetes cluster, and applying a basic policy. It also identifies prerequisites in its own 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 those details as prerequisites for that documented walkthrough, not automatically as universal booking requirements for every environment.
Tanzu Academy is described in the supplied VMware article as an on-demand learning hub with expert tutorials, guides, written lessons, and hands-on lab infrastructure. The article distinguishes free and paid membership options. Confirm current availability and access conditions directly before depending on a particular course or lab.
What is a practical study sequence?
A staged plan works better than alternating randomly between product pages and practice questions. First establish vSphere and Kubernetes foundations, then build the Tanzu architecture model, perform configuration work, practice workload and service operations, and finish with evidence-based troubleshooting. At every stage, turn reading into a demonstrable task or a written explanation.
Start with a readiness check. Confirm that you can explain basic containers and Kubernetes, describe vSphere networking and storage at an operational level, and identify where NSX-T knowledge is relevant. If any of those areas is unfamiliar, address it before spending most of your time on exam-specific review. Also check whether the recommended VCP-DCV and training expectations apply to your certification path.
Next, study the architecture and create your component dependency map. Use the official objectives as the boundary: Supervisor Cluster purpose and role, Control Plane VM characteristics, vSphere with Tanzu core services, and kubectl characteristics and uses. Add only supported product detail from the recommended training and official documentation you can access.
Then complete a guided vSphere with Tanzu lab and repeat the major operations without following the instructions line by line. Record prerequisites, inputs, validation checks, and likely failure points. After that, work through workload, services, networking, and storage exercises. Tie every exercise to one of the weighted curriculum domains so that weaker areas remain visible.
Finish with troubleshooting drills and a timed review using the documented 62-item, 125-minute format as a planning simulation. This is not a prediction of item types or a substitute for the official exam. It is a way to practice pacing, switching between recognition and reasoning, and reserving time to revisit uncertain answers.
A four-checkpoint roadmap
Checkpoint one is foundation readiness: explain Kubernetes and containers, verify your vSphere knowledge, and review NSX-T and networking fundamentals. Checkpoint two is platform understanding: draw the Supervisor Cluster and Control Plane VM relationships and explain the core services without notes.
Checkpoint three is operational repetition: deploy or configure the documented lab environment, inspect workloads, use kubectl for basic investigation, and connect service or network behavior to the underlying platform. Checkpoint four is diagnosis: work from symptoms to evidence, cover all five curriculum domains, and schedule only after you can explain your weaker domain clearly.
Keep a decision log during the roadmap. For each uncertain topic, label it as a terminology gap, architecture gap, command gap, or troubleshooting gap. Each label suggests a different remedy: glossary review, dependency mapping, command drills, or fault isolation practice.
What mistakes cause inefficient preparation?
The most expensive preparation mistakes are usually misdiagnosis and imbalance. Candidates often over-study Kubernetes basics while neglecting vSphere integration, memorize interface paths without understanding dependencies, or postpone troubleshooting until the final review. Correct those habits by linking every study session to a blueprint domain and an observable operational outcome.
Do not use exam dumps, leaked questions, or memorization schemes as a replacement for knowledge. They cannot establish that you understand a Supervisor Cluster, a Control Plane VM, core services, networking, storage, or kubectl usage, and reliance on unauthorized material creates an unreliable readiness signal.
Do not treat a successful lab as proof that you can troubleshoot. Repeat the workflow, explain each prerequisite, and inspect the system when the expected result does not appear. Also avoid taking old administrative claims at face value: the official guide is dated, and the current certification page should control booking details.
Finally, avoid measuring readiness by how many pages you have read. Use evidence instead: can you explain the architecture, carry out the relevant operation, interpret basic command output, and defend a troubleshooting sequence? If not, identify the exact missing skill and return to the corresponding lab or course section.
When should you schedule the exam?
Schedule after your preparation evidence matches the exam’s scope, not simply because you have completed a course. You should be able to explain the official objectives, perform relevant lab tasks, and troubleshoot across the weighted domains without relying on a memorized answer pattern. Confirm the current Pearson VUE process and any certification prerequisites before paying for an appointment.
Use a final readiness review with three outputs: a one-page architecture diagram, a domain-by-domain gap list, and a short troubleshooting playbook. The diagram should distinguish Supervisor Cluster, Control Plane VMs, workload clusters, and core services. The gap list should retain the official domain labels, including Troubleshooting at 30% and Storage at 10%. The playbook should show how you move from symptom to evidence and validation.
On exam day, follow the official appointment instructions and manage the documented 125-minute duration deliberately. Read each item for its scope and qualifiers, answer what the question asks, and mark uncertainty rather than allowing one difficult item to consume disproportionate time. This pacing advice is a practical recommendation, not a description of undisclosed test-center procedures.
What should you do next?
Download and read the official exam preparation guide first, then compare its objectives with your current experience. If you meet the vSphere, Kubernetes, container, NSX-T, and networking expectations, begin a lab-led plan. If you do not, resolve the foundation gap before attempting to memorize Tanzu-specific terminology.
Use the official training recommendations and the supplied hands-on resources to build evidence of competence. Keep a dated study record, but do not assume that elapsed study time equals readiness. Your next concrete action should be one of three choices: complete a foundation module, perform a targeted vSphere with Tanzu lab, or investigate a troubleshooting scenario tied to your weakest blueprint domain.
Before booking, recheck the official guide and current certification portal for exam code, prerequisites, delivery arrangements, and appointment information. After booking, reserve the final study period for retrieval practice, architecture explanation, command reasoning, and troubleshooting—not for collecting more disconnected notes.
Conclusion
This exam is best approached as a platform-operations assessment: vSphere knowledge provides the foundation, Kubernetes and kubectl provide the operating language, and Tanzu architecture connects the two. Prioritize the 30% Troubleshooting domain, build a reliable model of Supervisor Clusters and Control Plane VMs, and validate your understanding through authorized hands-on work. Use the official guide for documented requirements and the current certification system for scheduling decisions, then book when your lab evidence—not confidence alone—shows that you can reason across the full environment.
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
