VCP-VCF 9.0 Administrator (2V0-17.25)
The foundational administrator certification for VMware Cloud Foundation 9.0. Validates hands-on operational knowledge of VCF components: ESX 9.0, vCenter 9.0, vSAN 9.0 (OSA/ESA, ESA default), NSX 9.0, VCF Operations 9.0 and VCF Automation 9.0 (with SDDC Manager UI deprecated), lifecycle management, certificate rotation, password management, and backup/DR. 60 questions, 135 minutes, passing score 300 (scaled score; Broadcom publishes no percentage). This section covers the complete VCF 9.0 admin stack from Day-0 bring-up through Day-2 operations, with emphasis on the architectural shift from VCF 5.2 (Cloud Builder + SDDC Manager) to VCF 9.0 (VCF Installer + VCF Operations with fleet management + VCF Automation).
Exam Blueprint Weights
Version Evolution
VCF 5.2: Cloud Builder bootstraps SDDC Manager → domain-centric management. VCF 9.0: VCF Installer deploys the management domain together with VCF Operations (and optionally VCF Automation) → private cloud / fleet / instance / domain hierarchy.
Key admin changes: SDDC Manager UI deprecated with its workflows surfaced in the VCF Operations console (the SDDC Manager appliance and API remain in every instance), separate Cloud Builder appliance eliminated (the Installer becomes SDDC Manager), vCenter is protected by vSphere HA in both releases (vCenter HA is not supported in VCF, Table 670), NSX upgraded from 4.x (VCF 5.2) to NSX 9.0, vSAN 9.0 ships ESA as the default alongside OSA (VCF 5.2 shipped vSAN 8.x), and the VCF Operations fleet management appliance brings cross-instance lifecycle, certificate and password management.
Certificate management consolidated into VCF Operations (Fleet Management > Certificates). Password management moved to VCF Operations (Fleet Management > Passwords); SDDC Manager 5.2 already offered scheduled rotation, and in 9.0.x rotation still runs through the SDDC Manager UI/API (known issue).
Learning Outcomes
- Obj 2.1: Describe Private Cloud vision and architecture — Instance, Fleet, Private Cloud hierarchy
- Obj 2.2: Deploy/configure VCF compute — host commissioning, vSphere clusters, VMs, DRS/HA, Content Libraries, encryption
- Obj 2.3: Configure vSphere storage — vSAN ESA vs OSA, storage policies, resilience, fault domains, stretched clusters
- Obj 2.4: Differentiate VCF networking — NSX Tier-0/Tier-1, segments, DFW, TEPs, BGP/OSPF routing, networking services
- Obj 4.1: Deploy & Configure VCF — VCF Installer, bring-up workflow, management domain, VCF Operations deployment
- Obj 4.2: Manage VCF — Fleet management, identity/RBAC, license management, certificate rotation, password management
- Obj 4.3: Operate VCF — VCF Operations + Operations for Logs, dashboards, alerts, compliance, costing, Service Discovery, vSAN Storage Ops
- Obj 4.4: Consume & Automate — VCF Automation (Cloud Assembly, Service Broker, Orchestrator), regions, multi-tenancy, provider networking, cloud templates
VCP-VCF 9.0 Administrator (2V0-17.25)#
Exam Badge: 2V0-17.25
60 questions, 135 minutes, passing score 300 (scaled score; Broadcom publishes no percentage), proctored.
This is the foundational administrator certification for VMware Cloud Foundation 9.0. It validates hands-on operational knowledge of VCF components (vSphere, vSAN, NSX, lifecycle management, security, backup/DR). Unlike the VCDX (design-focused), this exam tests implementation and day-to-day administration of VCF 9.0 environments. Success requires deep understanding of each component's architecture, integration points, and common operational tasks.
Official documentation for this exam (VCF 9.0, vSphere 9.0, vSAN 9.0, NSX in VCF 9.0, vSphere Replication 9.0, VMware Live Site Recovery 9.0) and the Broadcom VCP-VCF Administrator certification page are linked under References at the foot of this page.
VCF 9.0 Architecture & Components
VCF 9.0 fundamentally restructures the management plane. VCF 9.0 introduces VCF Operations as the primary management interface. Cloud Builder is removed (replaced by VCF Installer for initial deployment). SDDC Manager still exists but its UI is deprecated — lifecycle management and Day-2 operations are now performed through VCF Operations and vSphere Client. SDDC Manager UI will be removed in a future major release. The hierarchy introduces new concepts above the domain level: a VCF Private Cloud is the highest-level construct encompassing one or more Fleets, each Fleet contains one or more Instances, and each Instance contains domains (management + workload). VCF Operations becomes the mandatory management appliance, with SDDC Manager UI deprecated.
VCF 9.0 Hierarchy (VCF 9.0.1 documentation, Constructs of a VCF Private Cloud)
VCF private cloud
one or more VCF fleets
VCF fleet
one set of fleet-level components: VCF Operations (with the fleet management appliance) and VCF Automation,
hosted in the management domain of the fleet's first VCF Instance
one or more VCF Instances, plus optional standalone vCenter instances managed by that VCF Operations
VCF Instance
SDDC Manager, NSX, vCenter, ESX
one management domain plus optional workload domains
VCF domain
one vCenter instance; one or more vSphere clusters (HA and DRS on); a vDS per cluster and NSX segments;
a dedicated or shared NSX Manager cluster; optional NSX Edge clusters; principal and supplemental storage
Key Architectural Changes from VCF 5.2 to 9.0:
- Cloud Builder replaced by the VCF Installer for deployment and convergence; the VCF Installer also deploys VCF Operations, VCF Automation and the fleet components that SDDC Manager and the Aria Suite Lifecycle flow handled in 5.2
- SDDC Manager stays in every VCF Instance; its UI is deprecated (to be removed in a future major release) and its workflows run from VCF Operations (fleet management) and the vSphere Client
- Hierarchy above the domain: VCF private cloud, then VCF fleet, then VCF Instance, then VCF domains (management and workload)
- Each VCF domain keeps its own vCenter; workload-domain vCenters are deployed into the management domain; NSX Manager clusters are per domain or shared between workload domains, never shared with the management domain
- NSX 4.2 (5.2) becomes NSX 9.0; vSAN 8.0 U3 becomes vSAN 9.0 with OSA or ESA chosen per cluster
- Fleet-wide identity through VCF SSO with the VCF Identity Broker (an embedded service on the management domain vCenter, or a three-node appliance cluster)
Instance vs Fleet vs Private Cloud Explained
- VCF private cloud: The highest level of management and consumption for the software-defined data center resources. A VCF private cloud can contain one or more VCF fleets.
- VCF fleet: An environment managed by a single set of fleet-level management components, VCF Operations and VCF Automation. A fleet contains one or more VCF Instances and may contain standalone vCenter instances managed by the fleet's VCF Operations. The management domain of the first VCF Instance hosts the fleet-level components.
- VCF Instance: The compute, storage and networking virtual infrastructure that runs business workloads: SDDC Manager, NSX, vCenter and ESX. An Instance consists of VCF domains, a management domain and, optionally, workload domains. In a converged environment the management components may also sit in clusters of the workload domains.
- Management domain and workload domains (current terminology, not legacy): The management domain is created by the VCF Installer during deployment or convergence. It carries the Instance's management components, the SDDC Manager appliance and the fleet management appliance, and, for the first Instance in the fleet, VCF Operations and VCF Automation. Workload domains are created in VCF Operations to run consumer workloads; VCF Operations deploys each workload domain's vCenter (and a new or shared NSX Manager cluster) into the management domain. Workload domains cannot use the management domain's NSX Manager cluster.
vSphere Administration
vSphere 9.0 (ESX 9.0 and vCenter 9.0) is the foundation of VCF 9.0. Mastering ESXi host management, vCenter cluster operations, VM lifecycle, and HA/DRS is non-negotiable for VCDX-level administration.
ESX 9.0 Host Management
Key capabilities in ESX 9.0 (the hypervisor is branded ESX in 9.x):
- Secure Boot & vTPM: ESXi 8.0+ supports Secure Boot (prevents rootkits at firmware level) and virtual TPM (vTPM) for VM encryption keys. Enterprise deployments require these.
- Memory Encryption: AMD SEV (Secure Encrypted Virtualization) and Intel TME (Total Memory Encryption) at host level. Can be enabled per-VM for sensitive workloads.
- Driver Support & HWA: Hardware acceleration for NVMe, storage controllers, and network adapters. Critical for performance tuning.
- Kernel Module Acceptance Level: Can restrict (partner/vmware-approved) or allow (any driver). Set via Host Profile or ESXi settings. VCDX exams test this.
vCenter 9.0 Operations
vCenter Server Availability: vSphere provides vCenter HA as an Active-Passive-Witness architecture (NOT active-active). The Active node handles all operations, continuously replicating data to a Passive node. A lightweight Witness node (1 vCPU, 1GB RAM) provides quorum. If the Active node fails, the Passive node is promoted automatically. All three nodes communicate over a dedicated vCenter HA private network.
vCenter HA Architecture:
┌─────────────────────────────────────┐ │ vCenter HA (Active-Passive-Witness) │ │ ┌─────────────┐ │ │ │ vCenter-01 │ (Active) │ │ │ Public IP │ Handles all ops │ │ ├─────────────┤ │ │ │ vCenter-02 │ (Passive) │ │ │ No public IP│ Receives replicas │ │ ├─────────────┤ │ │ │ vCenter-03 │ (Witness) │ │ │ 1vCPU/1GB │ Quorum only │ │ └─────────────┘ │ │ • Continuous replication Active→ │ │ Passive over HA private network │ │ • Automatic failover if Active │ │ node fails │ └─────────────────────────────────────┘
IMPORTANT VCF Restriction: vCenter HA CANNOT be configured for a vCenter Server that is managed by VCF (per Broadcom documentation). In VCF environments, vCenter availability is achieved through vSphere HA (which restarts the vCenter VM on another host if the ESXi host fails) and regular SDDC Manager/VCF Operations backups for recovery. This is a critical exam distinction — do not confuse vCenter HA (standalone vSphere feature) with vCenter protection in VCF (vSphere HA + backup/restore).
VM Lifecycle & Resource Management
DRS (Distributed Resource Scheduler)
DRS balances VM placement across hosts to optimize CPU/memory utilization. DRS algorithms in vSphere 9.0:
- Affinity Rules: VMs should/must run on same host or separate hosts. Critical for HA VMs (e.g., don't co-locate all DB nodes on one host).
- VM/Host Groups: Assign VMs and hosts to groups, then apply rules. Example: "Finance VMs run on Finance Hosts."
Cluster Configuration:
# Enable DRS on a cluster (PowerCLI); in VCF the Installer and VCF Operations set HA and DRS on every cluster they create — use this only to inspect or correct the automation level
Get-Cluster "management-domain" | Set-Cluster -DrsEnabled:$true -DrsAutomationLevel "FullyAutomated" -Confirm:$false
# Check what the platform configured
Get-Cluster "management-domain" | Select Name, DrsEnabled, DrsAutomationLevel, HAEnabled, HAAdmissionControlEnabledExam note: VCF requires vSphere HA and vSphere DRS to be enabled on every cluster in a VCF domain; disabling either breaks the platform's assumptions for lifecycle operations and host maintenance.
Key Takeaways
- VCDX Test Focus: Expect deep questions on DRS automation levels, HA admission control calculation, FT limitations, and vMotion compatibility. Practice calculating failover capacity: (total_resources) - (largest_host) = failover_budget.
- Exam Emphasis: Expect 8-10 questions on vSAN. Know how to calculate usable capacity from raw disks + RAID + replication. Understand FTT vs host failure tolerance. Know when to use OSA vs ESA. Stretched cluster is common in disaster recovery scenarios—understand quorum math.
- NSX Exam Topics: Expect questions on Tier-0/Tier-1 hierarchy, segment creation, DFW microsegmentation rules, Geneve encapsulation, and BGP/OSPF peering. Practice creating a multi-tier network (app, db, storage segments) with DFW policies that enforce east-west isolation.
- LCM is heavily tested on the exam. Understand pre-check/remediation flow, bundle dependencies, certificate rotation, drift detection, and upgrade paths. Practice reading LCM logs to troubleshoot failed patches. Know the impact of each step: vCenter (Reduced Downtime Upgrade) and NSX Manager updates interrupt management access rather than running workloads (during the NSX management-plane upgrade the UI is unavailable for a short period, and when upgrading from VCF 9.x API downtime is negligible, VCF 9.0.1 docs p.1390), while ESX hosts are remediated in maintenance mode with DRS evacuating their VMs and a vSAN data-migration option per host, one after another or several at once when parallel remediation is enabled (VCF 9.0.1 docs p.453, p.1406, p.1729).
- Backup & DR Design: VCDX exams test your ability to design a complete backup strategy. Example: "Design a DR plan for VCF with 4-hour RTO and 1-hour RPO." Answer: vSphere Replication (5 min RPO VM level) + SRM (orchestration) + VADP hourly backups (granular restore) + VCF component daily backup.
VCF 9.0 Day-1 Bring-up Flow End-to-End#
Deploying VCF 9.0 is fundamentally different from VCF 5.2. The workflow has shifted from Cloud Builder → SDDC Manager to VCF Installer → VCF Operations (fleet management), with a revised governance model emphasizing Fleet management and Private Clouds. Understanding each step and its validation gates is essential for VCP-Admin certification and beyond.
Pre-Flight Prerequisites & Validation
Before launching VCF Installer, validate the physical infrastructure:
Infrastructure Checklist:
├─ Hardware: │ ├─ CPU: minimum 16 cores per ESXi host (32+ recommended for VCF 9.0) │ ├─ RAM: 256 GB per host minimum (512 GB+ if vSAN + workloads on same cluster) │ ├─ NVMe: 2x 1.6 TB (management domain) + 4x 3.84 TB (workload domain) │ └─ NIC: minimum 10 GbE (25 GbE+ recommended for vSAN replication) ├─ Networking: │ ├─ Management network: 192.168.1.0/24 (for vCenter, NSX, SDDC → VCF Ops IPs) │ ├─ vSAN network: 192.168.2.0/24 (dedicated for vSAN replication, isolated vLAN) │ ├─ Workload network: 192.168.3.0/24 (overlay or external) │ ├─ Static IPs reserved: 192.168.1.10-30 (management domain components) │ └─ DNS/NTP: external servers configured, synchronization verified ├─ Software: │ ├─ ESX 9.0 (the build named in the VCF 9.0.x release notes BOM) installed on all hosts │ ├─ VCF Installer OVA staged (download from Broadcom Support Portal) │ └─ VCF 9.0.x binaries downloaded to the VCF Installer depot (online depot or offline via the VCF Download Tool) └─ Validation: ├─ NTP: all ESXi hosts ± 1 second of true time ├─ Networking: ping between all ESXi hosts on all vLANs └─ Storage: all NVMe devices visible via vCenter datastore browser
Step 1: VCF Installer OVA Deployment
Deployment Method:
Deploy the VCF Installer OVA to one of the ESXi hosts (typically the first host, which will host SDDC Manager in VCF 5.2 or become the management domain in VCF 9.0).
VCF Installer Appliance Sizing (VCF 9.0.1, Deploy the VCF Installer Appliance):
├─ vCPU: 4 ├─ Memory: 16 GB ├─ Disk: 914 GB (thin-provisioned) ├─ Network: 1 vNIC (management network, e.g., 192.168.1.5), static IP and FQDN registered in DNS └─ Deployment location: a management-domain ESX host (host-01) or an existing vCenter. Deployed on a management-domain host, the appliance is not ephemeral: after the management domain storage is configured it is Storage-vMotioned to that storage and switched to SDDC Manager mode (its local disk is not added to management storage)
Post-Deployment Configuration:
- Power on VCF Installer VM
- Wait for boot (3–5 minutes)
- Access via SSH or Web UI: https://vcf-installer-ip:443/ui
- Authenticate: admin@local with the password set at OVA deployment
- Navigate to: Deployment Wizard → VMware Cloud Foundation → choose "A new VCF fleet" or "A VCF Instance in an existing VCF fleet"
Step 2: Management Domain Bring-up (Foundation Tier)
The management domain is the foundational tier in VCF 9.0. It contains:
- vCenter Server: Single VCSA protected by vSphere HA (vCenter HA not supported in VCF)
- NSX Manager Cluster: 3-node cluster behind a cluster VIP
- SDDC Manager: The VCF Installer appliance switched to SDDC Manager mode after bring-up
- VCF Operations (first instance in a fleet): VCF Operations appliance(s) plus the VCF Operations fleet management appliance, which adds the Fleet Management workflows; VCF Operations collectors and the logs/networks components as deployed
- VCF Automation (optional at bring-up): Can be skipped and deployed as a Day-N operation from Fleet Management > Lifecycle
- vSAN Datastore: Sized from the Planning and Preparation Workbook for all management appliances (ESA: 4 hosts recommended for the high-availability deployment model)
VCF Installer bring-up workflow (automated):
Step 2A: Configure Management Domain Network Pools
├─ Specify IP ranges for management components: │ ├─ vCenter: 192.168.1.10 (single appliance protected by vSphere HA — VCF does not support vCenter HA, Table 670) │ ├─ NSX Manager IPs: 192.168.1.20, 192.168.1.21, 192.168.1.22 (one per manager) + cluster VIP │ ├─ SDDC Manager: 192.168.1.30 (the VCF Installer appliance switches to SDDC Manager mode after bring-up) │ ├─ VCF Operations: 192.168.1.32 and the VCF Operations fleet management appliance: 192.168.1.33 (new in VCF 9.0) │ ├─ VCF Automation: 192.168.1.34 (optional at bring-up; can be a Day-N deployment) │ └─ ESX management IPs: 192.168.1.50-60 (vmk0 for each host) └─ Validation: the VCF Installer pre-checks verify DNS forward/reverse records, NTP and that no IP conflicts exist with the physical network gateway
Step 2B: Deploy vCenter Server
├─ VCF Installer deploys a single vCenter Server Appliance (VCSA) ├─ vCenter is protected by vSphere HA (VM restart on host failure) ├─ Note: vCenter HA (active-passive-witness) is NOT supported in VCF └─ Validation: vCenter boots, DNS resolves vcenter.vcf.local to management IP
Step 2C: Deploy NSX Manager Cluster
├─ 3 NSX Manager appliances deployed (spread across 3 ESXi hosts) ├─ NSX Manager is a 3-node cluster behind a cluster VIP; the control plane (CCP) runs inside the manager appliances — there are no separate controller appliances since NSX-T 2.4 ├─ Host transport nodes are prepared for NSX during bring-up; Edge clusters are a Day-N addition └─ Validation: NSX Manager API responding on the cluster VIP (:443); cluster status STABLE
Step 2D: Configure vSAN for Management Domain
├─ vSAN cluster is formed by the Installer (4 hosts for the high-availability deployment model; 3 for a simple deployment; a standard vSAN cluster needs at least 3) ├─ vSAN ESA (9.0 default): single-tier storage pool of NVMe devices per host, no disk groups; vSAN OSA only: disk groups of 1 cache + 1–7 capacity devices ├─ Datastore named "vsanDatastore" (default) ├─ Default storage policy FTT=1 (ESA auto-policy picks RAID-1 or RAID-5 by host count; OSA RAID-1) └─ Validation: vCenter reports vSAN health as GREEN, all hosts contributing storage
Step 2E: Deploy VCF Operations with fleet management (NEW in VCF 9.0)
├─ Single appliance (16 vCPU, 64 GB RAM) deployed as nested VM ├─ VCF Ops connects to vCenter, NSX Manager, and cluster ├─ Collectors (optional) can be deployed separately for scale └─ Validation: VCF Ops UI is accessible at https://vcf-ops.vcf.local:443
Step 2F: Bootstrap Identity Services (NEW in VCF 9.0)
├─ Local user database initialized (administrator@vcf.local) ├─ Optional: LDAP/AD integration configured ├─ OAuth 2.0 enabled for API clients └─ Validation: Can log into VCF Ops with administrative credentials
Management Domain Bring-up Time: 60–90 minutes (depends on hardware + network)
Post-Bring-up Validation Gates:
├─ DNS resolution of all FQDNs (vcenter.vcf.local, nsxmgr.vcf.local, etc.) ├─ SSL certificates auto-generated and valid (VMCA-signed for vCenter and ESX; VCF Operations certificates visible under Fleet Management > Certificates for later replacement with CA-signed certificates) ├─ SDDC Manager mode active on the former Installer appliance; inventory shows the management domain, its cluster and hosts ├─ VCF Operations shows the VCF Instance under Fleet Management > Lifecycle with all components at the deployed version ├─ vSAN health GREEN, vSphere HA and DRS enabled on the management cluster, NSX Manager cluster STABLE └─ Backups configured: SDDC Manager/vCenter/NSX file-based backup target registered before the first workload domain is created
Holodeck note: in Holodeck 9.0.x the whole sequence above runs unattended from the VCF Installer deployment wizard inside the nested site; the Post Deployment table on the HoloRouter records the FQDNs and the documented default credentials to use for the validation gates.
Key Takeaways
- VCP-Admin Test Tip: Understand the difference between VCF 5.2 (Cloud Builder → SDDC Manager) and VCF 9.0 (VCF Installer → VCF Operations) bring-up flows. Exam questions will ask: "Which component replaces Cloud Builder in VCF 9.0?" Answer: the VCF Installer. SDDC Manager remains in the management domain of every VCF Instance; only the SDDC Manager UI is deprecated, with the Day-2 workflows (lifecycle, certificates, passwords) surfaced in VCF Operations.
Understanding the VCF Fleet Concept Deeply#
The VCF fleet is one of the significant architectural changes in VCF 9.0: one set of fleet-level management components governs several VCF Instances. It is an administrator-level concept that every VCDX-level design must place correctly.
The VCF 9.0 construct hierarchy (VCF 9.0 Administration, Table 1 "Constructs of a VCF Private Cloud" and Table 2 "Types of VCF Domains")
| Construct | What it is | Components |
|---|---|---|
| VCF private cloud | The highest level of management and consumption for the software-defined data centre resources | One or more VCF fleets |
| VCF fleet | An environment managed by a single set of fleet-level management components. Contains one or more VCF Instances and may contain standalone vCenter instances managed by the same VCF Operations | VCF Operations, VCF Automation, one or more VCF Instances, optional standalone vCenter instances |
| VCF Instance | The compute, storage and networking virtual infrastructure that runs business workloads: a management domain plus optional workload domains | SDDC Manager, NSX, vCenter, ESX |
| VCF domain | One vCenter, one or more vSphere clusters (HA and DRS enabled), a vSphere Distributed Switch per cluster, a dedicated or shared NSX Manager instance, optional NSX Edge clusters, principal and supplemental storage | Management domain or workload domain |
Where the fleet-level components live
The management domain of the first VCF Instance in the fleet hosts the fleet-level components: VCF Operations (with the VCF Operations fleet management appliance, which adds the infrastructure-management workflows — Lifecycle, Certificates, Passwords, Identity & Access — to the VCF Operations console) and VCF Automation. Each management domain also holds the instance's own SDDC Manager appliance, vCenter and NSX Manager cluster. There is no separate "Fleet Manager" product or appliance to size, cluster or fail over; the VCF Operations fleet management appliance is deployed by the VCF Installer and lifecycled from Fleet Management > Lifecycle like the other VCF Operations components.
Fleet hierarchy as deployed:
VCF private cloud
└─ VCF fleet (one VCF Operations instance + VCF Automation) ├─ VCF Instance 1 (first instance; its management domain hosts VCF Operations, the fleet management appliance and VCF Automation) │ ├─ Management domain: SDDC Manager, vCenter, NSX Manager cluster, ESX cluster(s) │ └─ Workload domains: one vCenter each, NSX Manager cluster (own or shared with another workload domain; never the management domain's), clusters, edge clusters ├─ VCF Instance 2 (joined to the existing VCF Operations at deployment: "A VCF Instance in an existing VCF fleet") │ ├─ Management domain: SDDC Manager, vCenter, NSX Manager cluster │ └─ Workload domains └─ Standalone vCenter instances (optional; managed by the fleet's VCF Operations without SDDC Manager)
How a fleet grows (VCF Installer deployment wizard)
- First VCF Instance: the VCF Installer deployment wizard offers "A new VCF fleet" — it deploys VCF Operations (or connects to an existing one) together with the management domain, and can skip VCF Automation for a Day-N deployment later.
- Additional instance: choose "A VCF Instance in an existing VCF fleet" and select the existing VCF Operations instance; a new instance in an existing fleet must connect to that VCF Operations.
- Workload domains are created in VCF Operations. For the first workload domain, VCF Operations deploys a vCenter and an NSX Manager instance into the management domain; each further workload domain gets another vCenter and either shares an existing workload NSX Manager cluster or receives a new one.
- Brownfield: the VCF Installer converges an existing vSphere environment into a new VCF Instance, and VCF Operations imports an existing vCenter as a workload domain (in VCF 9.0 this replaces the 5.x VCF Import Tool, vcf_brownfield.py); in a converged environment the management components may sit in workload-domain clusters rather than the first management cluster.
Fleet-level operations in VCF Operations (the menu names an administrator will be examined on)
| Menu | What it does at fleet scope |
|---|---|
| Fleet Management > Lifecycle | Component inventory and upgrades for VCF Operations components, VCF Automation and each VCF Instance (clusters are updated per instance with vSphere Lifecycle Manager images) |
| Fleet Management > Certificates | Certificate inventory and replacement per VCF Instance and component |
| Fleet Management > Passwords | View, update and remediate managed credentials across the instances (see the Objective 4.2 block for the 9.0.x rotation known issue) |
| Fleet Management > Identity & Access | VCF Single Sign-On, Active Directory and identity-provider configuration for the fleet |
| Inventory and dashboards | Cross-instance capacity, health, compliance and cost views; standalone vCenter instances appear alongside VCF Instances |
Instance vs fleet vs private cloud — terminology that is tested
| Term | Scope | Count | Example |
|---|---|---|---|
| VCF private cloud | Everything the organisation runs on VCF | One or more fleets | "Group private cloud" spanning two regions |
| VCF fleet | One VCF Operations + VCF Automation pair and what they manage | One or more VCF Instances plus optional standalone vCenters | Fleet "EMEA" managed from the Frankfurt management domain |
| VCF Instance | A management domain and its workload domains, with its own SDDC Manager | Several per fleet, typically one per data centre | "DC-A", "DC-B" |
| Management domain | The first domain of an instance: SDDC Manager, vCenter, NSX; plus the fleet components for the first instance | One per instance | — |
| Workload domain | Consumer workloads under their own vCenter | Zero or more per instance | "Prod-Finance", "Dev" |
Example: enterprise with two data centres
VCF fleet "Group-EMEA" (VCF Operations and VCF Automation in the DC-A management domain)
├─ VCF Instance "DC-A" │ ├─ Management domain (SDDC Manager, vCenter, NSX; hosts VCF Operations, fleet management appliance, VCF Automation) │ ├─ Workload domain "Prod-Finance" (own vCenter and NSX Manager cluster) │ └─ Workload domain "Prod-Engineering" (own vCenter; shares Prod-Finance's NSX Manager cluster) ├─ VCF Instance "DC-B" (deployed as an instance in the existing fleet) │ ├─ Management domain (SDDC Manager, vCenter, NSX) │ └─ Workload domain "DR-Finance" (recovery target for Prod-Finance via VMware Live Site Recovery) └─ Standalone vCenter "Legacy-Lab" (managed by VCF Operations, not yet converged)
Design implications for a VCDX candidate
- The first instance's management domain is the fleet's single point of management: its availability design (vSphere HA for the management VMs, file-based backups of VCF Operations, SDDC Manager, vCenter and NSX) protects every instance's Day-2 operations, even though workloads in the other instances keep running if it is down.
- A fleet gives one console and one identity configuration; it does not stretch an instance's storage or networking across sites — DR between instances still needs replication and recovery tooling (vSphere Replication, VMware Live Site Recovery, NSX Federation where used).
- Decide per workload domain whether to share an NSX Manager cluster (fewer appliances, one policy scope) or dedicate one (fault isolation, independent upgrades); the management domain's NSX Manager cluster is never an option for workload domains.
- Standalone vCenters in the fleet get VCF Operations visibility and lifecycle, but the SDDC Manager-driven workflows (host commissioning, domain creation) require convergence into a VCF Instance.
Holodeck lab note: a single Holodeck site is one VCF Instance in a one-instance fleet; the VCF Operations console there is the same Fleet Management console you would use for many instances, which makes it the right place to practise the menu paths above.
Key Takeaways
- Exam: a VCF fleet = one VCF Operations + VCF Automation pair managing one or more VCF Instances (and optionally standalone vCenters); the fleet-level components run in the management domain of the first instance (VCF 9.0 Table 1 and Table 2).
- There is no separate Fleet Manager appliance to size or cluster: the VCF Operations fleet management appliance adds the Fleet Management workflows (Lifecycle, Certificates, Passwords, Identity & Access) to VCF Operations and is deployed and lifecycled by the platform.
- VCDX design consideration: in a multi-instance design, protect the first instance's management domain as the fleet's management single point of failure, and keep DR between instances as an explicit replication/recovery design — the fleet is a management scope, not a stretched infrastructure.
- VCDX identity design consideration: multi-tenant VCF needs VCF Single Sign-On federated to the corporate identity provider (Fleet Management > Identity & Access) with group-to-role mapping per instance and workload domain; SDDC Manager and ESX stay outside VCF SSO and need their own credential handling.
VCF Compute, Storage & Network Fundamentals (Objectives 2.2–2.4)#
Blueprint Objectives 2.2, 2.3, 2.4 — VCF Fundamentals
This topic covers VCF-specific aspects of compute, storage, and networking that differentiate VCF Admin from VVF Admin. Core vSphere/vSAN/networking concepts are covered in the main theory topic; this topic focuses on how these components integrate within the VCF stack.
VCF Compute Fundamentals (Objective 2.2)
Deploy/Configure VCF Compute:
VCF compute deployment differs from standalone vSphere — all ESX hosts are commissioned into the VCF free pool — in VCF 9.0 from the vSphere Client (management-domain vCenter, or any linked vCenter with VCF SSO) or alternatively from the SDDC Manager UI — never added manually to a cluster.
Host Commissioning Workflow:
├── Physical host prepared (BIOS, firmware, networking) ├── ESXi installed with VCF-compatible image (from VCF bundle) ├── Host commissioned into the free pool: vSphere Client → Global Inventory Lists → Hosts → Unassigned Hosts → Commission Hosts (FQDN, credentials, storage type, network pool); JSON template for bulk; SDDC Manager UI as the alternative ├── Platform validates: DNS forward/reverse, NTP, network pool connectivity, storage type (vSAN ESA hosts can only join ESA clusters, OSA to OSA, NFS/FC/vVols likewise); SSH is enabled briefly to collect the host key, then disabled ├── Host assigned when a workload domain or cluster is created or expanded in VCF Operations (or the management domain is expanded) └── Platform configures automatically: vDS and uplinks, vSAN membership (ESA storage pool or OSA disk groups), NSX transport node preparation with the TEP pool
vSphere Cluster Configuration in VCF:
├── Clusters created via VCF Operations (not directly in vCenter) ├── DRS: enabled; Fully Automated with medium threshold is the design recommendation (VCF-CLS-RCMD-CFG-003, VCF 9.0.1 docs p.550); Supervisor clusters require Fully or Partially Automated (p.540) ├── HA: Enabled with admission control (percentage-based, 25% default) ├── EVC (Enhanced vMotion Compatibility): Recommended for mixed-CPU clusters ├── vLCM: Image-based lifecycle (VCF bundle includes ESXi + VIB + firmware) └── Minimum hosts depend on storage type and deployment model (VCF 9.0.1 docs p.1267): a standard vSAN cluster needs at least 3 hosts (p.1663); the high-availability model with vSAN OSA at FTT=1 needs 4 (p.268) — size with the Planning and Preparation Workbook
Deploy/Configure VMs in VCF:
├── Standard VM deployment via vCenter (same as standalone vSphere) ├── Content Libraries: Federated across VCF instance (publish/subscribe) ├── VM Templates: OVF/OVA deployed via vCenter or VCF Automation (if licensed) ├── VM Encryption: vTPM + VM encryption policies backed by KMS (HyTrust, Thales) ├── VM Storage Policies: Tied to vSAN storage policies (FTT, encryption, RAID level) └── GPU Passthrough: vGPU (NVIDIA GRID) or DirectPath I/O for AI/VDI workloads
Manage VMs through vCenter:
├── Day-2 VM operations: snapshot, clone, migrate (vMotion), hot-add CPU/memory ├── vSphere DRS automation: VM placement recommendations, load balancing ├── Resource Pools: Hierarchical resource allocation (shares, limits, reservations) ├── VM Groups & Host Groups: Affinity/anti-affinity rules for workload placement ├── Distributed Resource Scheduling (DRS) Levels: │ ├── Manual: Recommendations only (admin must approve) │ ├── Partially Automated: Initial placement automatic, migrations recommended │ ├── Fully Automated: All placement and migrations automatic (VCF default) │ └── Migration Threshold: Conservative (1) to Aggressive (5) — affects sensitivity └── Tags & Custom Attributes: Organizational metadata for filtering and policy
VCF Storage Fundamentals (Objective 2.3)
vSphere Storage in VCF:
├── VMFS on Fibre Channel: principal or supplemental storage ├── NFS: NFS v3 as principal; NFS v3 and v4.1 as supplemental ├── iSCSI, NVMe/TCP, NVMe/FC, NVMe/RDMA: supplemental only (VCF 9.0.1 docs p.502, Table 23) ├── vVols: deprecated starting with VCF 9.0, bug-fix support only (VCF 9.0.1 docs p.229) ├── vSAN (ESA or OSA): Default HCI principal storage for VCF (most common) └── vSAN storage cluster (formerly vSAN Max): disaggregated vSAN — compute and storage on separate clusters; not supported for the default management cluster (VCF 9.0.1 docs p.502, p.1498)
vSAN ESA vs OSA:
├── OSA (Original Storage Architecture):
│ ├── Separate cache tier (SSD) + capacity tier (HDD or SSD)
│ ├── Disk groups: 1 cache device + 1-7 capacity devices per group
│ ├── Up to 5 disk groups per host
│ ├── Dedup/compression: Optional, post-process
│ └── Use case: Existing hardware with mixed SSD/HDD
├── ESA (Express Storage Architecture):
│ ├── Single storage tier (NVMe only — no cache tier distinction)
│ ├── Storage pool: All NVMe devices contribute to single pool
│ ├── Space efficiency: compression enabled by default through the storage policy; deduplication is not available on a vSAN ESA cluster (VCF 9.0.1 vSAN docs)
│ ├── RAID-5/6 erasure coding with single object stripe
│ ├── Higher performance: Single tier eliminates cache destaging bottleneck
│ └── Use case: New deployments with NVMe-only storage (recommended for VCF 9.0)
└── Decision Framework:
├── Choose ESA if: All NVMe, new deployment, VCF 9.0
├── Choose OSA if: Mixed media (SSD + HDD), existing hardware, budget constraints
└── Migration: OSA → ESA requires vSAN cluster rebuild (no in-place migration)vSAN Storage Policies:
├── FTT (Failures to Tolerate): 0, 1, 2, 3 ├── RAID Level: RAID-1 (mirroring) or RAID-5/6 (erasure coding) ├── Encryption: Data-at-rest (KMS required), data-in-transit (TLS between hosts) ├── Object Space Reservation: Thick provisioning (0-100%) ├── IOPS Limit: Per-object QoS throttling ├── Checksum: Data integrity verification (enabled by default) └── Stripe Width: Number of capacity devices used (performance tuning)
vSAN Resilience & Data Availability:
├── Component placement: Automatic across fault domains ├── Fault Domains: Group hosts by rack/power/network for failure isolation ├── Witness: Required for 2-node clusters (witness appliance on third failure domain) ├── Stretched Cluster: Synchronous replication across 2 sites + witness (RPO=0) ├── vSAN Data Migration: Ensure accessibility/full evacuation/no data migration (host maintenance) └── Rebuild Priority: Automatic after failure, configurable delay timer (60 min default)
VCF Network Fundamentals (Objective 2.4)
Differentiate VCF Networking Components:
VCF uses NSX for overlay networking — unlike VVF which uses vDS only. Understanding the NSX integration is critical.
NSX in VCF — Architecture:
├── NSX Manager Cluster: 3-node cluster (management plane) ├── NSX Edge Cluster: 2+ Edge nodes (data plane — north-south routing) ├── Transport Zones: │ ├── Overlay TZ: Geneve encapsulation for east-west VM traffic │ └── VLAN TZ: Physical network connectivity (uplinks to ToR switches) ├── Transport Nodes: ESXi hosts with NSX VIBs installed (N-VDS or vDS-backed) └── Segments: Logical network switches (replace port groups in NSX world)
NSX Networking Constructs:
├── Tier-0 Gateway: North-south routing (connects to physical network via BGP/OSPF/static)
│ ├── HA Mode: Active-Active or Active-Standby
│ ├── Route Redistribution: Connected, static, NAT, LB VIPs
│ └── Uplink: Connected to VLAN-backed segment on Edge node
├── Tier-1 Gateway: Tenant/workload routing (connects to Tier-0 for external access)
│ ├── Per-workload domain or per-tenant isolation
│ ├── Services: NAT, firewall, load balancing, DHCP, DNS forwarding
│ └── Route Advertisement: Connected subnets, NAT IPs, LB VIPs → Tier-0
├── Segments: Layer 2 broadcast domains (equivalent to VLANs/port groups)
│ ├── Overlay Segment: Geneve-encapsulated (TEP-to-TEP tunneling)
│ ├── VLAN Segment: Direct VLAN tagging (for physical device connectivity)
│ └── Subnet: IP range + gateway assigned per segment
└── Distributed Firewall (DFW): Microsegmentation at hypervisor level
├── Rules applied per-VM (based on tags, segments, groups, IPs)
├── Stateful inspection: East-west traffic filtered without hairpinning
├── Policy Categories: Emergency > Infrastructure > Environment > Application
└── Applied to: All VMs on NSX-prepared hosts (no agent required)Configure Virtual Networking Fabrics/Features:
├── N-VDS: NSX-managed virtual switch (deprecated in NSX 4.x — use vDS integration) ├── vDS Integration: NSX 4.x integrates with vSphere Distributed Switch ├── TEP (Tunnel Endpoint): IP on each host for Geneve encapsulation │ ├── TEP VLAN: Dedicated VLAN for overlay traffic (jumbo frames recommended) │ └── TEP Pool: IP range assigned via VCF Operations during host commissioning ├── MTU: 1600 is the minimum required for Geneve overlay; 1700 or higher is recommended to leave room for Geneve header growth; 9000 is common in practice (VCF 9.0 network MTU table) └── BFD (Bidirectional Forwarding Detection): Fast failure detection between TEPs
Configure Virtual Networking Connectivity/Routing:
├── BGP Peering: Tier-0 peers with physical ToR switches (eBGP recommended) ├── OSPF: Alternative to BGP for Tier-0 uplink routing ├── Static Routes: Manual routes on Tier-0/Tier-1 (simple topologies) ├── Route Redistribution: Control which routes are advertised (connected, static, NAT) └── ECMP: Equal-Cost Multi-Path for north-south load distribution across Edge nodes
Configure Virtual Networking Services:
├── NAT: SNAT (outbound masquerade), DNAT (inbound service publishing) ├── Load Balancing: L4/L7 LB on Tier-1 (or Avi ALB for advanced) ├── DHCP: Relay or local DHCP server on Tier-1 gateway ├── DNS Forwarding: Conditional DNS forwarding on Tier-1 ├── VPN: IPSec (site-to-site) or L2VPN (extend L2 across sites) └── Edge Firewall: Gateway firewall rules on Tier-0/Tier-1 (north-south filtering)
Holodeck Lab Note: In Holodeck, NSX overlay networking works within nested environment. TEP traffic is encapsulated inside the outer ESXi vDS. Verify MTU end-to-end: outer ESX vDS MTU must be at least 1600 (1700 or more recommended) for the inner NSX overlay to function. Common Holodeck issue: overlay connectivity fails if outer vDS MTU is default 1500.
Key Takeaways
- Exam: VCF hosts are commissioned into the free pool from the vSphere Client (or the SDDC Manager UI as an alternative), not added manually to a cluster; workload domains and cluster expansions that consume the free pool are then done in VCF Operations. Know the commissioning workflow: prepare → commission → assign to domain → auto-configure.
- Exam: ESA vs OSA — ESA = NVMe-only, single storage pool, compression on by default via storage policy, no deduplication. OSA = cache + capacity disk groups, optional cluster-wide dedup and compression. ESA recommended for VCF 9.0 new deployments.
- Exam: NSX in VCF — Tier-0 (north-south, BGP/OSPF) → Tier-1 (per-tenant routing, services) → Segments (L2). DFW for microsegmentation. TEPs for Geneve encapsulation.
- Exam: vSAN storage policies — know FTT + RAID combinations and their space overhead. FTT=1/RAID-1 = 2x overhead. RAID-5 FTT=1 depends on architecture: OSA is always 3+1 = 1.33x (4 hosts); ESA is adaptive - 2+1 = 1.5x under 6 hosts, 4+1 = 1.25x at 6+ hosts. RAID-6 FTT=2 (4+2) = 1.5x.
VCF 9.0 Edge Patterns (Design Library)#
VCF Edge is the 9.x successor to the pre-9.0 "Remote Clusters" concept — the docs state it plainly: "VCF Edge earlier called Remote Clusters is an optimized configuration of VMware Cloud Foundation tailored for edge use cases." Anything an exam presents as "remote clusters" in a 9.x context maps to VCF Edge.
Platform entitlement gates (VCF Edge Models page):
├── Minimum 10 sites or more ├── Minimum 8 CPU cores per host ├── Maximum 256 CPU cores per site ├── Edge hosts physically distinct from data-centre workloads (separate rack/switch) └── VCF Operations is MANDATORY for licensing the Edge environment
The Design Library splits VCF Edge content into two tiers, and the distinction is exam-relevant:
- Design Options WITH Full VCF Stack -> the numbered "VCF Edge Pattern N" series
- Design Options WITHOUT the full stack -> the "VCF Edge Option N" series (3 options)
Pattern count is VERSION-SCOPED: VCF 9.0 documents NINE patterns (1-9). VCF 9.1 adds Pattern 10 (Colocated vCenter with ESX Host at the Edge) for TEN. Quote the count that matches the release you are asked about.
THE NINE VCF 9.0 EDGE PATTERNS
Pattern 1 — Centrally Managed Edge Compute Clusters in a Workload Domain
Each edge site is a vSphere compute cluster inside one central workload domain. Management (vCenter, NSX, VCF Operations, VCF Automation, SDDC Manager) is entirely in the core DC. Constraint: 100 ms / 10 Mbps to the edge. Choose for many sites, one operational model, no local admin staff.
Pattern 2 — Segregated Edge Deployment across Multi-Region Workload Domains
Central management domain, but ONE WORKLOAD DOMAIN PER REGION, each region holding multiple sites and its own independent vCenter for daily operation. Constraint: 100 ms / 10 Mbps. Choose for regional blast-radius separation with central governance.
Pattern 3 — Locally Managed Edge
The management domain is hosted NEAR the edge locations, and a single local vCenter manages both the management and the edge-site workloads. Each site operates autonomously. This is the key contrast with Patterns 1/2/6/8, where the WAN is on the critical path for management and LCM. Choose for oil rigs, mines, offshore platforms, military/defence, sovereignty-constrained and disconnected-tolerant sites. (The doc also captions a figure here "Locally Managed Thick Edge".)
Pattern 4 — VCF Fleet with Multi Region, Distributed Edge
Each major region runs its OWN VCF Instance with its own management domain, all bound into a single VCF Fleet. Management is explicitly dual-level: central IT owns LCM, certificates, password policy and standards; regional IT owns Day-N operations, resources, users and local compliance. A regional VCF Operations Collector handles local collection over WAN latency. The largest and most complex pattern.
Pattern 5 — Dark Site Edge
The dark site runs its OWN independent VCF Instance, separate from the primary Fleet, with a local management domain. A local VCF Offline Depot is deployed to serve software bundles, patches and upgrades in the absence of internet connectivity — this is what keeps LCM working. Two variants: Dark Site 1 buffers collector data offline and synchronises to central VCF Operations when connectivity returns; Dark Site 2 is fully local with its own Fleet and dedicated VCF Operations. Dark sites needing VKS deploy a Harbor bootstrap registry to stage initial components.
LICENSE CHECK-IN: the design guide states VCF Operations "mandates a periodic license check-in (e.g., every 180 days, even for dark sites via their limited connectivity or alternative methods)". Note the wording — 180 days is given as an EXAMPLE, and it is the only figure the guide provides. Treat it as the defensible exam answer, but do not defend it to a panel as a hard product-enforced maximum.
Pattern 6 — vSphere Supervisor at the Edge in a VCF Instance with Multiple Domains
Central management; workload domains hold multiple clusters so edge types can be separated. THIS is where thin/thick edge is defined: thin edge = 2-host clusters in a workload domain; thick edge = "a more substantial cluster with more resources" — no host count is documented for thick edge anywhere. Supervisor is enabled at each edge site alongside traditional VMs.
Pattern 7 — Supervisor Zonal Separation at the Edge
Each site is split into a Control Plane Zone and a Worker/Workload Zone (the doc uses both names). The two zones run on SEPARATE 2-HOST CLUSTERS with external storage — 4 hosts per site, 2 per zone, no vSAN. Unusually, management (VCF Operations, SDDC Manager, vCenter, VCF Automation, NSX) sits AT the edge location. Choose for strong local control and minimal external dependencies.
Pattern 8 — Single Host vSphere Supervisor at the Edge in a VCF Instance
ONE physical ESX host per edge site, with Supervisor enabled including a Supervisor Control Plane VM. Cluster creation and host add are manual in vCenter. Networking is VDS for both Supervisor management and workload networks; storage is shared or local.
HA ADMISSION CONTROL: the design guide is explicit — "vSphere HA is enabled on the cluster however, to make vSphere Supervisor to work, we have disabled HA Admission control in the cluster level in vCenter", and restates it as a requirement. Read that precisely: vSphere HA STAYS ENABLED; it is ADMISSION CONTROL that is disabled. An answer saying "disable vSphere HA" is wrong.
Connectivity: target 1 Gbps or higher, 100 Mbps minimum tolerable, latency below 100 ms. Implications: single point of failure, no vMotion for local HA, and a critical caveat — for multi-node VKS clusters, if a pod using a persistent volume must restart on another worker node, Supervisor MUST reach vCenter to perform the volume detach/attach, or the pod cannot come back online.
Choose for retail stores, bank branches, QSR, cell towers, remote industrial sites.
Pattern 9 — Leveraging Existing VCF Operations for Far Edge Expansion
An existing Fleet is extended to far-edge sites under VCF Edge licensing; a vCenter for those sites sits in the existing DC or a colo and connects to VCF Operations. VCF Operations provides LICENSE MANAGEMENT AND UNIFIED MONITORING ONLY — verbatim: "VCF Operation will not perform life cycle management of vCenter and hosts which are connected to this vCenter." LCM stays with the edge vCenter.
Pattern 10 — Colocated vCenter with ESX Host at the Edge (VCF 9.1 ONLY)
The management domain stays central, but each edge site needing colocated management deploys its own VCSA on-site next to its ESX cluster, imported into VCF as a workload domain. Option A is greenfield (deploy new, then brownfield-import); Option B imports an existing locally-managed vCenter with no redeployment and no VM maintenance window. Constraint: SDDC Manager to vCenter latency under 100 ms.
SIZING TABLE (from the pattern index page)
Four supported shapes: 1-node cluster in a VCF Instance | 2-node with external storage in a workload domain | 3-node vSAN cluster | 4-node VCF Fleet.
├── Max hosts per cluster: 64 (all four) ├── Max workload domains: NOT SUPPORTED for 1-node; 24 for the other three ├── 1-node storage: local or external NFS/FC. 2-node: external NFS or FC, NO vSAN. 3/4-node: vSAN or external └── VKS supported in all four
Version drift to watch: the 9.0 index states 100 ms latency / 10 Mbps; the 9.1 index states 300 ms / 10 Mbps for the same columns. Cite the figure for the release you are asked about.
THE THREE NON-FULL-STACK OPTIONS
Option 1 — VCF Operations with vCenter for Distributed Edge: central VCF Operations plus centrally located vCenters managing many distributed sites.
Option 2 — Thin Edge with vSphere Supervisor on Two-Node vSAN: 2a places License Server, VCF Operations, vCenter and a Witness VM in a management cluster, recommends ONE Control Plane VM on the 2-node vSAN cluster, and allows up to 300 ms / 10 Mbps vCenter-to-ESX; 2b adds a unified software depot, centralised logging and password/certificate management, deployed with the VCF Installer's VVF option. The docs state the key deviation from Pattern 6 explicitly: this design does NOT incorporate a full VCF stack, but it does leverage vSAN.
Option 3 — vSAN Witness Placement for Distributed Edge: witness placed outside the data-bearing edge sites to hold quorum for 2-node vSAN edges.
TRAP: "THIN EDGE" IS DEFINED TWO INCOMPATIBLE WAYS
Pattern 6 (9.0): thin edge = 2-host clusters INSIDE a full VCF stack, centrally managed.
Option 2 (9.1): Thin Edge = 2-node vSAN cluster explicitly WITHOUT the full VCF stack.
Any statement asserting one universal definition of thin edge — or any host count for "thick edge" — is unsupported by the documentation.
Key Takeaways
- Count is version-scoped: VCF 9.0 documents NINE numbered Edge patterns (1-9); VCF 9.1 adds Pattern 10 for TEN. Plus three non-full-stack 'Options' in both releases.
- Pattern 5 = Dark Site Edge: own independent VCF Instance + local VCF Offline Depot for LCM. License check-in is given as 'e.g., every 180 days' — an example in the guide, not a hard enforced maximum.
- Pattern 8 = Single Host vSphere Supervisor: one ESX host per site. vSphere HA stays ENABLED; HA ADMISSION CONTROL is what must be disabled. 'Disable vSphere HA' is a wrong answer.
- Pattern 3 = Locally Managed Edge: management domain sits NEAR the edge and one local vCenter runs both management and workloads — the autonomy/WAN-outage-resilience choice, versus Patterns 1/2/6/8 where the WAN is on the management critical path.
- Pattern 7 = Supervisor Zonal: 2-host cluster per zone x 2 zones = 4 hosts per site, external storage, no vSAN, and management located AT the edge.
- Pattern 9 = Far Edge Expansion: VCF Operations does licensing and monitoring ONLY — it explicitly does NOT perform LCM of that vCenter or its hosts.
- VCF Edge is the rename of pre-9.0 'Remote Clusters'. Entitlement gates: 10+ sites, 8+ cores per host, 256 cores per site max, and VCF Operations is mandatory for Edge licensing.
- Defence trap: 'thin edge' has two incompatible definitions (Pattern 6 = 2-host inside full stack; Option 2 = 2-node vSAN without full stack), and 'thick edge' has NO documented host count.
VCF Management Operations (Objective 4.2)#
Blueprint Objective 4.2 — VCF: Manage
Fleet Management Capabilities in VCF Operations (Obj 4.2)
VCF Operations is the unified management plane for VCF 9.0. It surfaces the SDDC Manager workflows (the SDDC Manager UI is deprecated, the appliance and API remain in every VCF Instance) and adds fleet-level capabilities across instances.
Fleet Management Functions (VCF Operations console, VCF 9.0.x):
├── Fleet Management > Lifecycle: component inventory and upgrades per VCF Instance and for the VCF Operations/VCF Automation components; cluster image updates via vSphere Lifecycle Manager ├── Fleet Management > Certificates: certificate inventory and replacement for each VCF Instance's components ├── Fleet Management > Passwords: view, update and remediate managed credentials (see Password Management below for the 9.0.x rotation known issue) ├── Fleet Management > Identity & Access: VCF Single Sign-On, Active Directory and identity-provider configuration ├── Inventory: VCF Instances, workload domains, clusters, hosts (free pool and assigned) and standalone vCenters managed by the fleet ├── Capacity, cost, compliance and health dashboards across all instances (VCF Operations collectors; certificate and account data can take hours to appear after onboarding — VCF 9.0.1 known issue) └── Not fleet functions: cross-instance DFW policy push (that is NSX Federation) and HCX migration orchestration (HCX has its own manager); do not expect them under Fleet Management
VCF Operations Dashboard Features:
├── Private Cloud status (management + workload domains) ├── Host inventory (free pool, commissioned, decommissioned) ├── Certificate status (expiry timeline, rotation history) ├── Password rotation status (auto-rotated vs manual) ├── Lifecycle management (bundle availability, upgrade readiness) └── Alert center (cross-component alerts from vCenter, NSX, vSAN)
Identity Management & RBAC (Obj 4.2)
VCF Identity Architecture:
├── Local Users: Built-in user database (administrator@vcf.local) ├── Active Directory/LDAP: External identity source integration │ ├── LDAP over SSL (port 636) recommended for production │ ├── User/group sync: Automatic, configurable interval │ └── Nested group support: Yes (up to 5 levels) ├── SAML 2.0: Federation with enterprise IdP (Okta, Azure AD, ADFS) │ ├── SP-initiated SSO: User clicks login → redirected to IdP │ ├── Attribute mapping: IdP groups → VCF roles │ └── Session timeout: Configurable (default 8 hours) └── OAuth 2.0: API client authentication (machine-to-machine)
RBAC Roles in VCF:
├── System Administrator: Full access to VCF Operations, all Private Clouds, all operations ├── Cloud Administrator: Manage specific Private Clouds (workload domains) ├── Network Administrator: NSX configuration, segment management, DFW policies ├── Security Administrator: Certificate management, password rotation, compliance ├── Operator: Read-only access to dashboards and reports ├── Service Account: API-only access for automation tools └── Custom Roles: Granular permission sets (create via VCF Operations API)
Role Assignment:
├── VCF Operations UI → Administration → Access Control → Users & Groups ├── Assign roles at: Instance level, Private Cloud level, or Cluster level ├── Principle of Least Privilege: Assign minimum required role └── Audit: All role changes logged in VCF Operations audit trail
License Management (Obj 4.2)
VCF Licensing Model (post-Broadcom acquisition):
├── Subscription-based: per-core licensing (replaced the perpetual per-socket model) │ ├── Minimum 16 cores per physical CPU (VCF 9.0.1 docs p.80) │ └── License assigned to vCenter instances; connected ESX hosts are licensed automatically ├── Licensing workflow: │ ├── VCF Operations is registered with Broadcom in connected licensing mode (recommended, VCF-OPS-RECD-LIC-001) or licensed offline │ ├── The VCF or vSphere Foundation license is added in VCF Operations, and vCenter instances are licensed from there │ └── 90-day evaluation until licensed ├── Entitlement: one VCF per-core subscription covers vSphere, vSAN (1 TiB per licensed core, VCF 9.0.1 docs p.1465), NSX, VCF Operations and VCF Automation; the docs define no "VCF Standard/Advanced" tiers ├── Add-ons licensed through VCF Operations: │ ├── VMware vSAN (TiB) for capacity beyond the per-core entitlement │ ├── VCF Operations for Networks, Avi Load Balancer, vDefend │ └── Add-on names change; the VCF Operations licensing page, not a memorised SKU list, is the exam-safe reference ├── License Compliance: VCF Operations tracks core count vs entitlement └── Expiry Management: VCF Operations alerts 90/60/30 days before expiry
License Operations in VCF Operations:
├── Add License: VCF Operations → Administration → Licensing → Add License Key ├── Assign License: Automatically applied to all hosts in instance ├── View Usage: Dashboard shows cores consumed vs entitled ├── Export Report: License compliance report (PDF/CSV) for audit └── Renewal: Replace license key before expiry (no downtime)
Certificate Management (Obj 4.2)
VCF Certificate Architecture:
├── VCF CA: Built-in Certificate Authority (issues certificates for all VCF components) ├── External CA: Microsoft CA, DigiCert, Let's Encrypt (enterprise option) ├── Component Certificates: │ ├── vCenter: Server certificate + machine SSL certificate │ ├── NSX Manager: Cluster certificate + API certificate │ ├── ESXi: Host certificate (signed by VCF CA or external CA) │ ├── VCF Operations: Appliance certificate │ └── Edge Nodes: Tunnel endpoint certificates └── Certificate Chain: Root CA → Intermediate CA (optional) → Leaf certificates
Certificate Rotation:
├── VCF Operations → Fleet Management > Certificates → view all component certificates (VCF Management and each VCF Instance) ├── Auto-renewal: activated per VCF Management or VCF Instance with the Activate Auto-renewal toggle (fixed 60-day threshold, see below) ├── Manual rotation: Select component → Rotate → specify CA → generate CSR or auto-sign ├── Impact: Certificate rotation may cause brief API interruption (seconds) │ ├── vCenter: Rolling restart of vpxd service │ ├── NSX: API unavailable for ~30 seconds during rotation │ ├── ESXi: Host reconnects to vCenter after cert update │ └── VCF Operations: Self-restart after own certificate rotation ├── Validation: VCF Operations validates certificate chain, key length (2048+ RSA), expiry ├── Auto-renewal (VCF Operations Fleet Management): automatic renewal happens 60 DAYS before certificate expiration, for VMCA / Microsoft CA / OpenSSL / self-signed certs on components that support non-disruptive update. Documented in VCF 9.0 (VCF 9.0.1 docs p.2924, Fleet Management > Certificates). ├── vCenter-NATIVE VMCA renewal is different and fixed (starting with VCF 9.0.2, VCF 9.0.1 docs p.388): vCenter Machine SSL auto-renews when less than 5 days remain; ESX SSL at less than 10 days (vpxd.certmgmt.certs.autoRenewThreshold); a pre-expiration ALARM fires at 30 days. In VCF 9.1 the ESX value is documented as 30 days — version-scope it. ├── VCF Operations auto-renewal covers only VMCA, Microsoft CA, OpenSSL and self-signed certificates (configure the Microsoft CA or OpenSSL CA first); certificates from other external CAs (for example DigiCert or imported third-party certificates) are outside that list, and vCenter-native auto-renew is inoperative when vpxd.certmgmt.mode=custom └── Do not confuse ALERTING with RENEWAL: the 90/60/30-day figures elsewhere are licence-expiry alerts, not certificate renewal
Password Management (Obj 4.2)
VCF Password Architecture:
├── Credential Vault: VCF Operations stores all component credentials securely (encrypted at rest) ├── Managed Accounts: │ ├── ESXi root passwords (per-host) │ ├── vCenter administrator@vsphere.local │ ├── NSX admin │ ├── VCF Operations admin │ ├── Service accounts (SDDC Manager service, backup accounts) │ └── vSAN witness passwords ├── Rotation in 9.0.x: the 5.x options (rotate all, rotate, schedule rotation) are not present in VCF Operations — VCF 9.0.1 known issue; rotate VCF core component passwords through the SDDC Manager UI or SDDC Manager API. Scheduled rotation (30/60/90 days) existed in SDDC Manager 5.2 and never covered ESX root │ ├── VCF Operations > Fleet Management > Passwords offers view, update (you supply the new password) and remediate (re-sync a credential changed outside VCF) ├── Password length is PER COMPONENT, not one global rule: SDDC Manager vcf/root/backup min 12; SDDC Manager admin@local 15-127; vCenter root min 15; administrator@vsphere.local 8-20; ESX root 7-40; NSX root/admin/audit 12-128; VCF Operations root/admin(OS) min 15, admin(app) min 8; VCF Automation min 15. SDDC-Manager-GENERATED rotated passwords are exactly 20 characters. VCF 9.1 adds fleet/instance-scoped password policies but publishes no new default length │ ├── History: Last 5 passwords cannot be reused │ └── Notification: VCF Operations alerts before rotation (email/webhook) ├── Rotate: SDDC Manager UI → Security → Password Management → select account → Rotate (or the SDDC Manager credentials API); Update/Remediate: VCF Operations → Fleet Management > Passwords └── Password Retrieval: VCF Operations → Fleet Management > Passwords → account → show (admin role); newly connected instances may take up to a day to list their accounts (9.0.1 known issue)
Password Rotation Considerations:
├── Coordinate with backup schedules (backup credentials may need update) ├── Update external integrations (monitoring tools, scripts using rotated credentials) ├── Test after rotation: Verify all component connectivity ├── Lockout prevention: VCF Operations coordinates rotation to avoid lock-out cascades └── Emergency: Reset password via VCF Operations CLI if GUI inaccessible
Holodeck Lab Note: In Holodeck, VCF Operations password rotation can be tested safely. Rotate a vCenter or NSX service credential from the SDDC Manager UI (Security > Password Management) and update an ESX root password from VCF Operations > Fleet Management > Passwords (ESX root is not rotated automatically). Verify connectivity after the change by logging in with the new credential. Certificate rotation in Holodeck uses self-signed VCF CA (acceptable for lab).
Key Takeaways
- Exam: VCF Operations provides fleet-level management — inventory sync, cross-instance policy, centralized reporting. Know VCF Operations dashboard components.
- Exam: RBAC roles — System Admin (full access), Cloud Admin (per-PC), Network Admin (NSX), Security Admin (certs/passwords). Assign at instance or PC level.
- Exam: Certificate auto-renewal in VCF Operations (Fleet Management > Certificates) fires 60 DAYS before expiry (VCF 9.0). vCenter-native VMCA auto-renew (VCF 9.0.2+) is separate and fixed: Machine SSL 5 days, ESX SSL 10 days, with a 30-day pre-expiry alarm. Microsoft CA and OpenSSL certificates do auto-renew once the CA is configured; certificates from other external CAs are not covered. Alerting is not renewal.
- Exam: VCF 9.0 password management lives in VCF Operations (Fleet Management > Passwords: view, update, remediate). In 9.0.x the 5.x rotate / schedule-rotation options are not in VCF Operations (known issue) — use the SDDC Manager UI or API. Length rules are per component; ESX root is never auto-rotated.
VCF Operations & Observability (Objective 4.3)#
Blueprint Objective 4.3 — VCF: Operate
VCF Network Operations & Operations for Logs (Obj 4.3)
VCF Operations in VCF context includes deeper integration than VVF — specifically NSX adapter, network topology visualization, and cross-component correlation.
VCF Operations — VCF-Specific Capabilities:
├── NSX Adapter: Collects NSX Manager metrics and topology
│ ├── Metrics: Firewall rule hit count, segment traffic, Edge throughput
│ ├── Topology: Tier-0/Tier-1/Segment hierarchy visualization
│ ├── Flow analysis: East-west traffic patterns between segments
│ └── DFW analytics: Most/least used rules, shadow rule detection
├── VMware Cloud Foundation adapter: Collect VCF instance health and lifecycle data
├── Cross-Component Correlation:
│ ├── VM slow → check host CPU (vCenter) → check segment congestion (NSX) → check vSAN latency
│ ├── Unified timeline: Correlate events across vCenter, NSX, vSAN in single view
│ └── Root cause analysis: Automated symptom-to-cause chain
└── Capacity Planning:
├── Demand forecasting: Predict when cluster needs additional hosts
├── What-if analysis: Model adding hosts or VMs before commitment
├── Reclaimable resources: Identify oversized VMs (CPU/memory waste)
└── Cost optimization: Right-size recommendations with savings estimateVCF Operations Cluster Components & Deployment (Obj 4.3):
├── Analytics Node: Processes collected data (metrics, events, alerts) ├── Collector Node: Gathers data from adapters (vCenter, NSX, vSAN, VCF Operations) ├── Remote Collector: For distributed data centers (reduces WAN bandwidth) ├── Data Node: Time-series database (TSDB) for metric storage ├── Sizing (VCF): │ ├── Small (up to 4,000 objects): 1 node (4 vCPU, 16GB, 512GB) │ ├── Medium (up to 20,000 objects): 2-node cluster + remote collector │ ├── Large (up to 100,000 objects): Multi-node cluster + data nodes │ └── Note: VCF typically has more objects than VVF due to NSX (segments, DFW rules, Edge nodes) └── HA: Analytics node HA (active-passive) recommended for production
VCF Operations for Logs — VCF-Specific (Obj 4.3):
├── Log Sources (beyond VVF): │ ├── NSX Manager logs: Control plane events, DFW rule changes, policy updates │ ├── NSX Edge logs: Routing changes, NAT translations, LB health │ ├── VCF Operations logs: Lifecycle operations, host commissioning, bundle downloads │ └── VCF Automation logs: Blueprint deployments, catalog requests, ABX actions ├── Content Packs: │ ├── NSX Content Pack: Pre-built dashboards for NSX events │ ├── VCF Content Pack: VCF Operations operations dashboard │ └── vSAN Content Pack: Storage-specific log analysis └── Integration: Bidirectional with VCF Operations (launch-in-context between metrics and logs)
Differentiate Metrics, Properties, and Logs (Obj 4.3):
Metrics:
├── Definition: Numeric, time-series data collected at regular intervals ├── Examples: CPU usage %, memory consumed MB, disk IOPS, NSX firewall throughput ├── Collection: Every 5 minutes (default), stored in TSDB ├── Use: Trending, alerting, capacity planning, anomaly detection └── Retention: 5-min granularity (24h), 1-hour (1 month), 1-day (1 year)
Properties:
├── Definition: Configuration attributes — static or slowly changing ├── Examples: VM name, ESXi version, NSX segment name, vSAN disk type ├── Collection: On inventory sync (every 5 min for changes) ├── Use: Grouping, filtering, compliance, inventory views └── Retention: Current value + history of changes
Logs:
├── Definition: Unstructured text events with timestamps ├── Examples: "DFW rule 1024 applied to VM web-01", vpxd error stack trace ├── Collection: Real-time syslog ingestion (UDP 514, TCP 1514, TLS 6514) ├── Use: Root cause analysis, forensics, audit trail, security investigation └── Retention: 30 days default (configurable, archive to NFS/S3)
Custom Views, Reports & Dashboards (Obj 4.3):
Custom Views:
├── List View: Tabular display of objects with metrics columns ├── Summary View: Aggregated statistics (avg, max, min, count) ├── Trend View: Time-series chart for selected metrics ├── Distribution View: Histogram of metric values across objects ├── Filters: Object type, property value, tag, custom group └── Export: CSV, PDF, schedule email delivery
Reports:
├── Pre-built Templates: Capacity, Performance, Compliance, Cost ├── Custom Reports: Combine multiple views + charts + text ├── Scheduling: Daily, weekly, monthly auto-generation ├── Format: PDF or CSV export └── Distribution: Email to stakeholders, archive to shared storage
Dashboard Creation:
├── Widget Types: Scoreboard, heatmap, top-N, trend, alert list, object relationship ├── Widget Interactions: Click-to-filter across widgets (host → VMs, cluster → hosts) ├── Sharing: Per-user/group, read-only or edit, import/export as JSON └── Content Packs: Pre-built dashboards (vSAN, NSX, K8s, VCF Operations)
Alerting & Notifications (Obj 4.3):
├── Symptom: Single condition (metric threshold + duration) ├── Alert Definition: One or more symptoms with AND/OR logic ├── Criticality: Info, Warning, Immediate, Critical ├── Notification: Email (SMTP), webhook (REST), SNMP trap, Slack/PagerDuty ├── Recommendation: Suggested remediation steps attached to alert └── Alert Lifecycle: New → Acknowledged → Resolved (manual or auto-clear)
Costing & Chargeback (Obj 4.3):
├── Rate Cards: Define cost per resource unit ($/vCPU/month, $/GB storage/month) ├── Cost Drivers: Server hardware, storage, network, licensing, power/cooling ├── Chargeback: Bill business units based on actual VM resource consumption ├── Showback: Display costs without billing (awareness mode) ├── Reports: Cost per VM, per department, per Private Cloud, trend analysis └── Setup: VCF Operations → Administration → Cost Settings → Rate Card Editor
Policies & Compliance (Obj 4.3):
├── Operational Policies: Define thresholds per object type/group │ ├── Capacity: Alert when remaining capacity < N days │ ├── Utilization: Alert on sustained over/under utilization │ └── Override: Per-object policy customization ├── Compliance Benchmarks: │ ├── CIS ESXi 8 Benchmark: 100+ configuration checks │ ├── DISA STIG for vSphere: DoD security requirements │ ├── PCI-DSS: Payment card industry requirements │ └── Custom: Define organization-specific compliance rules ├── Compliance Dashboard: Per-host/cluster green/yellow/red status ├── Drift Detection: Alert when configuration deviates from baseline └── Remediation: Recommended esxcli/PowerCLI commands for non-compliant items
Application Monitoring & Service Discovery (Obj 4.3):
├── Service Discovery: Auto-detect applications in VMs │ ├── Discovers: Web servers (Apache, Nginx, IIS), databases (MySQL, PostgreSQL, Oracle), app servers (Tomcat, JBoss) │ ├── Method: Agentless (port scan + protocol detection) or agent-based (Telegraf) │ └── Output: Application → VM → Host → Cluster dependency map ├── Application-Aware Monitoring: │ ├── Response time, throughput, error rate per application │ ├── Dependency visualization (which VMs serve which applications) │ └── Impact analysis: If host fails, which applications are affected? └── Integration: ServiceNow CMDB, Slack notifications, PagerDuty alerts
vSAN Storage Operations (Obj 4.3):
├── Deep vSAN Monitoring: Disk health, rebuild progress, dedup/compression ratio ├── Capacity Forecasting: Predict when vSAN needs additional disks/hosts ├── Performance Monitoring: Per-disk group latency, IOPS, throughput ├── Health Correlation: vSAN health → VM performance impact analysis └── Alerts: Disk failure prediction, congestion warning, capacity threshold
Holodeck Lab Note: VCF Operations in Holodeck can monitor all nested components including NSX Manager (add NSX adapter with NSX Manager IP and credentials). The NSX adapter enables network topology dashboards and DFW analytics. Install NSX Content Pack from VMware Marketplace for pre-built NSX dashboards.
Key Takeaways
- Exam: VCF Operations in VCF adds NSX adapter (DFW analytics, network topology), VCF Operations adapter, and cross-component correlation. Know these VCF-specific capabilities.
- Exam: Metrics = numeric time-series (CPU %, IOPS). Properties = config attributes (VM name, ESXi version). Logs = text events (syslog). Know the differences.
- Exam: Dashboards use widgets with interactions (click-to-filter). Reports combine views + charts. Both support scheduling and sharing.
- Exam: Compliance = CIS/DISA STIG benchmarks. Costing = rate cards + chargeback/showback. Service Discovery = auto-detect apps in VMs.
VCF Automation — Consume & Automate (Objective 4.4)#
Blueprint Objective 4.4 — VCF: Consume and Automate
VCF Automation Use Case (Obj 4.4)
VCF Automation (formerly vRealize Automation / Aria Automation) is the self-service and governance platform in VCF. It is NOT included in VVF — it's a VCF-only capability.
What changed in 9.0 (read the rest of this block with this framing):
├── Two organization types: All Apps organizations (workload domains with Supervisors, running VMs and containers) and VM Apps organizations (VM-only clusters); a workload domain, its vCenter and clusters cannot be used by both (VCF 9.0.1 docs p.473) ├── All Apps model: each organization is mapped to one or more vSphere Supervisors through Regions; organizations hold Projects, Projects hold vSphere Namespaces (pp.909-910) ├── VM Apps model: the Aria Automation 8.x-style constructs below (cloud accounts, cloud zones, cloud templates, catalog, policies) — but the former Assembler (Cloud Assembly), Service Broker and Orchestrator UIs are merged into one UI: Consume (Catalog, Deployments), Design (Blueprints, Property Groups, Custom Resources, Resource Actions) and Content & Policies (Content Sources, Content, Policies, Notifications); the services remain in the backend, so RBAC is unchanged (p.112) ├── Orchestrator is embedded as VCF Operations orchestrator (Orchestrator tab) (p.112) └── VCF Automation Pipelines (formerly Code Stream) is no longer supported (p.239)
VCF Automation Purpose:
├── Self-Service Portal: Developers request infrastructure via catalog ├── Cloud Templates: Infrastructure-as-Code (YAML) for multi-cloud deployments ├── Governance: Approval workflows, cost controls, lease management ├── Day-2 Operations: Automated resize, snapshot, backup, decommission ├── Multi-Cloud: Deploy to vSphere, AWS, Azure, GCP from single catalog └── Extensibility: ABX (Action Based Extensibility) for custom logic
VCF Automation Components & Deployment (Obj 4.4):
Architecture:
├── Assembler (formerly Cloud Assembly; in 9.0 its UI is the Design menu, p.112): Template design and deployment engine
│ ├── Cloud Accounts: Connections to vCenter, NSX, AWS, Azure
│ ├── Cloud Zones: Compute/storage placement policies
│ ├── Flavor Mappings: VM sizing (small=2vCPU/4GB, medium=4vCPU/8GB)
│ ├── Image Mappings: OS images per cloud (e.g., ubuntu → vSphere template + AWS AMI)
│ └── Network Profiles: Network assignment per cloud zone
├── Service Broker (in 9.0 its UI is the Consume and Content & Policies menus, p.112): Catalog management and request processing
│ ├── Catalog Items: Published cloud templates available to consumers
│ ├── Content Sources: Assembler templates, VCF Operations orchestrator workflows, external sources
│ ├── Entitlements: Who can request what (user/group → catalog item)
│ └── Policies: Approval, lease, Day 2 actions, quota and other policy types (VM Apps: Content and Policies > Policies > Definitions, p.6209)
├── VCF Operations orchestrator (embedded in VCF Automation, Orchestrator tab, p.112): Workflow engine for automation
│ ├── Pre-built Workflows: VM lifecycle, NSX config, vSAN management
│ ├── Custom Workflows: JavaScript/Python actions, drag-and-drop designer
│ ├── Event-Based Triggers: Deploy hook, post-provision, on-delete
│ └── Integration: REST API, SSH, PowerShell, SNMP
└── Deployment:
├── VCF Automation appliance: 12 vCPU, 48GB RAM, 200GB disk
├── Clustered: 3-node cluster for HA (recommended for production)
├── Integrated: Deployed and managed via VCF Operations
└── Access: https://<automation-fqdn>/cloudConfigure Region (Obj 4.4):
Regions in VCF Automation:
├── All Apps organizations: a Region maps the organization to one or more vSphere Supervisors (pp.909-910); the cloud-account regions below describe the VM Apps model ├── Definition: A region maps to a VCF instance or cloud provider region │ ├── vSphere Region: Maps to a vCenter + associated NSX + vSAN │ ├── AWS Region: Maps to an AWS region (us-east-1, eu-west-1) │ ├── Azure Region: Maps to an Azure region (eastus, westeurope) │ └── GCP Region: Maps to a GCP region (us-central1, europe-west1) ├── Purpose: Enable multi-region deployment with placement policies ├── Configuration: │ ├── Add Cloud Account (vCenter connection with credentials) │ ├── Associate cloud zones to region (which clusters serve this region) │ ├── Configure capability tags (e.g., "tier:gold", "location:dc-a") │ └── Map regions to projects (which teams can deploy to which regions) └── Use Case: "Deploy my app to the nearest VCF instance" → region selection
Configure Multi-Organizational Tenancy (Obj 4.4):
Multi-Tenancy in VCF Automation:
├── Organization type: All Apps (Organization → Projects → vSphere Namespaces, p.910) or VM Apps (p.473)
├── Organizations: Top-level isolation boundary
│ ├── Each org has its own: users, projects, cloud accounts, catalog, policies
│ ├── Data isolation: Org A cannot see Org B's deployments
│ └── Use case: MSP (Managed Service Provider) hosting multiple customers
├── Projects: Resource boundary within an organization
│ ├── Members: Users/groups assigned to project with roles
│ ├── Roles: Administrator, Member, Viewer
│ ├── Resource Limits: Max VMs, max CPU, max memory, max storage
│ ├── Cloud Zones: Which compute resources this project can use
│ └── Naming Convention: Project-level naming template (e.g., ${project}-${resource}-${count})
├── Custom Naming: Template-driven resource naming
│ ├── Variables: ${project}, ${resource}, ${org}, ${user}, ${count}
│ ├── Example: "prod-web-${count}" → prod-web-001, prod-web-002
│ └── Uniqueness: VCF Automation ensures no name collisions
└── Lease Management:
├── Lease Duration: Auto-delete deployment after N days (prevent sprawl)
├── Warning: Email notification before lease expiry
├── Extension: User can request extension (requires approval if policy set)
└── Default: No lease (deployments persist until manually deleted)Configure Provider Networking (Obj 4.4):
Provider Networking in VCF Automation:
├── Network Profiles: Define how deployments get network connectivity │ ├── Existing Networks: Use pre-created NSX segments or vDS port groups │ ├── On-Demand Networks: VCF Automation creates NSX segments dynamically │ │ ├── Routed: Connected to Tier-1 gateway (internet-accessible) │ │ ├── Isolated: No external connectivity (internal communication only) │ │ └── Outbound-only: NAT for outbound, no inbound (security zones) │ └── Private Networks: Isolated per deployment (multi-NIC VMs) ├── IP Address Management (IPAM): │ ├── Internal IPAM: VCF Automation manages IP pools │ ├── External IPAM: Integration with Infoblox, BlueCat │ └── IP Ranges: Define start/end IP per network profile ├── Load Balancer Integration: │ ├── NSX LB: Tier-1 L4/L7 load balancing │ ├── Avi ALB: Advanced L7 with WAF, analytics │ └── Cloud Template: LB defined as resource in YAML template ├── Security Groups: NSX security groups applied to deployed VMs │ ├── Existing Groups: Reference pre-created NSX security groups │ ├── On-Demand Groups: Created per-deployment with DFW rules │ └── Tag-Based: VMs automatically added to groups via tags └── DNS Integration: Auto-create DNS records for deployed VMs
Cloud Templates (Obj 4.4):
Cloud Template YAML Example:
formatVersion: 1
inputs:
size:
type: string
enum: [small, medium, large]
default: small
count:
type: integer
default: 1
resources:
web-server:
type: Cloud.vSphere.Machine
properties:
image: ubuntu-2204
flavor: ${input.size}
count: ${input.count}
networks:
- network: ${resource.web-network.id}
customizationSpec: linux-cloud-init
cloudConfig: |
packages:
- nginx
runcmd:
- systemctl enable nginx
- systemctl start nginx
web-network:
type: Cloud.NSX.Network
properties:
networkType: routed
constraints:
- tag: env:productionCloud Template Capabilities:
├── Inputs: User-provided parameters (dropdowns, text, numbers) ├── Resources: Infrastructure objects (VMs, networks, LBs, disks) ├── Constraints: Tag-based placement (match cloud zone capability tags) ├── cloud-init: Guest OS customization (packages, scripts, users) ├── Iterations: count property for multi-instance deployment ├── Dependencies: Implicit (resource references) and explicit (dependsOn) └── Version Control: Templates versioned in Git (GitOps integration)
Approval Policies:
├── Pre-Approval: Required before deployment starts │ ├── Approvers: Named users or group │ ├── Conditions: Based on cost, VM count, network type │ └── Timeout: Auto-deny after N days if not approved ├── Day-2 Approval: Required for resize, reconfigure, delete operations └── Integration: Email notification, Slack webhook, ServiceNow ticket
Holodeck Lab Note: VCF Automation can be deployed in Holodeck but requires significant resources (12 vCPU, 48GB RAM per appliance). For lab purposes, single-node deployment is acceptable. Configure a vCenter cloud account pointing to the Holodeck vCenter. Create simple cloud templates that deploy VMs to the Holodeck cluster. On-demand NSX networks require NSX integration configured in VCF Operations.
Key Takeaways
- Exam: VCF Automation in 9.0 has All Apps organizations (Supervisor-based: Organization [mapped to Supervisors through Regions, VCF 9.0.1 docs p.909] → Projects → vSphere Namespaces, p.910) and VM Apps organizations (p.473). In VM Apps the former Assembler, Service Broker and Orchestrator UIs are merged into Consume / Design / Content & Policies with an embedded VCF Operations orchestrator (p.112); Pipelines is no longer supported (p.239). VCF-only, not in VVF.
- Exam: Regions map to VCF instances or cloud provider regions. Cloud zones within regions define placement. Capability tags drive placement decisions.
- Exam: Multi-tenancy = Organizations (isolation) → Projects (resource limits, members, cloud zones). Lease management prevents VM sprawl.
- Exam: Provider networking = existing, on-demand (routed/isolated/outbound), private networks. IPAM internal or external (Infoblox). Security groups via NSX.
- Exam: Cloud templates (YAML) — inputs, resources, constraints, cloud-init. Approval policies enforce governance. Version control via Git.
VCF Troubleshooting Methodology & Scenarios (Scenarios T1–T4, mapped to official 2V0-17.25 Objectives 2.4, 4.2, 4.3, 4.4)#
The VCF Admin exam Section 4 tests practical troubleshooting across all VCF layers. This theory covers the troubleshooting methodology and common scenarios for vSphere networking, VCF lifecycle management, VCF Operations, and VCF Automation.
General Troubleshooting Methodology
VCF troubleshooting follows a layered approach: identify symptoms → isolate the layer (physical/virtual/application) → gather diagnostic data → correlate events across components → remediate → validate fix → document root cause.
Tools by Layer: Physical network (switch CLI, cable tester, LLDP/CDP), vSphere networking (esxtop, packet capture, net-stats), NSX overlay (Traceflow, Central CLI, transport node status), vSAN (vSAN Health Service, vSAN Observer, esxtop for disk stats), VCF lifecycle (VCF Operations > Fleet Management > Lifecycle; SDDC Manager task API /v1/tasks and lcm logs as secondary evidence), VCF Operations (dashboards, alerts, super metrics, log queries), VCF Automation (deployment history, event logs, extensibility action logs).
T1 — Troubleshoot vSphere Networking Issues (official Objective 2.4, Network Fundamentals)
esxtop Network Counters: Launch esxtop on ESXi host, press 'n' for network view. Critical counters:
%DRPTX / %DRPRX (Dropped Transmit / Receive): Packets dropped at the vNIC or pNIC level. Values > 0.01% indicate contention or misconfiguration. Cause: ring buffer exhaustion, MTU mismatch, uplink saturation. Fix: increase ring buffer (ethtool -G vmnicX rx 4096), verify MTU end-to-end, check uplink utilization.
MbTX / MbRX (Megabits Transmitted / Received): Throughput per vNIC/pNIC. Compare against link speed — if MbTX approaches link capacity, the NIC is saturated. Fix: add uplinks, enable LACP, or redistribute VMs across hosts.
USED-BY: Shows which port group and VM is using each vNIC. Essential for mapping traffic to physical uplinks during troubleshooting.
Troubleshoot Network — Common Scenarios:
Scenario 1: vMotion fails with "migration to host X failed with error timed out." Diagnostic steps: (1) Verify vMotion VMkernel adapter exists on both source and destination hosts. (2) Check vMotion network connectivity: vmkping -I vmkX <dest-vMotion-IP>. (3) Verify MTU consistency — if jumbo frames enabled on one side but not the other, large packets are silently dropped. (4) Check vMotion TCP port 8000 is not blocked by physical firewall. (5) Verify EVC mode compatibility if hosts have different CPU generations.
Scenario 2: VM loses network connectivity after adding to new port group. Diagnostic steps: (1) Verify VLAN ID on port group matches physical switch trunk configuration. (2) Check uplink teaming policy — active/standby vs LACP. (3) Verify security policy settings (promiscuous mode, MAC changes, forged transmits) if VM uses nested virtualization or load balancer VIPs. (4) Use packet capture on ESXi: pktcap-uw --uplink vmnic0 --dir 0 -o /tmp/capture.pcap. (5) Check DVS health check for VLAN/MTU mismatches.
Scenario 3: Intermittent packet loss on overlay network. Diagnostic steps: (1) Verify MTU 9000 end-to-end from ESXi TEP → physical switch → destination TEP. Use vmkping -d -s 8972 -I vmkX <dest-TEP>. (2) Check TEP connectivity via nsxcli on transport node: get logical-switch transport-node-table. (3) Verify BFD status between TEPs. (4) Check physical switch for CRC errors or interface resets on uplink ports.
T2 — Troubleshoot VCF Lifecycle Management Issues (official Objective 4.2, VCF: Manage — lifecycle)
VCF 9.0 Lifecycle Architecture: SDDC Manager no longer provides the lifecycle-management API (/v1/system/precheck); its lifecycle capabilities moved to VCF Operations (VCF 9.0.1 docs p.227). Run prechecks and upgrades from VCF Operations > Fleet Management > Lifecycle. Instance-level operations (upgrades, host commissioning, domain creation) still execute as asynchronous SDDC Manager tasks with sequential sub-tasks; if a sub-task fails, the update shows Failed with the reason and remediation steps. Upgrade logs: /var/log/vmware/vcf/lcm/ on the SDDC Manager appliance — after SDDC Manager is upgraded to 9.0, all logging goes to lcm-debug and lcm.log is no longer updated (VCF 9.0.1 docs p.1456).
Bundle Download Failures: Symptoms: bundle download stuck at 0% or fails with timeout. Diagnostic steps: (1) Verify the appliance can reach the online depot (dl.broadcom.com, VCF 9.0.1 docs p.1267) and that a valid download token from the Broadcom Support Portal is configured (p.1276). (2) Check the proxy configuration if the appliance sits behind a corporate proxy. (3) Verify DNS resolution of the depot hostname. (4) Check free disk space on the appliance that stores the binaries. (5) For air-gapped environments: use the VCF Download Tool and an offline depot, and verify the downloaded binaries before making them available.
Bundle Apply / Upgrade Failures: Symptoms: the update shows Failed in VCF Operations > Fleet Management > Lifecycle (with the reason and remediation steps). Diagnostic steps: (1) Check the failed sub-task in the update status view, or via the SDDC Manager API: GET /v1/tasks/{id}. (2) Read the LCM logs in /var/log/vmware/vcf/lcm/ (lcm-debug on 9.0) — search for ERROR or EXCEPTION. (3) Common failures: pre-check validation failed (host not in maintenance mode, incompatible version), SSH connectivity lost to ESXi host during upgrade, vCenter upgrade failed (insufficient disk space, service restart timeout). (4) Fix: resolve the specific pre-check failure, then retry the failed update (VCF 9.0.1 docs p.1456).
SDDC Manager Error States: Common error patterns and resolution:
"Host commission failed — cannot reach host via SSH": Verify ESXi host has correct management IP, SSH service is running (esxcli system service list | grep SSH), and no firewall blocks port 22 between SDDC Manager and host.
"Workload domain creation failed — insufficient resources": a standard vSAN cluster requires at least 3 hosts with compatible storage (4 for the high-availability model with vSAN OSA at FTT=1; VCF 9.0.1 docs p.1663, p.268). Verify all hosts have correct disk configuration, no existing VMFS partitions on vSAN-designated disks, and hosts are in the SDDC Manager inventory with UNASSIGNED status.
"Upgrade pre-check failed — compatibility issue": the precheck validates component version compatibility. If a component is at an unexpected version (manual upgrade outside VCF lifecycle), the check fails. Fix: compare component versions in the VCF Operations > Fleet Management > Lifecycle component inventory, then remediate per the relevant KB article.
LCM Retry and Rollback: Most LCM tasks support retry after failure remediation. For ESXi rolling upgrades, if one host fails, the remaining hosts are untouched — fix the failed host and retry. For vCenter upgrade failure: a vCenter Reduced Downtime Upgrade rolls back automatically; otherwise restore from the file-based backup taken before the upgrade (VCF 9.0.1 docs p.1416). For NSX upgrade failure: check NSX Manager cluster health, restore individual node if needed.
T3 — Troubleshoot VCF Operations Issues (official Objective 4.3, VCF: Operations)
VCF Operations Adapter Troubleshooting: Adapters collect metrics from managed infrastructure. Common failures:
Adapter Collection Failure: Symptoms: metrics stop updating for specific objects (vCenter, NSX, vSAN). Dashboard shows stale data. Diagnostic steps: (1) Check adapter status in VCF Operations UI → Administration → Solutions → adapter instance → check connection status. (2) Verify credentials — if vCenter password changed, adapter loses connectivity. Fix: update credentials in adapter configuration. (3) Test API connectivity from VCF Operations VM to target: curl -k https://vcenter.lab.local/rest/com/vmware/cis/session. (4) Check VCF Operations logs: /var/log/vmware/vcf-operations/collector/. (5) Restart adapter: Administration → Solutions → select adapter → Manage → Restart.
Alert Configuration Failures: Symptoms: alerts not firing despite threshold breaches, or false-positive alerts flooding notification channels. Diagnostic steps: (1) Verify alert definition: correct metric, correct threshold, correct comparison operator. Common mistake: setting "greater than 80" when metric reports as decimal (0.80 vs 80). (2) Check alert scope — is it applied to the correct object type (VM, host, cluster)? (3) Verify notification channel: test email/webhook connectivity. Common failure: SMTP relay blocks VCF Operations IP. (4) Check alert suppression rules — an overly broad suppression may silence legitimate alerts. (5) For false positives: adjust threshold or add hysteresis (sustained condition duration before firing).
Metric Collection Gaps: Symptoms: gaps in metric graphs, "no data" for specific time periods. Causes: VCF Operations maintenance/restart during collection window, network connectivity interruption to monitored infrastructure, resource exhaustion on VCF Operations node (CPU/disk). Fix: verify VCF Operations node health, check disk space (metric storage can fill up), verify collection interval settings.
Troubleshoot Operations — Log Analysis: VCF Operations for Logs (formerly vRealize Log Insight / Aria Operations for Logs) centralizes syslog from all VCF components. Troubleshooting steps: (1) Verify syslog forwarding from ESXi hosts: esxcli system syslog config get. (2) Check log ingestion rate — if rate exceeds node capacity, logs are dropped. Scale with additional nodes. (3) Use structured queries to correlate events: filter by timestamp + hostname + severity to isolate incidents. (4) Create log-based alerts for critical patterns: "PSOD", "vSAN object lost", "NSX controller disconnected".
T4 — Troubleshoot VCF Automation Issues (official Objective 4.4, VCF: Consume and Automate)
Deployment Failures: Symptoms: cloud template deployment fails or hangs in "CREATE_IN_PROGRESS" state. Diagnostic steps: (1) Check deployment details in VCF Automation UI → Deployments → select failed deployment → History tab → expand failed step. (2) Common failure: "No matching placement found" — the constraint tags in the cloud template don't match any cloud zone capability tags. Fix: verify cloud zone tags match template constraints. (3) "Resource quota exceeded" — project has reached CPU/memory/storage limit. Fix: increase quota or remove unused deployments. (4) "Network provisioning failed" — on-demand NSX network creation failed. Check NSX cloud account connectivity and network profile IP range availability. (5) Check extensibility action logs if ABX actions are configured — custom code failures block deployment pipeline.
Template Errors: Cloud template (YAML) errors are caught at design time or deployment time.
Design-time errors: Syntax validation in Cloud Assembly canvas. Common issues: incorrect indentation (YAML is whitespace-sensitive), invalid resource type reference, missing required property (e.g., image or flavor not specified), constraint tag syntax error.
Deployment-time errors: Template validates but fails during provisioning. Common issues: flavor mapping doesn't exist in target cloud zone (e.g., "small" flavor not defined), image mapping references non-existent template/OVA, network profile has no available IP addresses in the range, storage profile references non-existent vSAN policy.
Troubleshoot Automation — Integration Failures:
vCenter Cloud Account: "Failed to validate cloud account" — verify vCenter API endpoint URL, service account credentials, and network connectivity from VCF Automation appliance to vCenter (port 443). Check if vCenter certificate has changed (re-accept certificate in cloud account config).
NSX Cloud Account: "NSX integration failed" — verify NSX Manager VIP is reachable, credentials are valid, and NSX Manager version is compatible with VCF Automation version. Check if NSX Manager certificate chain is trusted.
Active Directory Integration: "User sync failed" — verify LDAP connectivity (port 389/636), bind DN credentials, base DN configuration. Test with ldapsearch command from VCF Automation appliance.
Custom Form Rendering: "Form not loading" — verify custom form JSON schema is valid, all referenced fields exist in the cloud template inputs section, and conditional visibility rules have correct syntax.
Troubleshoot Automation — Performance: Slow deployments often caused by: (1) VCF Automation database growth — PostgreSQL vacuum and index maintenance needed. (2) Large number of concurrent deployments exceeding appliance capacity. (3) Extensibility actions with external API calls timing out. (4) Event subscription backlog — check event broker queue depth.
Key Takeaways
- T1 (official 2.4): esxtop 'n' view for network troubleshooting — watch %DRPTX/%DRPRX (drops), MbTX/MbRX (throughput), USED-BY (VM-to-pNIC mapping). vMotion failures: check VMkernel adapter, MTU consistency, port 8000, EVC mode.
- T2 (official 4.2): VCF 9.0 lifecycle troubleshooting — upgrades and prechecks run from VCF Operations > Fleet Management > Lifecycle (the SDDC Manager LCM API is removed); logs at /var/log/vmware/vcf/lcm/ (lcm-debug), download failures (dl.broadcom.com reachability, download token, proxy, disk), upgrade failures (failed sub-task, precheck remediation, vCenter RDU rollback or file-based backup), then retry the update.
- T3 (official 4.3): VCF Operations troubleshooting — adapter collection failures (credentials, API connectivity, restart adapter), alert misfire (threshold units, scope, notification channel), metric gaps (disk space, node health, collection interval).
- T4 (official 4.4): VCF Automation troubleshooting — deployment failures (placement mismatch, quota exceeded, network provisioning), template errors (YAML syntax, missing flavor/image mapping, IP range exhaustion), integration failures (cloud account validation, certificate trust, LDAP connectivity).
- Cross-cutting: Always correlate timestamps across SDDC Manager tasks, vCenter events, NSX audit log, and VCF Operations alerts to build a unified incident timeline.
Exam Mapping: 2V0-17.25 — VCP-VCF 9.0 Administrator
- 2.1 Private Cloud Vision — VCF architecture, Instance/Fleet/PC hierarchy, management vs workload domains
- 2.2 Compute Fundamentals — host commissioning, vSphere clusters, VMs, DRS/HA, Content Libraries, vTPM/encryption
- 2.3 Storage Fundamentals — vSphere storage, vSAN ESA vs OSA, storage policies, FTT/RAID, resilience, fault domains
- 2.4 Network Fundamentals — NSX Tier-0/Tier-1, segments, DFW microsegmentation, TEPs, BGP/OSPF, networking services
- 4.1 Deploy & Configure — VCF Installer, bring-up workflow, management domain, VCF Operations, Private Cloud provisioning
- 4.2 Manage — Fleet management, identity/RBAC, license management, certificate rotation, password management
- 4.3 Operate — VCF Operations (dashboards, alerts, views, reports, costing, policies, compliance, Service Discovery, vSAN Ops, Ops for Logs)
- 4.4 Consume & Automate — VCF Automation (Cloud Assembly, Service Broker, Orchestrator), regions, multi-tenancy, provider networking, cloud templates
Labs in This Section
📝 Quiz — VCF 9.0 Administrator
Section 1 — VCF Architecture and Components
- SDDC Manager
- VCF Operations Console
- VCF Installer
- Aria Automation
- 8 hosts
- 3 hosts
- 4 hosts
- 6 hosts
- Workload Domain → Instance → Fleet → Private Cloud
- Instance → Fleet → Private Cloud → Workload Domain
- Fleet → Instance → Workload Domain → Private Cloud
- Private Cloud → Fleet → Instance → Workload Domain
- VCF Operations Console
- NSX Manager
- SDDC Manager
- VCF Automation
- VCF Installer appliance
- SDDC Manager
- Aria Suite Lifecycle 9.0, upgraded in place
- VCF Operations fleet management appliance
Section 2 — vSphere, vSAN, and NSX Administration
Section 3 — Planning and Design
Section 4 — Deploy, Configure, and Operate VCF
Section 5 — Troubleshooting
🃏 Flashcards — VCF 9.0 Administrator
References
- VCF 9.0 documentationTier 1 — Official
- vSphere 9.0 documentation (ESX 9.0 and vCenter 9.0)Tier 1 — Official
- vSAN 9.0 documentationTier 1 — Official
- vSphere Replication 9.0Tier 1 — Official
- VMware Live Site Recovery 9.0 (formerly Site Recovery Manager)Tier 1 — Official
- VCP-VCF Administrator certification (Broadcom certification page)Tier 1 — Official
- VCF 9.0 Design Library — VCF Edge Options and PatternsTier 1 — Official
- VCF Edge Pattern 5 — Dark Site EdgeTier 1 — Official
- VCF Edge Pattern 8 — Single Host vSphere Supervisor at the EdgeTier 1 — Official
- VCF Edge Pattern 3 — Locally Managed EdgeTier 1 — Official
- VCF Edge Models (platform requirements, Remote Clusters rename)Tier 1 — Official
- VCF 9.0 Deployment, Convergence, and UpgradeTier 1 — Official
- VCF 9.0 Fleet Management (certificates, passwords, identity)Tier 1 — Official
- VCF 9.0 Lifecycle ManagementTier 1 — Official
- VCF 9.0 Infrastructure OperationsTier 1 — Official
- VCF 9.0 Security and ComplianceTier 1 — Official
- VCF 9.0 LicensingTier 1 — Official
- NSX in VCF 9.0Tier 1 — Official
- vSAN in VCF 9.0Tier 1 — Official
- vSphere in VCF 9.0Tier 1 — Official