NCA-5.20
Nutanix Certified Associate (NCA) 5.20 Exam
NCA-5.20 Exam Guide: Scope Checks, Product Context, and a Practical Study Plan
NCA-5.20 should be scheduled only after you confirm its current sponsor page, exam objectives, eligibility rules, and delivery instructions. The supplied official research does not publish an NCA-5.20 blueprint, passing standard, question format, duration, price, language list, or prerequisite. It does, however, provide current VMware Telco Cloud Platform 5.2 product context and official routes for locating support and exam-program information. This guide helps prospective candidates decide whether their experience matches the likely subject area, what to verify before booking, and how to build preparation around documented platform operations rather than unsupported question claims.
What can be confirmed about NCA-5.20?
The available official evidence does not identify NCA-5.20 by name or provide an authoritative exam description. Treat the exam code as a catalogue reference until the sponsor or testing provider confirms the associated certification, product version, audience, and objectives. Do not use the absence of a public blueprint as evidence that a particular topic, score, or delivery method applies.
The strongest available product evidence concerns VMware Telco Cloud Platform (TCP) 5.2. A VMware Telco Cloud Blog article states that TCP 5.2 is generally available and describes improvements in Kubernetes lifecycle management, policy enforcement, security posture, and container registry operations. That is useful study context only; it is not an NCA-5.20 exam specification.
Before committing study time, open the Broadcom Support Portal and locate the relevant product, learning, documentation, or certification material associated with NCA-5.20. The portal provides product documentation, Learnings, compatibility information, knowledge-base articles, and lifecycle resources: https://support.broadcom.com/
What remains unverified?
The supplied sources do not verify NCA-5.20’s official title, exam owner, certification relationship, candidate prerequisites, recommended training, blueprint domains, domain weights, passing score, number of questions, exam duration, supported languages, retake rules, expiration policy, test-centre availability, online-proctoring availability, or current status. A responsible candidate should obtain each item from the exam sponsor or the exam-program login page before scheduling.
The Certiport transcript page supplied for research confirms only page-level transcript information in the snapshot, including the text “Paper size: Standard A4 B5.” It does not establish NCA-5.20 registration, delivery, eligibility, or scoring rules. Do not treat a transcript page as an exam guide.
Who should consider this exam?
The relevant candidate profile cannot be stated as an official NCA-5.20 requirement from the supplied sources. If the exam is associated with VMware Telco Cloud Platform, the most defensible preparation audience is professionals who administer, upgrade, secure, troubleshoot, or govern Kubernetes-based telco workloads and who can consult the current product documentation. Confirm that association before using this profile to make a booking decision.
The TCP 5.2 product article describes operators managing Kubernetes at scale across multiple vendors, versions, and regulatory jurisdictions. It also discusses cloud-native network functions, cluster lifecycle operations, policy governance, security controls, and registry maintenance. Candidates working in those areas have a practical reason to investigate the exam, but the article does not say that NCA-5.20 requires this experience.
Use a skills-based decision rather than a job-title decision. Ask whether you can explain the operational effect of a platform change, identify the correct evidence in product documentation, reason about upgrade impact, and separate a policy violation from an application or network fault. If those tasks are unfamiliar, build product fundamentals before attempting exam-specific revision.
When is postponing the booking sensible?
Postpone scheduling when you cannot verify the sponsor’s current exam page, when your hands-on environment uses a materially different product release, or when you are relying mainly on memorized answers. Postponement is also sensible if you cannot describe how you would investigate a cluster lifecycle issue, policy event, registry upgrade, or pod-to-pod connectivity problem from documented procedures.
Do not infer a prerequisite from the existence of a product release. The official TCP 5.2 article describes capabilities and supported versions, not an NCA-5.20 eligibility rule. If the sponsor requires training, experience, another certification, or an account entitlement, only the sponsor’s current candidate instructions should settle the question.
Which skills are the best-supported preparation targets?
No official NCA-5.20 measured-skills list is included in the research. The following targets are therefore preparation priorities derived from the supplied TCP 5.2 product evidence, not a claimed exam blueprint: Kubernetes lifecycle management, cluster operations, policy governance, security posture, CNF registry operations, and operational troubleshooting. Verify these priorities against the official objectives before treating them as examinable domains.
The TCP 5.2 article says that extended support versions span Kubernetes 1.30, 1.33, and 1.36. It also says that lifecycle management and Create, Read, Update, and Delete operations continue to be supported for clusters running Kubernetes 1.33 and 1.30 through their respective end-of-support dates. Study the operational reason for version-aware planning instead of memorizing isolated version labels.
The article states that Kubernetes 1.36 carries a 24-month support window in this release and that support for Kubernetes 1.36 reduces the gap from upstream availability to three months. These are release-specific facts. Confirm that NCA-5.20 covers TCP 5.2 before making them part of a final revision sheet.
Kubernetes lifecycle and cluster placement
Prepare to reason through lifecycle decisions: version compatibility, upgrade sequencing, continued support for existing clusters, and continuity during planned maintenance. TCP 5.2 also supports rehoming CaaS workload clusters between management clusters, according to the official product article. A useful exercise is to document why an operator might rehome a workload cluster and what dependencies must be checked first.
Do not turn a release note into an implementation procedure. The article establishes that rehoming is supported, but it does not provide the complete command sequence, prerequisites, rollback plan, or environment-specific constraints. Use the official upgrade, reference architecture, and release-note resources named by the article for procedural study.
Policy governance with graduated enforcement
The official article describes Kubernetes Policy Manager as built on Open Policy Agent and says TCP 5.2 adds “warn” mode. It contrasts warn mode, which surfaces violations without stopping deployment, with deny mode, which blocks non-conforming workloads. Prepare by comparing the operational purpose of observation, remediation, and enforcement rather than memorizing the mode names alone.
The same source says policy configurations are preserved through cluster upgrades and node lifecycle events, unauthorized policy drift is automatically reconciled, and raw Rego policy templates are viewable in the platform. Turn each statement into a scenario: identify the intended control, the expected operator response, and the evidence you would collect when behavior differs from policy.
Security and traffic visibility
TCP 5.2 implements least-privileged credentials by default when the vSphere Cloud Provider Interface interacts with vCenter, according to the supplied official source. It also enables packet capture for pod-to-pod communications when using the Antrea CNI. These facts support study of privilege minimization and east-west traffic investigation, but they do not establish the exact NCA-5.20 troubleshooting workflow.
For preparation, write a short investigation map for a pod-to-pod communication problem: identify the affected workloads, confirm the network path and CNI context, determine whether packet capture is available, preserve relevant evidence, and distinguish an observation from a remediation. Consult current product documentation for permissions, retention, access, and operational safeguards rather than inventing commands.
Harbor and CNF supply-chain operations
The product article describes Harbor as the container registry CNF within the TCP ecosystem and says TCP 5.2 adds single-click upgrade support for Harbor. Study the lifecycle objective behind that capability: maintaining a current registry while protecting the availability and integrity of artifacts used by cloud-native network functions.
A practical exercise is to compare an upgrade plan with an ordinary application deployment plan. Record the prechecks, dependency review, change window, validation evidence, and rollback decision. The supplied source does not provide detailed Harbor upgrade steps or claim that an exam asks for a particular command, so keep the exercise documentation-led.
How should you prepare when no blueprint is available?
Use a verification-first study process. First obtain the current NCA-5.20 objectives and candidate rules; then map each objective to authoritative documentation, a practical task, and a self-test question written in your own words. Until the blueprint is confirmed, allocate time to the documented TCP 5.2 capabilities without calling any one topic a guaranteed exam domain.
Begin with product architecture and terminology, continue with lifecycle and governance workflows, then practise security and registry operations. Finish with mixed scenario review. This order reduces a common error: trying to memorize feature names before understanding which operational problem each feature addresses.
Keep three notes for every topic: what the product documentation explicitly states, what you have verified in a lab or supported environment, and what still requires confirmation. This separation prevents an assumption about NCA-5.20 from becoming a false study fact.
A four-stage study sequence
Stage one is scope confirmation. Find the current sponsor page, exam objectives, registration route, policies, and any version statement. Record the retrieval date in your notes because product and exam information can change. If the official page conflicts with catalogue text, follow the current sponsor instruction and seek clarification before paying or booking.
Stage two is concept mapping. Build a one-page map connecting management clusters, workload clusters, Kubernetes versions, CNFs, policy enforcement, vSphere CPI, Antrea, and Harbor. Add a “why it matters” sentence beside each item. The goal is to make relationships visible, not to create an oversized glossary.
Stage three is task practice. For lifecycle topics, analyse a version and maintenance scenario. For policy, compare warn and deny outcomes. For security, trace the evidence needed for least-privilege and traffic investigations. For Harbor, create a documented upgrade checklist. Do not use leaked questions or exam dumps; they cannot establish current objectives and memorization does not guarantee a pass.
Stage four is decision rehearsal. Practise selecting the next diagnostic or planning action from a scenario, explaining the reason, and naming the documentation you would consult. Review errors by cause: terminology confusion, missed dependency, incorrect sequence, unsupported assumption, or failure to distinguish observation from enforcement.
How to use product documentation efficiently
Read release notes for changed behavior, architecture material for component relationships, and upgrade guides for sequence and safeguards. The TCP 5.2 article specifically directs readers to release notes, a reference architecture, an upgrade guide, and related Telco Cloud resources. Use each source for the question it is designed to answer rather than treating one blog post as the full technical manual.
When a document says a capability is supported, ask four follow-up questions: for which component, under which version or CNI condition, with what operational effect, and with what limitation or prerequisite? This method is particularly important for the stated Kubernetes versions, the Antrea packet-capture condition, and Harbor lifecycle changes.
Create a citation-backed revision table with columns for feature, supported context, operator objective, verification method, and source URL. Remove any row whose source is only a forum comment, practice-question site, or unsourced summary.
What should a practical roadmap look like?
A useful roadmap is organized around decisions and evidence, not an arbitrary number of study days. Reserve the first block for scope and architecture, the next for lifecycle and governance, the next for security and registry operations, and the final block for mixed review and booking checks. Adjust the block lengths to your background and the confirmed NCA-5.20 objectives.
If your work is already centered on TCP operations, spend less time defining Kubernetes terms and more time testing upgrade, policy, and troubleshooting reasoning. If your background is general Kubernetes but not telco platforms, add time for CNF lifecycle, management-cluster relationships, and product-specific governance. If neither describes you, seek formal product learning or supervised practical work before relying on self-study alone.
Roadmap block one: confirm scope and foundations
Collect the official NCA-5.20 exam page, objectives, registration instructions, and current TCP documentation. Identify every term you cannot define without searching. Then study the platform’s component relationships and write a plain-language explanation of how workload clusters, management clusters, CNFs, Kubernetes versions, policy controls, and supporting services relate.
Your exit check is not a score. It is the ability to classify a question as architecture, lifecycle, governance, security, registry, or troubleshooting and to point to the authoritative document that should answer it.
Roadmap block two: practise lifecycle reasoning
Study the documented support position for Kubernetes 1.30, 1.33, and 1.36 in TCP 5.2, then build upgrade and maintenance scenarios. Include existing clusters, version dependencies, management-cluster continuity, and the possibility of rehoming CaaS workload clusters. Explain the risk of making a change without checking CNF and version compatibility.
Your exit check is a written sequence of precheck, change, validation, and contingency decisions. Keep product facts tied to their exact release context; do not generalize TCP 5.2 behavior to every VMware or Kubernetes environment.
Roadmap block three: practise governance and security
Compare warn and deny policy outcomes using deployment examples. Review OPA, Rego visibility, policy preservation through lifecycle events, and automatic reconciliation of unauthorized drift. Then study the least-privileged vSphere CPI credential behavior and Antrea packet capture for pod-to-pod communications.
Your exit check is the ability to explain what an operator should observe first, which control is involved, and whether the situation calls for diagnosis, remediation, or enforcement. A response that names a feature without explaining its operational effect is incomplete preparation.
Roadmap block four: consolidate and verify booking readiness
Create mixed, original scenarios from the official documentation and answer them without looking at notes. Revisit every error and label it as a knowledge gap, reading error, sequencing error, or unsupported assumption. Then recheck the official exam page for eligibility, registration, delivery, and policy information before scheduling.
Do not schedule merely because you can recite release highlights. Schedule when the confirmed objectives are covered, your practical reasoning is consistent, and the administrative details are verified through the current sponsor or testing-provider route.
How do you verify registration and delivery details?
Use the exam sponsor’s current instructions for registration and Pearson’s program directory or login route only to locate the correct exam programme. The supplied Pearson pages explain that candidates select a testing programme and may be redirected to the programme’s own website. They do not verify that NCA-5.20 is delivered by Pearson, at a test centre, online, or through another provider.
Start with Pearson’s alphabetical programme directory: https://www.pearsonvue.com/us/en/test-takers/a-to-z-program-list.html. If the relevant programme is listed, follow its official link and read the current candidate instructions. The Pearson login directory is also available at https://www.pearsonvue.com/gb/en/test-takers/log-in.html. Do not assume that a directory or login page supplies the exam’s technical objectives.
Before payment or appointment selection, confirm the exact exam code, sponsor name, account used for registration, acceptable identification, accommodations process, rescheduling and cancellation rules, delivery options, and any system-check requirements. None of those NCA-5.20 details is verified by the supplied research, so they must remain booking checks rather than asserted article facts.
What if the exam cannot be found?
If NCA-5.20 does not appear under the expected sponsor or programme, stop and investigate rather than selecting a similarly named exam. Check the Broadcom Support Portal, the sponsor’s certification material, and the current testing-provider directory. Keep screenshots or reference details for your own records, but rely on the current official instruction for the final decision.
A missing listing may reflect a naming difference, an account-specific route, a programme transition, or incomplete catalogue context; the supplied sources do not establish which explanation applies. Contact the sponsor or testing provider through the official support route when the code, title, and registration path do not align.
Which preparation mistakes create the most risk?
The most serious mistake is studying an assumed blueprint. Because the supplied research does not publish NCA-5.20 objectives, candidates should not treat TCP 5.2 release notes as a complete exam outline. Other avoidable errors include confusing product availability with certification requirements, ignoring version context, memorizing feature names without operational reasoning, and booking before confirming the programme and policies.
A second mistake is treating every product statement as universal. Kubernetes 1.36 support, the 24-month support window, the three-month upstream gap, Antrea packet capture, and Harbor single-click upgrades are all presented in the TCP 5.2 release context. Preserve that context in notes and verify whether NCA-5.20 uses the same version scope.
A third mistake is practising only recognition. Multiple-choice preparation, if applicable, should still require an explanation: why is the selected action appropriate, which condition makes it valid, and what evidence would disprove it? Do not infer the actual question format from this recommendation.
A final self-audit before booking
Can you identify the official NCA-5.20 sponsor and current objectives? Can you distinguish verified requirements from product context? Can you explain the operational purpose of Kubernetes lifecycle support, warn and deny policy modes, least-privileged CPI access, Antrea packet capture, and Harbor upgrades without claiming unsupported procedures? Can you locate the current registration and policy instructions?
If any answer is no, make that the next action. Retrieve the missing source, update your study map, and repeat the check. This is more reliable than adding another unsourced practice set or trying to predict questions.
What should you do next?
First, confirm the NCA-5.20 title, sponsor, blueprint, prerequisites, and registration route from the current official programme material. Second, use the Broadcom portal and the TCP 5.2 product article to build a source-backed technical checklist. Third, practise lifecycle, governance, security, and registry scenarios while marking assumptions clearly. Finally, verify delivery and policy details immediately before scheduling.
The TCP 5.2 article is useful for current product context: https://blogs.vmware.com/telco/whatsnewtcp5-2/. The Broadcom portal is the appropriate starting point for product documentation and learning resources: https://support.broadcom.com/. Pearson’s supplied directories can help locate a testing programme, but they do not replace sponsor confirmation.
NCA-5.20-specific facts should be added to this preparation plan only after an official source confirms them. Until then, the safest candidate decision is to prepare against documented TCP 5.2 operations, avoid unsupported claims about the exam itself, and delay booking if the exam identity or rules remain unclear.
Conclusion
The available evidence supports a careful preparation direction, not a fabricated NCA-5.20 specification. Use verified TCP 5.2 documentation to develop platform reasoning around Kubernetes lifecycle management, policy governance, security, traffic visibility, and Harbor operations, while separately confirming the exam’s official scope and administrative rules. That separation gives you a defensible study plan and prevents a catalogue code or product article from being mistaken for a current exam blueprint.