The recent announcement from Broadcom about three new VCAP exams for VMware Cloud Foundation 9 marks a significant shift in how VMware validates expertise across its private cloud stack. Previously, the VCAP track was organized around functional pillars such as Automation, Operations, Storage, VKS, and Networking, each demanding deep specialization in a single domain. The new role‑based exams—Administrator, Architect, and Support—cut across those pillars, testing a candidate’s ability to work with the entire VCF 9 platform from a specific operational perspective. This dual‑dimension approach mirrors the matrix organizations often use to balance depth and breadth, allowing professionals to demonstrate either niche mastery or holistic competence. For the market, it signals a growing demand for versatile cloud engineers who can navigate complex, multi‑tenant environments while still valuing deep technical specialists. The change also reflects Broadcom’s strategy to align certification paths with real‑world job functions, making credentials more directly applicable to hiring managers seeking particular role‑fit.
Understanding the new structure is easiest when visualizing it as a matrix where the existing pillar exams form the vertical axis and the three role‑based exams form the horizontal axis. A pillar exam, such as VCAP‑VCF Networking, requires the candidate to design, deploy, and troubleshoot NSX within a VCF context, covering the full lifecycle of that single component. In contrast, the role‑based exams slice horizontally: the Administrator exam addresses configuration tasks across all five pillars, the Architect exam covers design considerations spanning the same areas, and the Support exam focuses on troubleshooting and optimization throughout the stack. This arrangement ensures minimal overlap while delivering comprehensive coverage; holding all three role‑based certifications effectively means a professional has been assessed on every major objective in the VCF 9 blueprint. For employers, this provides a clearer signal about a candidate’s readiness to handle end‑to‑end responsibilities in a specific capacity.
Logistically, Broadcom has standardized the mechanics of the three new exams to create a consistent candidate experience. Each test comprises 60 items delivered over a 135‑minute appointment, with a passing threshold set at a scaled score of 300. The price point sits at USD 250 per attempt, and all exams are proctored through Pearson VUE. The extended duration compared to the legacy 40‑item VCP exams is explicitly intended to accommodate non‑native English speakers, giving them additional time to parse scenario‑based questions. Item variety has also increased beyond simple multiple choice; candidates will encounter multiple‑selection, build‑list, matching, drag‑and‑drop, point‑and‑click, and hot‑area formats. Notably, the Support exam guide flags two objectives as “Simulations,” hinting at interactive, hands‑on style items that approach the practical depth seen in former VCAP‑DCV Deploy labs, though stopping short of a full live‑lab environment.
The Administrator exam (3V0‑11.26) targets professionals responsible for the day‑to‑day operation of multi‑region or multi‑organisation VCF private clouds. Its blueprint concentrates entirely on Section 4 of the master framework, encompassing 60 objectives that span installation, configuration, and administrative tasks. The opening block (objectives 4.1‑4.18) revisits the infrastructure layer, covering vSAN cluster deployment, stretched clusters, cross‑cluster capacity sharing, storage policies, encryption, and vCenter performance tuning—content that will feel familiar to those with a vSphere or vSAN background. However, the exam quickly moves into newer territory introduced with VCF 9, such as the Provider Management portal, Organizations, the Provider Consumption Organization (PCO), and the “All Apps Organization” model that brings Projects, Governance Policies, Namespace Classes, and VPC connectivity profiles into play. This shift reflects the platform’s evolution toward a more consumable, service‑oriented private cloud.
Continuing through the Administrator objectives, the section covering the Supervisor (4.30‑4.34) delves into creating Supervisors with NSX VPC, NSX Segment, vDS, or Avi load‑balancer options, managing add‑on services like Harbor and external‑dns, and executing rolling updates of VKS clusters. The operational management layer (4.35‑4.47) introduces concepts such as resource reclamation, rightsizing, capacity forecasting via What‑If scenarios, cost management policies, the distinction between Business Intent and Operational Intent, Business Applications, alerting, fleet scaling and upgrades, SSO through Identity and Access Management, and configuration drift monitoring. Finally, the networking block (4.48‑4.60) addresses NSX Federation in VCF, Edge clusters, Tier‑0 and Tier‑1 gateways, VRF, segments, VPCs, DHCP, NAT, tenancy models, and operational tasks like syslog and backup/restore. Despite not being a networking‑focused certification, the Administrator exam demands a solid grasp of NSX concepts because they are integral to running a modern VCF environment.
The Architect exam (3V0‑12.26) serves as the design counterpart, appealing to professionals who craft the blueprints that others implement. Its scope covers Sections 1 through 3, amounting to 20 objectives that explore IT architectures, VMware product solutions, and the full plan‑and‑design process. Section 1 grounds candidates in design methodology: differentiating business versus technical requirements, separating assumptions from constraints, applying the AMPRS qualities (availability, manageability, performance, recoverability, security), forming design decisions, and devising validation strategies. This section is intentionally platform‑agnostic, emphasizing the discipline of architecture rather than VCF specifics. Section 2, though brief, challenges candidates to discern between merely supported design choices and those that are truly recommended, pushing them to evaluate when to adopt VCF Advanced Services versus sticking to core offerings—a nuance that often separates theoretical knowledge from practical judgment.
Section 3 forms the heart of the Architect exam, walking candidates through the end‑to‑end design flow: gathering and analyzing business objectives, building conceptual models, translating them into logical and physical VCF designs, and then addressing each of the AMPRS qualities with dedicated objectives. Three additional objectives introduce newer considerations: designing for identity management (tying into VCF Identity Broker), shaping a consumption strategy for VCF (leveraging VCF Automation), and planning a monitoring strategy (drawing on VCF Operations). These additions reflect the platform’s maturation, requiring architects to think beyond raw compute and storage to encompass service delivery, user experience, and observability. For those accustomed to producing High‑Level Designs for VCF customers, much of this will feel like a formalization of existing practice, but the exam demands rigorous reasoning about newer constructs such as VKS, VPCs, stateful NSX gateway services, and the Provider/Organization model of VCF Automation.
The Support exam (3V0‑13.26) fills a gap that existed in earlier VMware certification tracks by focusing explicitly on maintaining and troubleshooting VCF components against service‑level objectives. Aimed at platform support engineers, escalation contacts, and those who routinely interact with Broadcom support, the exam resides entirely in Section 5 and comprises 30 objectives organized by technology area. It begins with storage, expecting candidates to monitor and troubleshoot vSAN as well as any supported non‑vSAN storage using tools available within VCF. The workload domain section follows, covering the identification of appropriate diagnostic tools and the troubleshooting of ESX hosts, workload‑domain vCenter, clusters, and individual virtual machines, paired with performance‑optimization guidance for both the infrastructure and the VMs it hosts. This foundation ensures that support professionals can keep the core compute and storage layers healthy before moving up the stack.
Moving upward, the Support exam allocates three objectives to VCF Automation, focusing on oversight via VCF Operations, the Provider Management portal, and the All Apps Organization structure. VKS receives four objectives, covering the diagnosis of Supervisor and VKS cluster provisioning failures, connectivity or namespace issues, container deployment problems, registry and trusted certificate authority errors, recovery from failed upgrades, and performance optimization through monitoring and scaling. VCF Operations appears dually—as a subject to be troubleshot (examining Cloud Proxy, clusters, HA, adapters) and as a tool for diagnosing broader VCF configuration, network, and workload issues, including working with alerts generated by Operations for Networks and Operations for Logs. The final NSX block challenges candidates to select the proper VCF tool for a given NSX problem, address common infrastructure and connectivity issues, and tackle routing challenges. Two objectives are flagged as simulations, specifically referencing ECMP with high availability and the logical routing packet walk, indicating that candidates should be prepared to demonstrate deep packet‑flow understanding, a skill historically honed in lab‑centric exams.
Each of the new role‑based exams points to a recommended series of six courses, one for each pillar plus VKS, tailored to the exam’s flavor: Advanced Configuration for Administrator, Advanced Design for Architect, and Advanced Troubleshooting for Support. This results in eighteen distinct courses across the three tracks, underscoring the sheer scale of VCF 9 and the breadth of knowledge required to master it. For seasoned administrators, the vSphere, vSAN, and NSX portions may be approachable through hands‑on lab time and Broadcom’s TechDocs, but the newer Automation and VKS domains often prove more challenging to grasp from documentation alone. Consequently, the prescribed training paths become especially valuable for rapidly building practical competence in those evolving areas, reducing the reliance on trial‑and‑error in production environments.
From a market perspective, the introduction of role‑based VCAPs aligns with broader industry trends that favor hybrid skill sets. Organizations running private clouds increasingly seek engineers who can operate across silos—combining infrastructure expertise with automation fluency and container‑orchestration awareness—while still valuing deep specialists for complex escalations. The certification matrix enables professionals to signal either focus: a pillar VCAP declares “I am the go‑to expert for NSX or vSAN,” whereas a role‑based VCAP announces “I can design, operate, or support an entire VCF 9 private cloud.” Employers can thus match credentials to specific job functions, potentially reducing hiring mismatches. Moreover, the steady price and uniform exam structure make it easier for training providers to build predictable curricula and for individuals to plan certification roadmaps without worrying about disparate formats or costs.
Strategically, candidates should consider their current responsibilities and career aspirations when choosing which exam to pursue first. If you spend most of your time ensuring that VCF environments run smoothly—patching, scaling, managing tenants, and watching over services—the Administrator exam is the natural entry point; it validates the operational breadth you already exercise daily. Those who transition into support or escalation roles, especially anyone who has been called upon when a Supervisor refuses to provision or a VKS cluster misbehaves, will find the Support exam directly relevant to their troubleshooting workflow. Architects and consultants who spend their days drafting logical and physical designs, evaluating trade‑offs, and presenting solutions to stakeholders should prioritize the Architect exam, as it formalizes the decision‑making framework that underpins effective cloud design.
For those aiming to collect all three role‑based credentials, a sensible sequencing is to start with Administrator, then move to Support, and finish with Architect. The Administrator blueprint establishes a solid functional knowledge base of what each component does; the Support blueprint builds on that by teaching what happens when components fail or deviate from expected behavior; finally, the Architect exam challenges you to synthesize operational insight and failure‑mode understanding into forward‑looking design choices. If you already hold one or more pillar VCAPs, beginning with Administrator will feel the most comfortable, as its objectives overlap heavily with the configuration material you have likely already studied, letting you leverage existing preparation while adjusting to the broader, cross‑pillar perspective.
As you prepare, treat the exam guides as living documents; although they are dated 18 August 2026, minor revisions may appear as Broadcom catches errata (such as the footnote reference to “VVF” in the Architect guide). Always cross‑check the latest version on the Broadcom certification portal and read the VCF 9 release notes, which are explicitly in scope. Combine official coursework with hands‑on labs—particularly for the Automation and VKS sections—and use the TechDocs portal for deep dives on vSphere, vSAN, and NSX topics. Finally, schedule your exams with ample time for review, practice the varied item types through sample questions, and approach each test with the confidence that your preparation maps directly to real‑world VCF 9 responsibilities.