5V0-23.20
VMware vSphere with Tanzu Specialist
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 usage. It is aimed at candidates who already understand vSphere and have foundational Kubernetes, container, networking, NSX-T, virtualization, and operating-system knowledge. This guide helps you decide whether your experience is sufficient, which domains deserve the most study time, how to build practical skill, and when to verify the official scheduling requirements before booking.
What does the certification validate?
Passing exam 5V0-23.20 leads to the VMware Certified Specialist – vSphere with Tanzu certification. The focus is not general Kubernetes theory alone; it is the relationship between vSphere administration and the Kubernetes capabilities delivered through vSphere with Tanzu.
The official objectives include identifying the purpose and role of a Supervisor Cluster, recognizing the characteristics of Control Plane VMs, understanding vSphere with Tanzu core services, and identifying the characteristics and uses of the kubectl command-line interface. These objectives point to an operator-oriented exam: you need to understand platform components, their responsibilities, and the commands or decisions used to work with them.
A useful way to frame the certification is platform translation. A vSphere administrator must understand how namespaces, networking, storage, control planes, and workload clusters fit into a Kubernetes operating model. A Kubernetes practitioner must understand what the vSphere layer contributes and where its administrative boundaries lie. Study both sides rather than treating Tanzu as an isolated product.
Who should take this exam?
The exam is a reasonable target for a vSphere professional moving into Kubernetes platform operations, provided that person already has the required foundation. The official minimally qualified candidate has 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 official exam guide recommends completing the recommended training courses and holding a valid VCP-DCV certification. Treat those as important readiness signals, not items to skim past. If your vSphere knowledge is weak, Tanzu troubleshooting will become harder because many failures cross the boundary between Kubernetes objects and vSphere infrastructure.
A separate VMware Cloud Provider article describes candidates with at least 6 to 12 months of Tanzu Standard experience as being able to understand and describe components including vSphere with Tanzu, Tanzu Kubernetes Grid, and Tanzu Mission Control. That is useful practical guidance for experienced candidates, but the Broadcom exam guide remains the better source for the exam’s stated candidate profile.
Before scheduling, write down your evidence for each prerequisite area: vSphere administration, Kubernetes objects and containers, NSX-T and networking, operating systems, and Tanzu platform work. A gap in one area should change your preparation sequence rather than being hidden beneath product memorization.
What are the exam facts?
The official exam guide identifies the VMware vSphere with Tanzu Specialist exam as 5V0-23.20. It contains 62 items, uses a scaled passing score of 300, and has an exam duration of 125 minutes. The exam is delivered as a proctored exam through Pearson VUE.
These details are tied to the official guide, which was last updated on January 9, 2023. Because registration rules, delivery policies, and product versions can change, verify the current Broadcom exam information and Pearson VUE appointment information before paying for or selecting an appointment.
The provided VMware Cloud Provider article contains older or conflicting timing descriptions, including a separate reference to actual exam time and appointment time. Do not combine those figures with the official guide’s duration. For scheduling decisions, use the current official exam guide and the booking system rather than an older experience report.
The score is scaled, so a candidate should not translate 300 into a fixed percentage of correct answers. The official material does not provide a reliable conversion formula. Use the score requirement as a readiness checkpoint and measure yourself by domain coverage, scenario reasoning, and practical task accuracy.
How are the measured skills distributed?
For the v1.21 curriculum described in the VMware Cloud Provider source, Cluster Architecture, Installation & Configuration represents 25% of the exam, Workloads & Scheduling represents 15%, Services & Networking represents 20%, Storage represents 10%, and Troubleshooting represents 30%. Each percentage belongs to its named domain; do not compare the percentages as unlabeled figures.
The distribution makes troubleshooting the largest named domain, while architecture and installation, services and networking, workloads and scheduling, and storage make up the remaining coverage. This should influence study time, but it should not lead you to ignore smaller domains. A storage question can still expose a gap that causes problems in installation or troubleshooting.
Cluster Architecture, Installation & Configuration at 25% deserves an early study block because it provides the platform map. Learn the role and purpose of the Supervisor Cluster, the characteristics of Control Plane VMs, the services involved, and the configuration relationships that allow workloads to run.
Workloads & Scheduling at 15% should be studied through placement and operational scenarios. Focus on how Kubernetes workloads are represented and scheduled, what assumptions a workload makes about resources, and how platform configuration affects the result. Avoid learning command syntax without understanding the object or service being changed.
Services & Networking at 20% is a bridge between NSX-T, vSphere networking, and Kubernetes connectivity. Build a clear path from the workload or cluster requirement to the network service that supports it. Include ingress or service exposure concepts only to the extent supported by the current objectives and training material you use.
Storage at 10% is smaller by weight but important because persistent workloads require more than a generic statement that storage is available. Study storage classes, their selection, and how storage configuration relates to namespaces, clusters, and application needs.
Troubleshooting at 30% should receive the largest deliberate practice allocation. Practice identifying the layer where a failure begins: Kubernetes object, control plane, Supervisor Cluster, network, storage, vSphere resource, or operating system. Then decide what evidence would confirm or reject that hypothesis.
What should you know about the platform architecture?
Start with a component map: vSphere infrastructure, the Supervisor Cluster, Control Plane VMs, vSphere with Tanzu core services, and the Kubernetes workloads or Tanzu Kubernetes clusters they support. The exam expects recognition of roles and characteristics, so draw the relationships until you can explain them without relying on product labels alone.
For the Supervisor Cluster, answer three questions in your notes: what role does it play, what does it manage or enable, and how does it differ from a workload cluster? The official objective specifically calls for identifying its purpose and role. A diagram that shows ownership and communication paths is more useful than a glossary definition.
For Control Plane VMs, distinguish their characteristics from those of ordinary application workloads. Record where they fit in the control-plane design, what depends on them, and which symptoms could indicate a control-plane issue. Do not infer implementation details that your current product documentation or training does not support.
Create a service inventory for vSphere with Tanzu core services. For every service, document its purpose, dependencies, configuration inputs, and likely failure symptoms. This exercise prepares you for questions that ask which component is relevant rather than merely asking you to recall a definition.
Use two diagrams: one showing the management and control-plane relationships, and another showing a request path from a developer or platform operator to a running workload. Annotate the diagrams with vSphere, Tanzu, Kubernetes, networking, and storage boundaries. Revisit them during troubleshooting practice.
How should you prepare hands-on skills?
Hands-on practice should reproduce the decisions behind the objectives: inspect the platform, identify the relevant cluster or service, configure an appropriate resource, use kubectl to inspect state, and isolate a failure. The supplied VMware material specifically recommends hands-on labs for vSphere with Tanzu and points candidates toward Tanzu Kubernetes Grid and Tanzu Mission Control practice.
Begin with a clean environment or lab walkthrough. Record the starting state, prerequisites, network assumptions, storage choices, and expected result before clicking through a procedure. After completing it once, repeat the task from your notes without copying the steps. The second pass reveals whether you understand the workflow or only recognized the screens.
The VMware quick-start material describes a workflow involving a cluster group, registration of a vSphere with Tanzu Services Supervisor Cluster with Tanzu Mission Control, deployment of a Tanzu Kubernetes cluster, and creation of a basic policy. It also identifies prerequisites such as a vCenter environment with Tanzu Services enabled, a vSphere namespace, suitable network connectivity, and dedicated virtual distributed switch networks for workload clusters.
That quick-start workflow is especially useful for understanding boundaries. Tanzu Mission Control can organize clusters and apply policies, while the Supervisor Cluster is the vSphere Kubernetes control plane that can be registered as a management cluster. Practice explaining which system is being configured at each step and why.
The same guide describes selecting a Kubernetes version, network settings, and desired storage classes during a configuration step. Recreate the decision in your notes: what is being selected, which prerequisite makes it available, and what symptom would appear if the network or storage choice were unsuitable.
Use the official lab and documentation links as learning sources, not as a promise of the exact exam interface or questions. Product interfaces and versions can change. The goal is transferable diagnosis and administration, not memorizing a click path.
How do you build kubectl competence?
You do not need to memorize isolated kubectl commands; you need to recognize how the command-line interface helps you inspect and reason about Kubernetes state. The official objectives include identifying kubectl characteristics and uses, so practice selecting commands by purpose: discover resources, inspect configuration, view status, read events or logs where appropriate, and compare desired state with observed state.
Build a short command notebook organized by task rather than alphabetically. Include the resource being inspected, the information you expect to find, and the next decision that information enables. For example, a status result should lead to a question about conditions, events, configuration, scheduling, networking, or storage—not simply to another command chosen at random.
Practice safely in a lab. Use read-oriented inspection first, then make one controlled change and verify the result. After each exercise, explain which layer the command addresses and which layer it does not address. A Kubernetes command cannot by itself prove that an underlying vSphere or NSX-T dependency is healthy.
A common mistake is treating a successful command response as proof that the application is working. Separate API acceptance from actual readiness, scheduling, connectivity, and persistence. Your notes should distinguish object existence, desired configuration, observed status, and end-to-end application behavior.
Another mistake is memorizing syntax without context. If you forget a flag, the more valuable skill is knowing what evidence you need and where to obtain it. Combine command practice with architecture diagrams and failure scenarios so that each command supports a diagnosis.
How should you study troubleshooting?
Allocate the largest study block to troubleshooting because Troubleshooting represents 30% of the v1.21 curriculum described in the supplied source. Use a repeatable fault-isolation method: define the symptom, identify the affected scope, check dependencies in order, gather evidence, and choose the least disruptive corrective action.
Create scenarios across several layers. Examples include a workload that does not schedule, a service that cannot reach its endpoint, a cluster operation that does not complete, a storage request that cannot be satisfied, and a control-plane component that reports an unhealthy condition. These are practice scenarios, not claims about particular exam items.
For each scenario, write a decision tree. Start with scope: one pod, one namespace, one cluster, or the platform broadly. Then check the object state, events and logs available to you, resource and scheduling conditions, network dependencies, storage configuration, and relevant vSphere or Tanzu services. Stop searching once evidence identifies the responsible layer.
Do not make the common leap from symptom to cause. A pod that is not ready may involve its specification, scheduling, image or container behavior, networking, storage, or a dependent service. Conversely, a Kubernetes error may be reporting a failure rooted in vSphere infrastructure. Track dependencies in both directions.
Practice explaining why an answer is preferable. If two actions appear plausible, select the one that is supported by the evidence and has the narrower operational impact. Certification questions often test whether you understand sequence and scope, not whether you can name the largest number of possible causes.
After each lab failure, reset the environment and reproduce it if possible. Record the first observable symptom, the first useful diagnostic, the misleading clue, and the final dependency that mattered. This produces a troubleshooting reference you can review quickly before the exam.
What study sequence works best?
A four-stage sequence is more effective than reading every topic with equal intensity: establish foundations, map the Tanzu architecture, practice administration and kubectl, then run troubleshooting reviews. Schedule the exam only after you can move between vSphere and Kubernetes explanations without a major knowledge gap.
Stage one is a readiness audit. Confirm your vSphere background, Kubernetes and container fundamentals, NSX-T and networking understanding, and operating-system knowledge. If one category is missing, repair it first. The exam guide recommends valid VCP-DCV certification and recommended training, so check your certification and training position against the current official guidance before making a booking decision.
Stage two is architecture and core services. Read the official exam objectives and turn every objective into a question you can answer. Draw the Supervisor Cluster and Control Plane VM relationships, list core services, and explain how namespaces, networking, and storage support workloads. At the end of this stage, you should be able to teach the platform map to another administrator.
Stage three is guided implementation. Complete relevant training and hands-on labs, then repeat key tasks from notes. Include a Tanzu Kubernetes Grid or Tanzu Mission Control exercise where available, because the supplied VMware resources emphasize practical work with these technologies. Keep a failure log rather than recording only successful procedures.
Stage four is exam-directed review. Allocate time according to the labeled curriculum domains: 25% Cluster Architecture, Installation & Configuration; 15% Workloads & Scheduling; 20% Services & Networking; 10% Storage; and 30% Troubleshooting. These percentages describe the v1.21 curriculum in the supplied source, so verify that the version you are preparing for still matches the current official information.
In the final review, stop collecting unrelated material. Revisit missed objectives, redraw architecture from memory, perform a short kubectl inspection exercise, and work through troubleshooting decisions without looking at the answer first. Your final checkpoint should be confidence in reasoning, not familiarity with copied questions.
A practical weekly plan
In the first study block, audit prerequisites and refresh vSphere and Kubernetes fundamentals. In the next block, build the platform map and review Supervisor Cluster, Control Plane VM, and core-service objectives. Reserve later blocks for hands-on configuration, kubectl inspection, networking and storage scenarios, and troubleshooting. End each week with a closed-book explanation of one complete workflow.
Which mistakes waste preparation time?
The most damaging preparation mistakes are studying a product label instead of a dependency, ignoring the platform prerequisites, and relying on recalled questions. Correct those habits by tying every note to an objective, a component relationship, or a diagnostic decision that you can demonstrate in a legitimate lab or documentation exercise.
Do not treat a general Kubernetes course as complete Tanzu preparation. Kubernetes and containers are stated foundations, while the exam also concerns vSphere with Tanzu architecture, services, and operational boundaries. Learn the integration points rather than assuming that Kubernetes behavior alone explains the platform.
Do not study only installation. Installation and configuration matter, but Troubleshooting represents 30% of the described v1.21 curriculum. A candidate who can follow a deployment guide but cannot identify whether a failure is in scheduling, networking, storage, or the underlying platform has an incomplete preparation profile.
Do not memorize screenshots or navigation paths. The supplied quick-start guide is useful for understanding workflows, but interfaces and supported versions can change. Replace screenshot recall with a sequence of questions: what is the goal, what prerequisite is required, which component owns the setting, and how will success be verified?
Do not confuse recommendation with a guaranteed exam requirement. The official guide recommends training and a valid VCP-DCV certification, while candidate-profile statements describe expected knowledge and experience. Confirm the current certification policy and registration conditions through the official source before assuming that a historical article applies to your appointment.
Do not use exam dumps or leaked questions. They do not establish operational understanding, may be inaccurate or unauthorized, and cannot guarantee a passing result. Use the official objectives, training, documentation, and hands-on environments instead.
How should you use official resources?
Use the Broadcom exam prep guide as the authority for exam code, objectives, scoring, duration, delivery, and the stated candidate profile. Use VMware Tanzu articles for practical context and workflows, then verify that any product or version detail still applies to your exam attempt before building it into your study plan.
Begin with the official exam prep guide and make an objective checklist. Mark each objective as understand, can explain, can perform, or can troubleshoot. A topic should not be marked ready merely because you have read it. The checklist exposes the difference between recognition and usable skill.
The VMware Cloud Provider resource is valuable for preparation ideas, experience expectations, and suggested learning resources, but it is dated and includes historical certification context. Use its lab suggestions and broad study direction while relying on the current official exam guide for authoritative exam facts.
The VMware quick-start guide provides a concrete example of cluster grouping, Supervisor Cluster registration, Tanzu Kubernetes cluster deployment, policy application, and configuration choices involving networking and storage. Read it actively: annotate each step with the component responsible, prerequisite, expected state, and likely failure point.
Tanzu Academy is described by VMware as an on-demand learning hub with curated tutorials, guides, and hands-on lab infrastructure, with free and paid membership options. Treat it as a potential learning resource, not as evidence that every current exam objective or delivery detail is covered. Map any course or lab back to the official objectives.
Keep a source log. Record the URL, the product version or date shown by the material, the objective it supports, and any question that remains unresolved. This prevents older blog guidance from silently becoming your assumption about current exam policy.
When are you ready to schedule?
Schedule only after you have checked the current official exam information and can demonstrate readiness across both platform knowledge and diagnosis. A sensible final decision requires more than a practice score: you should be able to explain the architecture, perform representative lab tasks, use kubectl for inspection, and troubleshoot without depending on memorized answers.
Use this readiness checklist: you can explain the Supervisor Cluster’s role; distinguish Control Plane VMs from ordinary workloads; describe vSphere with Tanzu core services; identify useful kubectl applications; trace network and storage dependencies; and work through a failure using evidence. Also confirm the current Pearson VUE process, appointment conditions, and any certification or training requirement shown by the official registration path.
Do not schedule simply because you have completed a course. Training can expose the platform, but practical repetition shows whether you can apply it. Conversely, do not wait for perfect familiarity with every Tanzu feature. Concentrate on the published objectives and close demonstrable gaps rather than expanding the scope indefinitely.
Before the appointment, review the official guide again for changes, organize your identification and appointment information according to the current provider instructions, and avoid relying on an old blog’s timing or delivery description. The official guide states proctored Pearson VUE delivery, but the current booking process should control your final logistics.
What should you do after reading this guide?
Your next action is to turn the exam objectives into a gap list, then choose one practical exercise for each weak area. Start with the official exam guide, validate your candidate profile and current exam facts, and use labs or training to convert unfamiliar platform relationships into repeatable operational decisions.
First, confirm that your target is exam 5V0-23.20 and read the current Broadcom preparation material. Second, mark your knowledge of architecture, core services, kubectl, networking, storage, workloads, and troubleshooting. Third, select hands-on work that addresses the lowest-confidence categories instead of repeating tasks you already know.
Next, build a one-page troubleshooting map. Include the affected scope, the first evidence to collect, the dependencies to check, and the safe verification step after a correction. Add commands only when you understand what information each command provides.
Finally, review the labeled domain distribution from the source you are using, check current registration details through the official channel, and schedule only when your practical evidence supports the decision. The purpose of preparation is not to predict questions; it is to make platform behavior understandable enough that unfamiliar scenarios can still be analyzed.
Conclusion
The strongest preparation combines vSphere administration, Kubernetes fundamentals, Tanzu architecture, and disciplined troubleshooting. Use the official exam guide for authoritative facts and objectives, use VMware’s practical resources to structure lab work, and let your own evidence decide when to schedule. If you can explain component responsibilities, verify state with appropriate tools, and isolate failures across platform layers, your preparation is aligned with what this Specialist certification is designed to validate.
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