Academy/vSphere Foundation 9.0 Administrator (2V0-16.25)
VCF

vSphere Foundation 9.0 Administrator (2V0-16.25)

VCF 9.0vcp-foundation

vSphere Foundation 9.0 Administrator (2V0-16.25). 60-item exam, 135 minutes, passing score 300 (scaled). Validates ability to deploy, configure, and manage VVF-based solutions supporting both Supervisor-based and VM workloads. Components: vSphere (vCenter Standard, ESX, vSphere Supervisor), vSAN, VCF Operations, and VCF Operations for Logs.

2V0-16.25
VCP
60
Questions
135m
Duration
300 (scaled)
Pass Score
52
Objectives

Exam Blueprint Weights

Section titles, groupings and weights below are VCDX Academy study groupings, NOT the official Broadcom blueprint structure. Broadcom publishes no section weights. Always cross-check the official exam guide. Official exam guide ↗
Section 1 — Architecture and Technologies
~12%
Section 2 — vSphere Configuration and Management
~20%
Section 3 — Storage Management
~18%
Section 4 — Networking
~15%
Section 5 — Operations and Troubleshooting
~35%High Weight

Version Evolution

vSphere Foundation (VVF) is the entry-level VCF tier. VVF Admin covers core vSphere administration without SDDC Manager, NSX advanced features, or vSAN enterprise features. Understanding VVF scope is important for VCDX candidates to articulate the value proposition of full VCF vs VVF-only deployments.

Learning Outcomes

  • Deploy, configure, and manage vSphere Foundation 9.0 environments
  • Obj 2.1: Describe virtualization principles, use cases, and value proposition
  • Obj 2.2: Deploy/configure VVF compute (vCenter, ESX, clusters, VMs, Content Libraries, encryption)
  • Obj 2.3: Configure vSphere storage, deploy vSAN (ESA/OSA), configure storage policies and resilience
  • Obj 2.4: Differentiate VVF networking components (vDS, vSS, port groups)
  • Obj 4.1: Identify VVF deployment components, describe deployment process, configure Supervisor
  • Obj 4.2: Configure identity/RBAC, license management, certificate management, lifecycle management
  • Obj 4.3: Deploy and operate VCF Operations and VCF Operations for Logs — dashboards, alerts, views, policies, costing, compliance, Service Discovery, vSAN Storage Operations
  • Obj 4.4: Deploy Supervisor-based Services, VM Service VMs, VKS workloads, vSphere Pods, VCF Operations Orchestrator
  • Configure VCF Operations Alert, Capacity, Automation, and Compliance policies for automated operational governance
  • Use the Explore Logs feature to search, filter, query, and create dashboards from log data in VCF Operations for Logs
  • Explain vSphere Pods (CRX micro-VMs on ESX), why NSX networking is the documented baseline for them, and where the VCF 9.0 docs conflict for a VDS-networked Supervisor with a load balancer, and deploy VM Service VMs and VKS clusters on a VDS-networked VVF Supervisor
  • Manage VMCA certificate lifecycle including replacement scenarios, VECS store operations, and enterprise CA integration
  • Configure identity sources (Active Directory over LDAPS, OpenLDAP, identity federation via SAML/OIDC — IWA removed in vCenter 9.0) and implement RBAC with proper role and permission assignments in vCenter

VVF Architecture Overview#

VVF Definition:

vSphere Foundation (VVF) 9.0 is Broadcom's enterprise workload platform and the core of VCF: vSphere 9.0 (ESX and vCenter), vSAN 9.0, vSphere Kubernetes Service (VKS, the Supervisor-based Kubernetes runtime for VMs and containers side by side), VCF Operations and VCF Operations for Logs. Building a VVF platform starts by deploying VCF Operations (VCF 9.0.1 — Getting Started with vSphere Foundation). What VVF does not include is the cloud-management and integrated-automation layer of VCF: NSX, VCF Automation, SDDC Manager / the VCF Installer's instance and domain model, and the fleet-level workflows (VCF 9.0.1 — What Is vSphere Foundation?).

VVF vs VCF:

VCF adds NSX (overlay networking, distributed firewall, gateways, VPCs), VCF Automation (the successor to Aria Automation — VCF Operations Orchestrator is a separate component, formerly Aria Orchestrator) and the VCF Instance/domain model operated through VCF Operations fleet management. VVF keeps vSphere, vSAN, VKS, VCF Operations and VCF Operations for Logs, with vDS networking and external or Foundation load balancing for the Supervisor.

VVF Component Stack

  • vSphere 9.0 (vCenter + ESXi):
  • Management plane (vCenter Server Appliance 9.0) and compute hosts (ESX 9.0 minimum)
  • vSAN 9.0:

Converged storage; ESA compresses by default through the vSAN storage policy and has no deduplication in 9.0 ("Deduplication is not available in the vSAN ESA cluster"); OSA offers deduplication and compression; native replication, witness nodes for 2-node clusters

vSphere Kubernetes Service (VKS):

Kubernetes on ESXi clusters via vSphere Supervisor control plane

vSphere Lifecycle Manager (vLCM):

Image-based ESXi management, firmware/driver updates, desired state tracking

No NSX:

Traditional vSphere networking (vDS/vSS) only; no Geneve, no micro-segmentation, no advanced routing

Licensing (VCF 9.0 What's New — Licensing)

vSphere Foundation is a per-core subscription (every CPU counted as at least 16 cores) following the VCF pattern of two licenses — cores and vSAN TiB — imported as one license file into VCF Operations and assigned to vCenter instances; there are no Standard/Advanced/Enterprise tiers of vSphere Foundation in 9.0. The separate vSphere Standard and vSphere Enterprise Plus editions are hypervisor-only products outside the VVF scope.

Typical Deployment Architecture

┌─────────────────────────────────────────────────────────┐
│                   vCenter Server (VCSA 9.0)             │
│  (Tiny: 2vCPU/14GB | Small: 4vCPU/21GB | Med: 8/30GB)   │
└──────────────────┬──────────────────────────────────────┘
                   │
        ┌──────────┼──────────┐
        │          │          │
    ┌───▼──┐   ┌──▼───┐   ┌──▼───┐
    │ESXi-1│   │ESXi-2│   │ESXi-3│  (min. 3 nodes for vSAN quorum)
    └───┬──┘   └──┬───┘   └──┬───┘
        │         │          │
    ┌───▼─────────▼──────────▼───┐
    │   vSAN Cluster             │
    │  (RAID-1 or Erasure Code)  │
    └────────────────────────────┘

Key Takeaways

  • For exam: know the vSAN CMMDS host roles (leader, backup, agent) and how a 2-node cluster keeps quorum with a witness host at a third location holding witness components; the witness never stores VM data.

vSphere Core Administration#

vCenter Server Appliance (VCSA) Sizing & Deployment

SizevCPURAMScale target
Tiny214 GBup to 10 hosts / 100 VMs
Small421 GBup to 100 hosts / 1,000 VMs
Medium830 GBup to 400 hosts / 4,000 VMs
Large1639 GBup to 1,000 hosts / 10,000 VMs
X-Large2458 GBup to 2,000 hosts / 35,000 VMs

(vCenter deployment sizes as published in the vCenter installation documentation; storage size depends on the storage option chosen — Default, Large or X-Large — so check the vCenter 9.0 installation guide for the current disk figures.)

vCenter availability:
vCenter HA is a three-node active/passive/witness cluster and is still part of vCenter 9.0 (the 9.0 reduced-downtime upgrade integrates with vCenter HA deployments, VCF 9.0.1 docs p.80). It is unrelated to Enhanced Linked Mode, which is deprecated in vCenter 9.0 (p.226). Most VVF designs run a single vCenter protected by vSphere HA with high restart priority plus scheduled file-based backup and restore.

ESXi Installation & Configuration

ESX 9.0 installation options: interactive (ISO), scripted (kickstart), or network boot with vSphere Auto Deploy (Auto Deploy is still part of 9.0 — see its known issues, VCF 9.0.1 docs p.390)

Boot device: a local or SAN boot device on the Broadcom Compatibility Guide

BIOS/UEFI: virtualization extensions (VT-x/AMD-V), AES-NI for encryption performance, UEFI Secure Boot, VT-d where SR-IOV or DirectPath I/O is used

Licensing:

Licenses are managed in VCF Operations (connected to the VCF Business Services console at vcf.broadcom.com, or in disconnected mode): import the single license file, assign the license to vCenter instances, and every host and component connected to that vCenter is licensed from the assignment. vSphere Foundation follows the VCF pattern of two licenses — cores and vSAN TiB. License usage must be submitted from VCF Operations every 180 days or hosts disconnect from vCenter. Nothing is bound to hardware serial numbers and there is no Standard/Advanced/Enterprise ladder in 9.0 (VCF 9.0 What's New — Licensing).

Networking: vDS vs vSS

Storage: VMFS, NFS, vVols

VMFS 5 and VMFS 6 (there is no VMFS 7 or 8):
Used for BLOCK datastores (FC, iSCSI, local SCSI/NVMe) - vSAN does NOT use VMFS at all; it presents its own object-based vsanDatastore. vSphere treats VMFS, NFS, vSAN and vVols as four distinct datastore types. VAAI support (primitives: xcopy, atomic test-set, zero), automatic space reclamation

NFS 4.1:

Session trunking (several server IPs for one mount, i.e. multipathing) and Kerberos authentication; NFS 3 has neither. VAAI-NAS primitives come from the array vendor's plug-in

vVols (Virtual Volumes):

Per-VM storage policies through the array's VASA provider; snapshots and replication offloaded to the array at virtual-disk granularity

vSAN datastore:

One vsanDatastore per vSAN cluster, presented to every host in the cluster; capacity and placement are governed by storage policies (SPBM)

VM Management & Templates

Content Libraries:

Local libraries can be published; subscribed libraries synchronise from a published library (immediately or on demand). Items: OVF/OVA and VM templates, ISO images, scripts and other files.

VM Templates:

Clone from template and apply a guest customization specification (Sysprep for Windows, the Linux customization engine or cloud-init for Linux)

vSphere Configuration Profiles (Host Profiles are deprecated in vCenter 9.0)

Configuration Profiles: cluster-level desired-state host configuration (a JSON document)

Use case: consistent NTP, DNS, syslog and security settings on every host in the cluster

vCenter UI → Cluster → Configure → Desired State → Configuration

→ Create the draft from a reference host, or Draft → Import a JSON document (VCF 9.0.1 docs p.248)

→ Check compliance (Configuration → Compliance)

→ Remediate non-compliant hosts

Host Profiles still run in vCenter 9.0 but are deprecated and will be removed; Configuration Profiles manage configuration at cluster level instead (p.226). Note: 'Profile-Driven Storage' is the old name for storage policies (SPBM), not Host Profiles.

Distributed Virtual Switch (vDS) — Production Recommended

Centralized management:

One switch definition in vCenter, pushed to every member host; a 9.0 vCenter creates current-version switches

Port groups:

Distributed port groups carry a VLAN (802.1Q), trunk or private VLAN setting; VMkernel adapters on them carry the services (management, vMotion, vSAN, FT)

NIC Teaming:

Route Based on Originating Virtual Port:

Default on vSS and vDS; pins each VM port to one uplink; simple, but uplinks can be unevenly loaded

Route Based on Physical NIC Load (vDS only):

Load-based teaming; moves ports when an uplink passes 75% utilisation; the usual choice for VM and vMotion port groups

Explicit Failover Order:

Active/standby uplinks; the usual choice for Management and vSAN

Route Based on IP Hash:

Needs a static port channel (EtherChannel) on the physical switch with one port per team uplink; usable on vSS and vDS (VCF 9.0.1 docs p.1619–1620). The VCF 9.0 distributed-switch models list it as a load-balancing option (p.988), but the fabric design supports only LACP-based link aggregation to the host, treats that as not recommended, and does not support static/EtherChannel aggregation (p.1105)

LACP (vDS only):

Configured as a LAG on the vDS; when the LAG is the only active uplink its load-balancing mode overrides the port group policy (VCF 9.0.1 docs p.1627). VCF design treats link aggregation to the host as supported but not recommended (p.1105)

vSAN Network Isolation:

Dedicated VLAN and port group for vSAN; one consistent MTU end to end (9000 recommended where the physical network supports it)

vMotion Optimization:

Separate port group and the dedicated vMotion TCP/IP stack; jumbo frames help large migrations where the network supports them

🔬 Lab: Deploy vDS & Configure NIC Teaming

Create a new vDS at the current version: vCenter UI → Networking → New Distributed Switch

Add all ESXi hosts to vDS (1-pass migration: create VM port group, migrate management vmk, then data vmks)

Create port groups: Management, vMotion (TCP/IP Stack), vSAN (VLAN 100, MTU 9000)

Set teaming per port group: Route based on physical NIC load for VM and vMotion; explicit failover order (uplink1 active, uplink2 standby) for Management and vSAN

Verify in vSphere Client → vDS → Configure → Topology and Health Check: both uplinks up, VLAN and MTU health checks pass

Test: vmkping -I <vsan vmk> -d -s 8972 <peer vSAN IP> (-I takes the vmk interface name; should succeed with under 1 ms RTT between hosts in a single-site cluster)

Standard vSwitch (vSS) — Legacy/Edge Only

Host-local only; no policy replication

Teaming: originating virtual port, source MAC hash, IP hash (static EtherChannel), explicit failover order; no load-based teaming and no LACP

No LACP support; no central management

Used for single-host labs or edge deployments

Key Takeaways

  • For exam: VCSA size follows host and VM counts (Tiny up to 10 hosts / 100 VMs, Small up to 100 hosts / 1,000 VMs — see the table). Know the sizing table by heart for capacity planning questions.
  • For exam: vDS is enterprise standard; standard vSwitch for legacy/edge only. Know NIC teaming modes and LACP configuration for advanced networking questions.
  • For exam: vSphere supports VMFS5 and VMFS6 only - there is no VMFS 7 or 8, and vSAN does not use VMFS (it is an object store, vsanDatastore). VMFS is for block LUNs; NFS for file-based datastores. Understand VAAI primitives (xcopy, atomic test-set) and when to use each.

vSAN in VVF Context#

vSAN 9.0 Architecture: Standalone (No VCF Orchestration)

vSAN in VVF is deployed and managed directly via vCenter (no SDDC Manager). Quorum and resilience handled automatically via intelligent placement.

Cluster Topologies

3-Node Cluster:

Native quorum (2-of-3 majority). No witness required. Tolerates 1 host failure.

2-Node Cluster + Witness:

A vSAN witness appliance (a preconfigured ESX VM deployed from an OVA) runs outside the cluster, typically at a third location, and holds only witness components for quorum. Sizes: Tiny (up to 750 components, 10 VMs or fewer; not supported with ESA), Medium (up to 21,833 components, 500 VMs), Large (up to 45,000 components) — VCF 9.0.1 docs p.1699.

Stretched Cluster (Multi-Site):

Data sites A and B with a witness at site C; synchronous writes give RPO 0 for a site failure. Recovery after a site failure is a vSphere HA restart, so RTO depends on how long the workloads take to restart.

Single host:

Below the vSAN minimum (three hosts, or two hosts plus a witness); no failure tolerance, so not a design option.

vSAN Disk Groups & Capacity

Disk group: 1 cache tier (SSD) + N capacity tier (HDD or SSD)

vSAN 9.0: EXPRESS Storage Architecture (ESA) standard [ESA = Express, not Elastic]

- Compression is INLINE and always on. Deduplication is cluster-wide and post-process,

but arrived only in VCF 9.0 P01 (limited) and went GA in VCF 9.1 - vSAN 8 ESA has compression only.

- ESA is NVMe-flash ONLY: at least one NVMe TLC device per storage pool.

SAS/SATA devices and RAID/tri-mode controllers are NOT supported. There is NO HDD support.

Only OSA (Original Storage Architecture, disk groups) can use magnetic media, in hybrid mode.

OSA disk group (hybrid): cache SAS/SATA SSD or PCIe flash + capacity 7.2K SAS/NL-SAS HDD [hybrid OSA deprecated as of the vSAN 9.0 announcement]
ESA storage pool: NVMe TLC only (min 1.6 TB production drives, 4+ devices/host recommended, host RAM >=128 GB)

vSAN File Services (vSAN FSA)

A file-service layer on top of vSAN that serves SMB, NFSv3 and NFSv4.1 shares (VCF 9.0.1 docs p.1645):

Use case:

Shared file storage for VMs and Kubernetes ReadWriteMany volumes, home directories

Deployment:

Enable File Service on the cluster; give it a pool of static IP addresses from one subnet (ideally one per host); SMB and Kerberos NFS shares need Active Directory details

Protection:

Share data is stored as vSAN objects, so the share's storage policy (FTT) protects it like any other object

vSAN Encryption

Data-at-rest encryption:

Cluster-wide, needs a key provider — the vCenter Native Key Provider or an external KMS; vCenter gets the key IDs and hosts talk to the KMS directly (VCF 9.0.1 docs p.1612). Separate from per-VM encryption, which is a VM storage policy.

Data-in-transit encryption:

vSAN encrypts all data and metadata traffic between hosts in the cluster when enabled (p.1652). Enable under Cluster → Configure → vSAN → Services → Data-In-Transit Encryption → Edit, then choose a rekey interval; AES-256, forward secrecy, no key provider needed (pp.1778-1779).

Performance impact:

CPU cost depends on the platform (AES-NI); measure it in the target environment rather than assume a figure

Deduplication & Compression (ESA)

vSAN Express Storage Architecture (ESA) deduplication is cluster-wide and

post-process and asynchronous

(note: ESA dedup is NOT in vSAN 8 - limited availability in VCF 9.0 P01, GA in VCF 9.1. OSA dedup is the opposite: inline at destage, scoped to a single disk group):

Savings:

Depend entirely on the data; measure with the space-efficiency views rather than plan on a fixed ratio

Trade-off:

Post-process deduplication uses CPU and I/O in the background; verify workload performance in a lab before enabling it in production

vSAN Performance Service

vSAN Performance Service: collects and charts performance statistics (VCF 9.0.1 docs p.1812)

Turned on per cluster (Configure → vSAN → Services → Performance service)

  • Metrics: IOPS, throughput, latency, congestion, outstanding I/O
  • Views: cluster, host, disk group/storage pool, disk, VM and virtual disk
  • Where: Cluster → Monitor → vSAN → Performance

vSAN Resilience & FTT (Fault Tolerance Threshold)

FTT=0:
No replication (not recommended production)
FTT=1 (RAID-1):
2-way mirror, tolerate 1 host/disk failure. Space overhead = 2x
FTT=2 (RAID-6):

Erasure code (4+2 stripe, NOT 6+2), tolerate 2 failures. Space overhead = 1.5x, minimum 6 hosts (7 recommended)

FTT=3:

Rarely used; RAID-1 mirroring only, space overhead 4x, minimum 7 hosts
RAID overhead reference (verified): RAID-1 FTT=1 = 2.0x (3 hosts); RAID-1 FTT=2 = 3.0x (5 hosts); OSA RAID-5 3+1 FTT=1 = 1.33x (4 hosts); ESA RAID-5 is ADAPTIVE - 2+1 = 1.5x below 6 hosts (3 host min), 4+1 = 1.25x at 6+ hosts (5 host min), re-evaluated 24h after a host-count change; RAID-6 4+2 FTT=2 = 1.5x (6 hosts min, 7 recommended). VCF 9.1 Auto-RAID retires the 4+1 scheme: RAID-5 is always 2+1 at 3-5 hosts, RAID-6 4+2 at 6+.

Key Takeaways

  • Exam question tip: FTT=1 needs 3 hosts (RAID-1) or 4 hosts (OSA RAID-5; ESA builds RAID-5 as 2+1 from 3 hosts and 4+1 from 6). FTT=2 needs 5 hosts (RAID-1) or 6 hosts (RAID-6) — a 4-node cluster cannot provide FTT=2.

vSphere Lifecycle Manager (vLCM)#

vLCM Overview: Image-Based vs Baseline (Legacy)

vLCM (v9.0 recommended):
Single ESX image (base image, vendor add-on, firmware/driver add-on, components) applied to the cluster as desired state.

Baselines (removed in vCenter 9.0):

Baseline and baseline-group management (the legacy VUM method) is no longer supported in vCenter 9.0; every cluster is image-managed and clusters still on baselines must be converted before the ESX 9.0 upgrade.

Image-based:

Atomic replace of entire ESXi installation (clean, reproducible, rollback easier)

Cluster Image Composition

Cluster image = ESXi base + OEM customization image (HW drivers/firmware)

Workflow: Download from VMware, apply OEM drivers, validate, deploy to cluster

  1. vSphere Client → Cluster → Updates (vSphere Lifecycle Manager)
  2. Create cluster image: Select ESX 9.0 ISO + OEM image (Dell, HP, Lenovo)
  3. Attach image to cluster (desired state)
  4. Preview mode (dry-run) recommended before remediate
  5. Remediate cluster: Hosts updated in rolling fashion (HA maintains uptime)

Hardware Compatibility & VCG (VMware Compatibility Guide)

Before image deployment, verify:

Hardware certified in VMware Compatibility Guide (VCG) for ESX 9.0

OEM image includes certified driver versions

Firmware versions match OEM recommendations (e.g., Dell iDRAC, Broadcom HBA)

vLCM with NSX (N/A in VVF)

Note: NSX Edge node images also managed via vLCM in VCF. VVF does not include NSX.

Firmware Updates via vLCM

Firmware updates (e.g., BIOS, iLO, SSD) managed through OEM image

vLCM integrates with hardware vendor Lifecycle Management platforms

OEM Examples:

  • Dell: iDRAC (iLO for HP, RedFish API for modern servers)
  • Firmware bundle downloaded via OEM portal, included in OEM customization image
  • vLCM applies automatically on cluster remediation

Key Takeaways

  • For exam: vLCM images are the only lifecycle method in vCenter 9.0 (baselines removed); updates are atomic image remediations. Know the cluster image composition (ESXi base + OEM image) and remediation workflow.
  • For exam: Preview mode is essential before cluster remediation to validate compatibility. Always check VCG for hardware certification before deploying OEM images.
  • For exam: Firmware updates managed through OEM customization image (Dell iDRAC, HP iLO). vLCM integrates with OEM platforms for automated firmware delivery.

Monitoring & Operations#

vSphere Alarms & Events

Events:

Historical log of configuration/runtime changes (powered on VM, host connection lost, etc.)

Alarms:

Triggered on event conditions; actions configurable (email, SNMP, scripts)

Custom alarms:

vCenter UI → Alarms → Define custom triggers (e.g., CPU >80%, memory <10%)

Performance Charts

vCenter UI → VM/Cluster → Performance tab provides real-time and historical graphs:

CPU:

Used%, Ready%, Co-stop%, Overlap%, Guest % (useful for identifying scheduling contention)

Memory:

Used, Shared, Ballooned, Swapped (swapped = bad; indicates overallocation)

Disk (IOPS/Latency):

Read/Write latency <5ms ideal, >20ms = storage contention

Network:

Throughput Mbps, Packets dropped (indicates physical NIC saturation or vNIC issues)

vSAN Health Check

Automated diagnostic suite; run manually or on schedule:

vSAN Health Check categories:

- Cluster: Quorum, unicast agent reachability

- Storage: Disk claims, controller mode, encryption certs

- Network: vSAN vmk connectivity, MTU consistency (9000 recommended); design target less than 1 ms RTT between hosts (VCF 9.0.1 docs p.1608)

- Limits: Max objects, max hosts (9.0 = 64 hosts max per cluster)

- vSAN FSA (if enabled): Namespace health, share accessibility

Access: vCenter UI → Cluster → vSAN → Health

VCF Operations Diagnostics (replaces Skyline Advisor and Skyline Health Diagnostics in 9.0)

Capability:

Diagnostics Findings — a consolidated view of known product issues, VMSA-based security exposures and best-practice recommendations across the stack, with root-cause insight and remediation steps; parity with the former Skyline signatures; the Findings Catalog lists every signature; findings export to CSV

Support:

Log Assist gathers and uploads support bundles to Broadcom Support from VCF Operations

Setup:

VCF Operations → Diagnostics (connected mode keeps the signature catalog current). vSAN Skyline Health remains in the vSphere Client under Cluster → Monitor → vSAN → Skyline Health

vSphere HA and Proactive HA

vSphere HA:
Detects host failure and isolation through network heartbeats, datastore heartbeats and isolation addresses (ICMP); a host that loses all of them treats itself as isolated and applies the configured isolation response.

VM restart priority:

Five levels — Lowest, Low, Medium, High, Highest. The next priority group starts when the configured condition is met (resources allocated, VMs powered on, guest heartbeats or app heartbeats detected), plus an optional additional delay; VM-to-VM dependency rules give finer ordering. A sixth setting, Disabled, turns HA restart off for the VM (vSphere 9.0 Availability — Respond to Host Failure; vSphere 9.0 API reference ClusterDasVmSettingsRestartPriority / ClusterVmReadinessReadyCondition).

Proactive HA (separate feature):

Uses hardware vendor health providers to move VMs off a degraded host (quarantine or maintenance mode). With vSAN, choose maintenance mode for all failures (VCF 9.0.1 docs p.1690).

Configuration:

vCenter UI → Cluster → Configure → vSphere Availability → Edit (restart priority, isolation response, Proactive HA)

Routine operational checks

  • Host versions: every host in a cluster on the same ESX build (vLCM image compliance)
  • VM snapshots: report long-running snapshots (VCF Operations or a script)
  • Storage latency: watch DAVG/KAVG/GAVG in esxtop or the performance charts
  • vMotion network: dedicated port group and TCP/IP stack

References

📄 VCF Operations Diagnostics (replaces Skyline Advisor in 9.0)
📄 vSAN Skyline Health (VCF 9.0.1 docs p.1809)

Key Takeaways

  • For exam: Understand Performance Chart metrics—CPU Ready%, Memory Swapped, Disk latency >20ms = problem. These indicators critical for troubleshooting workload performance.
  • For exam: vSAN Health Check run before major operations. Categories: Cluster (quorum), Storage (disk claims), Network (vmk connectivity, MTU consistency; less than 1 ms RTT between hosts), Limits (64 hosts max).
  • For exam: VCF Operations Diagnostics Findings (the 9.0 successor to Skyline Advisor and Skyline Health Diagnostics) flags known issues, VMSA exposures and best-practice risks. HA isolation addresses test via ICMP; VM restart priority (five levels, higher priority restarts first: Highest → High → Medium → Low → Lowest) plus 'start next priority' conditions order VM restarts; Proactive HA is a separate, hardware-health-driven feature.

VVF vs VCF — Precise Positioning (Admin Track)#

VVF vs VCF — Precise Positioning (Admin Track, VCF 9.0 generation)
VMware vSphere Foundation (VVF) 9.0 is the smaller-data-centre offering next to VMware Cloud Foundation (VCF) 9.0: vSphere with vCenter, vSAN capacity and VCF Operations, without the SDDC Manager-driven VCF Instance, NSX and VCF Automation. The 2V0-16.25 exam (VVF 9.0 Administrator) is largely about operating VVF through VCF Operations (Objective 4.3: dashboards, views, reports, capacity, cost and compliance), so the component boundary below matters.

VVF 9.0 Component Bundle

VVF 9.0 includes:


  1. vSphere 9.0: ESX 9.0 hosts and vCenter Server Standard 9.0 (vSphere HA, DRS, vMotion, Storage vMotion, Lifecycle Manager images, vTPM, Secure Boot, VM encryption)
  2. vSphere Supervisor and vSphere Kubernetes Service (VKS) on vSphere networking (vDS) with an external load balancer; no NSX
  3. vSAN 9.0 with a per-core capacity entitlement (ESA or OSA); more capacity is a per-TiB add-on
  4. VCF Operations for VVF: monitoring, capacity, cost, compliance, dashboards, views, reports, alerts
  5. VCF Operations for Logs for VVF: deployed from the .ova with a VVF licence (VCF 9.0.1 docs: 'If you have a VMware vSphere Foundation (VVF) license, you deploy VCF Operations for logs virtual appliance from an .ova file'), feeding audit events and log analytics into VCF Operations

VVF 9.0 does NOT include:


  1. NSX (overlay networking, distributed firewall, Tier-0/Tier-1 gateways, NSX load balancing)
  2. VCF Automation (cloud templates, service broker, All Apps organizations)
  3. SDDC Manager, the VCF Installer bring-up and VCF Instances or workload domains; no VCF Operations fleet management workflows
  4. VCF Operations for Networks, vDefend, Avi Load Balancer, HCX
  5. vSAN Max (disaggregated storage); VVF vSAN runs as HCI on the vSphere cluster

VVF 9.0 Stack (Layer Model)

Applications and workloads (VMs, Supervisor namespaces, VKS clusters)

VCF Operations and VCF Operations for Logs (VVF scope: monitoring, capacity, cost, compliance, logs)

vSphere Supervisor / VKS (vDS networking, external load balancer)

  • vSphere 9.0 (ESX 9.0, vCenter Standard, HA, DRS, vMotion, Lifecycle Manager)
  • vSAN 9.0 (ESA or OSA, per-core capacity entitlement)
  • Hardware (servers, NVMe or SSD, 10/25 GbE)

Notable absence: no NSX layer and no SDDC Manager; networking is vDS with physical VLANs and physical firewalls.

VVF vs VCF Detailed Comparison

FeatureVVF 9.0VCF 9.0
Hypervisor and vCenterESX 9.0 and vCenter StandardESX 9.0 and vCenter in every VCF domain
vSANYes, HCI, per-core entitlement plus add-on TiBYes, HCI or vSAN storage clusters, larger per-core entitlement
NSXNoYes (NSX 9.0 overlay, DFW, gateways)
KubernetesSupervisor and VKS on vDS with Foundation Load Balancer or AviSupervisor and VKS with NSX networking (VPCs, NSX LB)
VCF OperationsYes (VVF scope: monitoring, capacity, cost, compliance, logs)Yes (fleet scope: plus fleet management, lifecycle, certificates, passwords, networks)
VCF Operations for LogsYes (.ova deployment with a VVF licence)Yes (deployed by VCF Operations fleet management)
VCF AutomationNoYes
SDDC Manager, VCF Installer, VCF Instances and domainsNoYes
LicensingPer-core subscription (minimum of 16 cores per CPU); vSAN TiB add-onPer-core subscription with a larger vSAN entitlement; add-ons for vDefend, Avi and others

Upgrade Path VVF to VCF

A VVF estate moves to VCF by entitlement and convergence, not by reinstalling vSphere:

  1. Change the subscription to VCF (per-core)
  2. Deploy the VCF Installer and converge the existing vCenter and clusters into a VCF Instance (management domain), which brings SDDC Manager and the fleet management appliance behind VCF Operations
  3. Add NSX to the converged domain (VCF Operations deploys and manages the NSX Manager cluster)
  4. Add VCF Automation for self-service IaaS and All Apps organizations
  5. Import further vCenters as workload domains

Timeline: phased (converge, then NSX, then Automation). Prerequisites: vCenter and ESX versions in the convergence support matrix (see vcf-evolution-03).

Use-Case Decision Framework

Use VVF when:

  • One or a few vSphere clusters without software-defined networking
  • Monitoring, capacity and cost management through VCF Operations is wanted without fleet management
  • Kubernetes through Supervisor and VKS on vDS is enough
  • Network security is delivered by physical firewalls and VLANs
  • Dev/test, remote or branch sites, migrations from perpetual vSphere

Use VCF when:

  • Multiple domains or Instances under one fleet (VCF Operations fleet management)
  • NSX networking and security (overlay, DFW, VPCs), Avi, vDefend
  • Self-service IaaS and tenancy through VCF Automation
  • Standardised lifecycle (SDDC Manager plus VCF Operations) across many clusters
  • Regulated or multi-tenant private cloud

Exam angle (2V0-16.25): the VVF administrator operates vSphere, vSAN and VCF Operations (with VCF Operations for Logs); questions on NSX, VCF Automation or SDDC Manager workflows describe VCF, not VVF.

Key Takeaways

  • For exam: VVF 9.0 = vSphere 9.0 (ESX, vCenter Standard, Supervisor/VKS on vDS) + vSAN (per-core entitlement) + VCF Operations + VCF Operations for Logs. VCF 9.0 adds NSX, VCF Automation, SDDC Manager/VCF Installer, fleet management, vSAN Max and the larger vSAN entitlement.
  • For exam: Know the VVF vs VCF comparison table—what's included/excluded per product. Critical for product positioning and customer advisory scenarios.
  • For exam: VVF to VCF is an entitlement change plus convergence with the VCF Installer, then NSX, then VCF Automation; no vSphere reinstall. Both are per-core subscriptions; VCF carries the larger vSAN entitlement.

Virtualization Fundamentals (Objective 2.1)#

Blueprint Objective 2.1 — Virtualization Fundamentals

Principles of Virtualization

Virtualization abstracts physical hardware into logical resources, enabling multiple operating systems to run concurrently on a single physical server. The hypervisor (ESXi in VMware's case) sits between hardware and guest OS, managing CPU scheduling, memory allocation, I/O, and device access.

Type 1 (Bare-Metal) Hypervisor:

ESXi runs directly on hardware — no host OS. Minimal attack surface (~150MB footprint). Direct hardware access via VMkernel for maximum performance.

Type 2 (Hosted) Hypervisor:

Runs atop a host OS (e.g., VMware Workstation). Higher overhead, used for development/testing only.

Key Abstraction Layers:

├── CPU: Virtual CPUs (vCPUs) scheduled on physical cores via VMkernel scheduler
│   └── Overcommit: More vCPUs than physical cores; scheduler uses time-slicing
├── Memory: Virtual memory mapped to physical via TPS (Transparent Page Sharing), ballooning, compression, swap
│   └── Overcommit: Total VM memory > physical RAM; managed via ballooning driver (vmmemctl)
├── Storage: Virtual disks (VMDKs) on datastores (VMFS, NFS, vSAN, vVols)
│   └── Thin provisioning: Allocate on write, report full size to guest
├── Network: Virtual NICs (vNICs) connected to virtual switches (vSS/vDS)
│   └── SR-IOV: Direct hardware NIC access bypassing hypervisor for latency-sensitive workloads
└── GPU: vGPU passthrough or shared GPU (NVIDIA GRID) for VDI/AI workloads

Use Cases for Virtualization

Server Consolidation:

Reduce physical servers 10:1 or higher. Typical enterprise runs 15-25 VMs per host. Saves power, cooling, rack space, hardware maintenance.

Business Continuity & DR:

vMotion (live migration), HA (automatic restart), SRM (Site Recovery Manager) — workloads survive hardware failures and site disasters without application changes.

Development & Testing:

Rapid provisioning via templates/clones. Snapshots for point-in-time rollback. Linked clones share base disk, reducing storage 70%+.

Cloud-Native Applications:

vSphere Supervisor enables Kubernetes on ESXi. Containers and VMs coexist on same infrastructure. VKS (vSphere Kubernetes Service) provides managed K8s clusters.

Desktop Virtualization (VDI):

Horizon View on vSphere. Persistent/non-persistent desktops. Instant clones for rapid provisioning (<2 seconds).

Edge Computing:

Single-host ESXi deployments at retail/branch locations. Managed centrally via vCenter.

Value Proposition for Virtualization

Hardware Efficiency:

Without virtualization: typical server runs at 5-15% CPU utilization. With: 60-80% utilization. ROI in hardware alone is 3-5x.

Operational Agility:

Provision new server in minutes (not weeks). Scale up/down with DRS automation. No procurement cycle for dev/test.

Standardization:

vSphere Configuration Profiles enforce consistent ESX configuration at cluster level (Host Profiles are deprecated in vCenter 9.0). VM templates enforce OS/app standards. Reduces configuration drift.

Security:

VM isolation (each VM has own address space). Micro-segmentation (with NSX, not in VVF). vTPM and VM encryption. Secure Boot chain from hardware to guest.

Cost Reduction:

Fewer physical servers = less power, cooling, rack space, cabling. Centralized management reduces admin overhead. License consolidation.

Holodeck Lab Note: In Holodeck environment, virtualization is nested — ESXi hosts are themselves VMs running on physical ESXi. This demonstrates Type 1 hypervisor running inside Type 1, useful for understanding CPU/memory overhead and performance characteristics of nested environments.

Key Takeaways

  • Exam: Know Type 1 (bare-metal, ESXi) vs Type 2 (hosted, Workstation) hypervisor distinction. ESXi is always Type 1.
  • Exam: Understand overcommit — CPU uses time-slicing, memory uses ballooning/compression/swap hierarchy. TPS shares identical pages.
  • Exam: Value proposition = hardware efficiency (5-15% → 60-80% utilization), operational agility (minutes not weeks), security (isolation, encryption).

VVF Networking Fundamentals (Objective 2.4)#

Blueprint Objective 2.4 — VMware Network Fundamentals

Differentiate Between VVF Networking Components

VVF uses traditional vSphere networking only — no NSX overlay. Understanding the components and when to use each is critical.

vSphere Standard Switch (vSS):

├── Scope: Host-local only — each ESXi host has its own vSS
├── Configuration: Manual per-host (no central management)
├── Port groups: Named network connections (e.g., "VM Network", "Management")
├── NIC teaming: originating virtual port, source MAC hash, IP hash, explicit failover order (load-based teaming is vDS-only)
├── Limitations: No LACP, no NetFlow, no port mirroring, no central policy
├── Use case: Small deployments, edge locations, labs
└── Max ports: 4096 per vSS

vSphere Distributed Switch (vDS):

├── Scope: Cluster-wide — single configuration applied to all member hosts
├── Configuration: Centralized via vCenter (survives host rebuilds)
├── Port groups: Distributed port groups with uniform VLAN, security, traffic shaping
├── NIC teaming: All vSS modes PLUS LACP (Link Aggregation Control Protocol)
├── Advanced features:
│   ├── NetFlow: Export flow data to collector for traffic analysis
│   ├── Port mirroring: SPAN/RSPAN equivalent for packet capture
│   ├── Network I/O Control (NIOC): QoS — reserve bandwidth per traffic type
│   │   └── Shares: relative priority 1–100 per traffic type (Low 25, Normal 50, High 100), applied only when an uplink is saturated
│   ├── Traffic filtering: Allow/deny rules on port groups
│   └── Health check: Verify VLAN trunking, MTU, NIC teaming consistency
├── Use case: Production clusters, any deployment >3 hosts
└── Max ports: 60,000 per vDS

VMkernel Adapters (vmk):

├── vmk0: Management traffic (vCenter-to-ESXi communication)
├── vmk1: vMotion (live VM migration — dedicated recommended)
├── vmk2: vSAN (dedicated VLAN recommended; MTU 1500 or 9000 — consistent end to end)
├── vmk3: FT logging (Fault Tolerance — high bandwidth required)
├── vmk4: NFS/iSCSI storage (if external storage used)
└── Each vmk has: IP, subnet, VLAN, TCP/IP stack, MTU setting

Traffic Types and Isolation:

In VVF, physical separation or VLAN isolation is the primary security mechanism (no NSX DFW):

VLAN IDPurposeMTUNIOC shares (VCF 9.0 design defaults)
10Management1500Normal (50)
20vMotion9000Low (25)
30vSAN9000High (100)
40VM Network1500High (100)
50FT Logging9000Low (25)

The share column follows the VCF 9.0 Network I/O Control detailed design (defaults on the switches VCF creates). On a vDS you create yourself, vSAN traffic starts at Normal/50; the vSAN networking guide's example raises it to High/100 when vSAN shares physical NICs.

Jumbo Frames (MTU 9000):

Supported, not required, for vSAN (vSAN runs at 1500; jumbo frames can reduce CPU use and raise throughput — VCF 9.0.1 vSAN networking: 'vSAN fully supports jumbo frames' and the decision is yours; recommended for vSAN storage clusters). Recommended for vMotion. If used, enable end-to-end: ESX vmk → vDS/vSS → physical switch → destination.
Verify: vmkping -d -s 8972 <target_ip> (8972 + 28 header = 9000 MTU)

NIOC v3 (Network I/O Control):

Quality of Service for virtual networking. Assigns bandwidth shares and reservations per traffic type. Critical when vSAN, vMotion, and VM traffic share physical NICs.

Holodeck Lab Note: Holodeck nested environment uses vDS for all traffic. Jumbo frames may not work in nested environments due to outer ESXi MTU limitations. Test with standard MTU 1500 first, then verify jumbo frame path if outer host supports it.

Key Takeaways

  • Exam: vSS = host-local, manual config, no LACP. vDS = cluster-wide, centralized, LACP + NetFlow + NIOC + port mirroring.
  • Exam: Know VMkernel adapter assignments — vmk0 (mgmt), vmk1 (vMotion), vmk2 (vSAN). A dedicated vSAN VLAN is recommended; jumbo frames are supported but optional and must match end to end.
  • Exam: NIOC v3 provides QoS via bandwidth shares/reservations/limits. Shares are relative (Low 25, Normal 50, High 100) and act only under contention; the VCF 9.0 design sets vSAN and VM traffic High, management Normal, vMotion and FT Low.

VVF Deployment & Supervisor Configuration (Objective 4.1)#

Blueprint Objective 4.1 — VVF: Deploy and Configure

Components of a VVF Deployment

VVF deployment consists of:

├── ESX 9.0 hosts (minimum 3 for vSAN quorum, minimum 1 for non-vSAN)
├── vCenter Server Appliance (VCSA 9.0) — single appliance (vCenter HA, if used, is a three-node active/passive/witness cluster)
├── vSAN cluster (if HCI storage desired)
├── vSphere Distributed Switch (recommended) or Standard Switch
├── VCF Operations (integrated monitoring)
├── VCF Operations for Logs (centralized logging)
└── vSphere Supervisor (optional — for Kubernetes workloads)

NOT included in VVF deployment:

├── NSX Manager (no overlay networking)
├── VCF Automation (no cloud templates/service broker)
├── SDDC Manager and VCF Instance fleet management (that's VCF, not VVF — VVF does include VCF Operations)
└── Fleet Manager (VCF-only)

VVF Deployment Process

Step 1: Hardware Preparation

├── Verify servers in VMware Compatibility Guide (VCG)
├── Configure BIOS: VT-x/AMD-V enabled, AES-NI (vSAN encryption), UEFI Secure Boot
├── Network: Management VLAN configured on ToR switches, trunk ports for vDS
└── Storage: Local disks for vSAN or SAN/NAS for external storage

Step 2: ESXi Installation

├── Boot from ISO (USB, PXE, or iLO/iDRAC virtual media)
├── Accept EULA, select boot disk (USB or local SSD)
├── Set root password, configure management network (vmk0)
├── Post-install: Enable SSH, set NTP (esxcli system ntp set --server=<ntp-ip>)
└── Repeat for all hosts

Step 3: vCenter Deployment

├── Deploy VCSA 9.0 OVA to first ESXi host
│   ├── Stage 1: Deploy appliance (15-20 min)
│   └── Stage 2: Configure SSO domain (vsphere.local), NTP, DNS
├── Sizing: pick from the deployment-size table in the VCSA section (Small 4 vCPU/21 GB up to 100 hosts/1,000 VMs; Medium 8 vCPU/30 GB up to 400 hosts/4,000 VMs)
└── Post-deploy: Create datacenter object, add ESXi hosts, create cluster

Step 4: Cluster Configuration

├── Create vSphere cluster with DRS and HA enabled
├── Configure vDS: Create distributed switch, add hosts, migrate vmk adapters
├── Enable vSAN: Select disks (cache + capacity), choose ESA or OSA
├── Configure storage policies (FTT, RAID level)
└── Verify: vSAN Health Check all green

Step 5: Configure Supervisor (vSphere Kubernetes)

Supervisor enables Kubernetes workloads on vSphere clusters:

Prerequisites:

├── vSphere cluster with DRS enabled (fully automated recommended)
├── HA enabled on cluster
├── vSAN or shared storage (for persistent volumes)
├── Networking: vDS with dedicated port group for Supervisor (or NSX — but VVF uses vDS)
└── Load balancer: Foundation Load Balancer (bundled with vCenter 9.0, Layer 4, VDS networking) or Avi Load Balancer; HAProxy is deprecated in 9.0. The Easy Supervisor option starts without a load balancer (VMs only) and adds one later for VKS

Supervisor Deployment (vDS networking mode — VVF):

├── vCenter → Workload Management → Enable Supervisor
├── Select cluster, choose "vSphere Distributed Switch" networking
├── Configure:
│   ├── Management network: static mode takes a block of 5 consecutive IPs (one per control-plane VM, the floating IP, and a buffer for a replacement VM)
│   ├── Workload network: IP range for Kubernetes nodes
│   ├── Storage policy: Select vSAN policy for persistent volumes
│   ├── Content library: For VM images (Ubuntu, Photon OS)
│   └── Load balancer: Foundation Load Balancer (deployed with the Supervisor) or Avi (controller endpoint, credentials, VIP range)
├── Deployment creates 1 (single Management Zone / Easy Supervisor) or 3 (three Zones) Supervisor control plane VMs
└── Validation: kubectl get nodes shows Supervisor nodes Ready

Supervisor Namespaces:

├── Logical isolation boundary for Kubernetes workloads
├── Each namespace gets: resource quota (CPU, memory, storage), network policy, storage policy
├── Admin creates namespace → assigns to developer → developer deploys workloads
└── Access: kubectl vsphere login --server=<supervisor-ip> --vsphere-username=user@domain

Holodeck Lab Note: Supervisor deployment in Holodeck requires careful resource planning — three Small control plane VMs consume 12 vCPU and 48 GB RAM (one VM in the single-Zone model). Ensure Holodeck hosts have sufficient resources. Use Foundation Load Balancer with VDS networking (HAProxy is deprecated in 9.0).

Key Takeaways

  • Exam: VVF deployment components = ESXi + VCSA + vSAN + vDS + VCF Operations + VCF Ops for Logs. No NSX, no SDDC Manager, no Fleet Manager.
  • Exam: Supervisor in VVF uses vDS networking (not NSX). Requires: DRS Fully Automated, HA enabled, shared storage, and a load balancer — Foundation Load Balancer (bundled) or Avi; HAProxy is deprecated in 9.0.
  • Exam: Supervisor creates 1 or 3 control plane VMs (single or three Management Zones). Namespaces provide logical isolation with resource quotas, network policies, storage policies.

VCF Operations & Operations for Logs in VVF (Objective 4.3)#

Blueprint Objective 4.3 — VVF: Operate

This is the largest section of the exam (19 sub-objectives). VCF Operations and VCF Operations for Logs are included in VVF licensing and are the primary monitoring/observability tools.

VCF Operations — Architecture & Deployment (Obj 4.3)

VCF Operations (formerly vRealize Operations / Aria Operations) is a monitoring, capacity planning, and compliance platform.

Cluster Components (VCF Operations 9.0 analytics cluster):

├── Primary node (and a primary replica node for high availability)
├── Data nodes: scale out analytics and storage
├── Witness node: only in a continuous-availability cluster (VCF 9.0.1 docs p.1317)
└── Cloud proxies: collect metrics and, from 9.0, logs from remote or segmented sites (cloud proxy is recommended over the older remote collector, p.2975)

Deployment Options:

├── Simple (single node) or High Availability (primary + primary replica) at deployment
├── Continuous availability: primary and replica fault domains plus a witness node (p.1317)
└── Node and cloud proxy sizes come from the VCF Operations sizing guidelines; size by object and metric count

Initial Setup:

├── Deploy OVA → configure admin password → access UI (https://<ops-ip>)
├── Add vCenter adapter: Provide vCenter IP, credentials, test connection
├── Adapter collects: VMs, hosts, clusters, datastores, networks, vSAN objects
├── Data collection starts immediately; analytics available after ~24 hours (baseline)
└── Content packs: Install for vSAN, Kubernetes, storage, network visibility

VCF Operations for Logs — Architecture & Deployment (Obj 4.3)

Centralized log management (formerly vRealize Log Insight / Aria Operations for Logs).

Cluster Components:

├── Primary Node: Ingests, indexes, and stores log data
├── Worker Nodes: Horizontal scale for ingestion throughput
└── Integrated Load Balancer: Distributes log traffic across nodes

Deployment Options:

├── Standalone: 1 node (up to 5,000 events/second)
├── Cluster: 3+ nodes with integrated LB (10,000+ events/second)
└── HA: Primary + 2 workers minimum for redundancy

Log Sources:

├── ESXi: Syslog forwarded to Ops for Logs (esxcli system syslog config set --loghost=<ip>)
├── vCenter: VCSA syslog configuration → Ops for Logs endpoint
├── vSAN: ESX hosts send vSAN logs over syslog; vSAN metrics come from the vSAN performance service via VCF Operations
├── VMs: Agent-based (Fluentd) or agentless (syslog)
└── Custom: Any syslog-capable source (network switches, firewalls, apps)

Metrics, Properties, and Logs — Differentiation (Obj 4.3)

Metrics:

├── Numeric time-series data collected at regular intervals
├── Examples: CPU usage %, memory consumed MB, disk latency ms, IOPS
├── Source: vCenter performance counters, vSAN performance service
├── Retention: 5-minute intervals for 1 day, 1-hour for 1 month, 1-day for 1 year (default)
└── Use: Trending, capacity planning, anomaly detection

Properties:

├── Configuration attributes — static or slowly changing
├── Examples: VM name, host model, ESXi version, vSAN disk type, cluster DRS level
├── Source: vCenter inventory, hardware probes
├── Retention: Current value + history of changes
└── Use: Filtering, grouping, compliance checks

Logs:

├── Unstructured or semi-structured text events
├── Examples: "Host esxi-01 lost network connectivity at 14:32:05", vpxd.log entries
├── Source: Syslog, VCSA logs, ESXi logs, application logs
├── Retention: Configurable (default 30 days, archive to NFS/S3)
└── Use: Root cause analysis, security forensics, audit trail

Custom Views & Reports (Obj 4.3)

Views:

├── Tabular display of objects with selected metrics/properties
├── Create: Operations UI → Dashboards → Views → Create View
├── Types: List (table), Summary (aggregated), Distribution (histogram), Trend (time-series)
├── Filters: By object type, property value, metric threshold
└── Share: Export as CSV/PDF, schedule email delivery

Reports:

├── Multi-page documents combining views, charts, and text
├── Templates: Pre-built (Capacity, Performance, Compliance) or custom
├── Schedule: Daily/weekly/monthly auto-generation
├── Format: PDF or CSV
└── Use case: Weekly capacity report for management, monthly compliance audit

Dashboards (Obj 4.3)

Creating Dashboards:

├── Operations UI → Dashboards → Create Dashboard
├── Widgets: Scorecards, heatmaps, top-N, trend charts, object lists, alerts
├── Interactions: Widget-to-widget linking (click host → filter VMs)
├── Layout: Grid-based, drag-and-drop
└── Share: Assign to user/group, set as default, export/import

Sharing Dashboards:

├── Per-user or per-group visibility
├── Read-only or edit permissions
├── Export as JSON for backup/migration
└── Import from content packs (vSAN dashboard pack, K8s dashboard pack)

Alerting (Obj 4.3)

Alert Definitions:

├── Symptom: Single condition (CPU > 90% for 5 min)
├── Alert: One or more symptoms combined with logic (AND/OR)
├── Recommendation: Suggested action attached to alert
├── Notification: Email, webhook, SNMP trap, REST API callback

Built-in Alert Examples:

├── "Host CPU Contention" — CPU ready > 5% for 10 minutes
├── "Datastore Running Out of Space" — free space < 15%
├── "vSAN Disk Latency High" — write latency > 30ms for 5 minutes
├── "VM Memory Pressure" — balloon + swap > 20% of configured memory
└── Custom: Create symptom → create alert definition → attach notification

Log Events Monitoring (Obj 4.3)

Explore Logs (in VCF 9.0 logs can also be analysed directly in VCF Operations, VCF 9.0.1 docs p.100; the VCF Operations for logs UI offers the same search):

├── Full-text search across all ingested logs
├── Structured fields: timestamp, source, text, facility, severity
├── Filters: Time range, source (host/VM/app), severity (emergency→debug)
├── Group by: Source, field extraction (regex), time bucket
├── Save as: Named query, alert trigger
└── Example: Search "SCSI sense code" + source=esxi* → find storage errors across fleet

Dashboards in Operations for Logs (Obj 4.3):

├── Pre-built: ESXi overview, vCenter events, vSAN errors
├── Custom: Create from saved queries, pin charts to dashboard
├── Widgets: Event trend (line chart), top sources (bar), event distribution (pie)
└── Share: Same model as Operations dashboards (user/group visibility)

Costing & Pricing (Obj 4.3)

VCF Operations Costing:

├── Define cost drivers: Server hardware ($/month), storage ($/GB), network ($/port)
├── Assign costs to clusters, datastores, host groups
├── Chargeback: Allocate costs to business units based on VM resource consumption
├── Showback: Display costs without billing (awareness mode)
├── Reports: Cost per VM, cost per business unit, cost trend, what-if scenarios
└── Setup: Operations UI → Administration → Cost Settings → Define rate cards

VCF Operations Integration (Obj 4.3):

├── vCenter adapter: Primary data source (inventory + metrics)
├── vSAN adapter: Deep storage metrics (disk health, rebuild status)
├── Kubernetes adapter: Supervisor and TKG cluster monitoring
├── SNMP adapter: Network device monitoring
├── REST API: Custom integrations (ServiceNow, Slack, PagerDuty)
└── Operations for Logs integration: Correlate metrics with log events

vSAN Storage Operations (Obj 4.3):

├── Deep vSAN monitoring within VCF Operations
├── Metrics: Disk health, rebuild progress, dedup ratio, capacity forecast
├── Alerts: Disk failure prediction, capacity threshold, congestion
├── Views: Per-disk group, per-host, per-cluster vSAN performance
└── Capacity planning: Predict when vSAN will need additional disks/hosts

VCF Operations Policies (Obj 4.3):

├── Define thresholds for alerts and capacity
├── Types: Capacity remaining (days), workload utilization, compliance
├── Apply to: Object groups (clusters, datacenters, custom groups)
├── Override: Per-object or per-group policy customization
└── Compliance: Map to regulatory frameworks (CIS, DISA STIG, PCI-DSS)

Application Monitoring (Obj 4.3):

├── Service Discovery: Auto-detect applications running in VMs
│   └── Discovers: Web servers (Apache, IIS), databases (MySQL, PostgreSQL), app servers
├── Application-aware metrics: Response time, throughput, error rate
├── Dependency mapping: VM → application → service → infrastructure
└── Setup: Install Telegraf agent in guest OS, or use agentless discovery

Security Hardening & Compliance (Obj 4.3):

├── Security benchmarks: CIS ESXi, DISA STIG, PCI-DSS
├── Compliance dashboard: Green/yellow/red per host, per cluster
├── Drift detection: Configuration changes from hardened baseline
├── Remediation: Recommendations with PowerCLI/esxcli commands
└── Reports: Compliance status over time, audit-ready export

VCF Operations for Logs — Cluster & Deployment (Obj 4.3):

├── Already covered above in Architecture section
├── Integration with VVF components:
│   ├── ESX syslog → Ops for Logs (configure via vSphere Configuration Profiles or esxcli)
│   ├── vCenter events → Ops for Logs (VCSA syslog configuration)
│   ├── vSAN logs → Ops for Logs (through ESX syslog)
│   └── VCF Operations → Ops for Logs (bidirectional launch-in-context)
└── Configure integration: Ops for Logs UI → Administration → Integration → Add VCF Operations

Holodeck Lab Note: VCF Operations and VCF Operations for Logs can be deployed in Holodeck as nested VMs. Minimum sizing for lab: VCF Ops = 4 vCPU/16GB RAM, Ops for Logs = 4 vCPU/8GB RAM. Configure ESXi syslog forwarding from all Holodeck ESXi hosts to Ops for Logs for hands-on log analysis practice.

Key Takeaways

  • Exam: VCF Operations = metrics + analytics + capacity + compliance. VCF Operations for Logs = centralized log management. Both included in VVF.
  • Exam: Know the difference — Metrics (numeric, time-series, trending), Properties (config attributes, static), Logs (text events, forensics).
  • Exam: Dashboards use widgets (scorecards, heatmaps, top-N). Alerts = symptoms + logic + notifications. Policies define thresholds per object group.
  • Exam: Costing = rate cards + chargeback/showback. Service Discovery = auto-detect apps in VMs. Compliance = CIS/DISA STIG benchmarks.
  • Exam: Operations for Logs — Explore Logs for full-text search, structured field filtering, regex extraction. Integrates bidirectionally with VCF Operations.

VVF Consume & Automate — Supervisor Services, VKS, Orchestrator (Objective 4.4)#

Blueprint Objective 4.4 — VVF: Consume and Automate

Supervisor-Based Services in VVF (Obj 4.4)

The vSphere Supervisor is a Kubernetes control plane embedded in vSphere. In VVF, Supervisor uses vDS networking (not NSX).

Supervisor Services:

├── Built-in services that extend Supervisor functionality
├── Catalog: vCenter → Workload Management → Services → Service Catalog
├── Examples:
│   ├── Contour (Ingress Controller): HTTP/HTTPS routing to K8s services
│   ├── Harbor (Container Registry): Private image registry on-premises
│   ├── Velero (Backup): Kubernetes resource and persistent volume backup
│   ├── MinIO (Object Storage): S3-compatible storage for cloud-native apps
│   ├── cert-manager: Automated TLS certificate management
│   └── External DNS: Automatic DNS record management for K8s services
├── Installation: Download from VMware Marketplace → Install via vCenter UI
├── Lifecycle: Versioned, upgradeable through vCenter Workload Management
└── Networking: Services use the Supervisor load balancer (Foundation Load Balancer or Avi in VVF)

Deploy Virtual Machines Using VM Service (Obj 4.4)

VM Service enables self-service VM provisioning through Kubernetes API:

Concept:

├── Define VM class (size: CPU, memory)
├── Define content library (VM images: Ubuntu, Windows, Photon OS)
├── Developer creates VirtualMachine YAML manifest
├── kubectl apply -f vm.yaml → VM created on vSphere cluster
└── VM managed through both kubectl and vCenter UI

VM Classes (predefined resource profiles):

├── best-effort-xsmall: 2 vCPU, 2GB RAM (no reservation)
├── best-effort-small: 2 vCPU, 4GB RAM
├── best-effort-medium: 4 vCPU, 8GB RAM
├── guaranteed-small: 2 vCPU, 4GB RAM (100% reservation)
├── guaranteed-medium: 4 vCPU, 8GB RAM (100% reservation)
└── Custom: Admin defines via vCenter → Workload Management → VM Classes

Example VM Service YAML (v1alpha3, the API version the VCF 9.0 docs use, p.5969; v1alpha1 is deprecated, p.240):

apiVersion: vmoperator.vmware.com/v1alpha3
kind: VirtualMachine
metadata:
  name: my-ubuntu-vm
  namespace: dev-team
spec:
  className: best-effort-medium
  imageName: vmi-<id from kubectl get vmi -n dev-team>
  storageClass: vsan-default-storage-policy
  powerState: PoweredOn

Deploy Kubernetes Workloads Using VMware Kubernetes Services (VKS) (Obj 4.4)

VKS (formerly Tanzu Kubernetes Grid) provides managed Kubernetes clusters:

Architecture:

├── Supervisor: control plane of one or three VMs on the vSphere cluster
├── VKS cluster: workload cluster created by the Supervisor (Cluster API)
│   ├── Control plane nodes: 1 or 3 (HA)
│   ├── Worker nodes: 1-N (auto-scaled via MachineDeployment)
│   └── Container runtime: containerd
├── Storage: Persistent volumes backed by vSAN (CSI driver)
└── Networking: Antrea CNI (default in VVF, replaces NSX NCP)

Create a VKS cluster (ClusterClass = the builtin-generic class shipped with your VKS version; VKS 3.3.1 in VCF 9.0 supports VKr 1.28+ and drops 1.27.x; 'tanzukubernetescluster' is deprecated):

apiVersion: cluster.x-k8s.io/v1beta1
kind: Cluster
metadata:
  name: prod-cluster
  namespace: dev-team
spec:
  topology:
    class: builtin-generic-v3.3.0
    version: <a READY VKr, e.g. v1.32.x+vmware.x-fips>
    controlPlane:
      replicas: 3
    workers:
      machineDeployments:
      - class: node-pool
        name: worker-pool-1
        replicas: 5

Lifecycle:

├── Upgrade: Change spec.topology.version to a newer VKr (kubectl edit) → rolling update of the nodes ('Update a v1beta1/v1beta2 VKS Cluster by Editing the VKr Version', Supervisor 9.0 Services docs)
├── Scale: Change worker replicas → auto-provisioned
├── Delete: kubectl delete cluster prod-cluster → all resources cleaned up
└── Monitor: vCenter → Workload Management → Clusters shows status

Deploy vSphere Pods and Other Services (Obj 4.4)

vSphere Pods (included here because Objective 4.4 names them). The VCF 9.0 documentation conflicts on whether a VDS-networked Supervisor can run them. 'What Is a vSphere Pod?' (p.5212) says: "vSphere Pods are only supported with Supervisors that are configured with NSX as the networking stack." 'Add a Load Balancer to a Simplified Supervisor Deployment' (p.5311, p.5314) says: "Adding a load balancer enables use of the vSphere Pods and Supervisor Services in addition to the VM Service." Treat NSX networking as the documented baseline for the exam, and confirm vSphere Pod support on your own build before relying on it on a VDS-networked VVF Supervisor:

├── Lightweight containers running directly on ESX (no worker VM needed)
├── Each pod gets its own micro-VM (CRX — Container Runtime for ESXi)
├── Benefits: VM-level isolation + container-level density
├── Limitations: Only Linux containers, limited to Supervisor namespace
└── Use case: High-security workloads requiring VM isolation per container

Other Services:

├── Persistent Volume Claims: vSAN CSI driver auto-provisions VMDKs
├── Load Balancer Services: Foundation Load Balancer or Avi in VVF (automatic VIP allocation)
├── Ingress: Contour or third-party (Nginx, Traefik)
└── Service Mesh: Istio (manual install, not built-in for VVF)

VCF Operations Orchestrator (Obj 4.4)

VCF Operations Orchestrator (formerly vRealize Orchestrator / Aria Automation Orchestrator):

Purpose:

├── Workflow automation engine for vSphere operations
├── Pre-built workflows: VM lifecycle, snapshot management, reporting
├── Custom workflows: JavaScript/Python actions + drag-and-drop designer
├── Integration: vCenter API, REST endpoints, PowerShell, SSH
└── Scheduling: Run workflows on schedule or trigger on events

Use Cases in VVF:

├── Automated VM provisioning with approval workflow
├── Scheduled snapshot cleanup (delete snapshots >7 days)
├── Automated compliance remediation (remediate vSphere Configuration Profile drift; Host Profiles are deprecated in 9.0)
├── Custom reporting (query vCenter API, format, email)
├── Integration with ITSM (ServiceNow ticket creation on alert)
└── Day-2 operations: disk expansion, CPU/memory hot-add workflows

Deployment:

├── Standalone appliance (2 vCPU, 6GB RAM, 100GB disk)
├── Embedded mode: Included with VCF Operations (if deployed)
├── Access: https://<orchestrator-ip>/orchestration-ui/
└── API: RESTful API for external integration

Holodeck Lab Note: VKS cluster deployment in Holodeck requires: (1) Supervisor enabled on Holodeck cluster, (2) Foundation Load Balancer (or Avi) configured for the Supervisor, (3) Content library with VKr node images. Minimum resources for 1 TKG cluster: 3 control plane VMs (6 vCPU, 24GB) + 3 workers (6 vCPU, 24GB) = 12 vCPU, 48GB total. Plan Holodeck host resources accordingly.

Key Takeaways

  • Exam: VM Service = deploy VMs via kubectl YAML. VM Classes define resource profiles (best-effort vs guaranteed). Content Library provides images.
  • Exam: VKS = managed Kubernetes clusters on vSphere. Uses Cluster API, Antrea CNI (not NSX), vSAN CSI for persistent volumes.
  • Exam: vSphere Pods = containers with VM-level isolation (CRX micro-VMs). Only Linux, only in Supervisor namespace.
  • Exam: VCF Operations Orchestrator = workflow automation engine. Pre-built + custom workflows. Use cases: VM lifecycle, snapshot cleanup, compliance remediation.

VCF Operations Policies, Explore Logs & Certificate/Identity Management (Objectives 4.2–4.3)#

VCF Operations Policies (Obj 4.3)

VCF Operations uses policies to automate operational decisions. Policy types:

Alert Policies:

├── Symptom-based: Trigger when a metric crosses threshold (e.g., CPU usage >90% for 5 min)
├── Condition-based: Multiple symptoms combined with AND/OR logic
├── Notification: Email, Webhook, SNMP trap, Slack integration
├── Suppression: Silence known-maintenance alerts via maintenance schedules
└── Smart alerting: VCF Operations groups related alerts into a single root-cause alert

Capacity Policies:

├── Time Remaining: Alert when projected resource exhaustion is within X days
├── Risk-based: High/medium/low risk scores based on utilization trends
├── Committed capacity: Track reserved vs actual usage across clusters
└── Reclaimable resources: Identify idle VMs, oversized VMs, orphaned VMDKs for reclamation

Automation Policies:

├── Workload placement: DRS-like recommendations based on cost/performance optimization
├── Right-sizing: Recommend CPU/memory resize based on utilization history (30/60/90 day)
├── Reclamation: Auto-tag VMs with no activity for >30 days for review
└── Custom actions: Script execution via VCF Operations Orchestrator on policy trigger

Compliance Policies:

├── vSphere Configuration Guide (SCG) benchmarks
├── DISA STIG profiles for DoD environments
├── CIS Benchmark alignment
├── Custom compliance templates: Define organization-specific hardening standards
├── Drift detection: Alert when host/VM configuration deviates from baseline
└── Remediation: One-click fix for non-compliant settings (e.g., enable SSH timeout, disable TLS 1.0)

Explore Logs Feature (Obj 4.3j)

VCF Operations for Logs provides an interactive log exploration interface:

Explore Logs UI:

├── Search bar: Full-text search across all ingested logs (syslog, vCenter events, NSX logs)
├── Filters: By source (ESXi, vCenter, NSX, vSAN), severity (emergency→debug), time range
├── Field extraction: Auto-parse structured log fields (hostname, process, PID, message)
├── Saved queries: Save frequent searches for reuse (e.g., "all PSOD events last 7 days")
├── Query language: Supports regex, wildcard, AND/OR/NOT operators
└── Export: Download filtered log results as CSV for offline analysis

Log Dashboard Integration:

├── Pin log query results to custom dashboards
├── Create log-based widgets: top error sources, log volume trends, severity distribution
├── Cross-reference: Link log events to VCF Operations metric anomalies
└── Alerts: Create alert definitions from log patterns (e.g., "if >10 auth failures in 5 min")

vSphere Pods (Obj 4.4d)

vSphere Pods run containers natively on ESXi without a guest OS VM:

Architecture:

├── CRX (Container Runtime for ESXi): Lightweight VM that acts as pod sandbox
├── Each pod gets its own CRX instance with dedicated kernel
├── Spherelet: Kubernetes kubelet equivalent running on ESXi
├── Integration: Pods appear in vCenter inventory alongside VMs
└── Networking: on an NSX-networked Supervisor, pod networking is provided through NSX (DOCUMENTED, VCF 9.0 p.5212); that NSX Container Plugin (NCP) provides it via NSX segments is ASSUMED, not re-checked against the 9.0 text

Use Cases:

├── Privileged workloads requiring direct hardware access
├── Low-latency applications (no guest OS overhead)
├── CI/CD ephemeral build agents (fast startup, disposable)
└── Sidecar/init containers running alongside VMs in the same namespace

Deployment:

├── Enable Workload Management on cluster → Supervisor created
├── Create vSphere Namespace → assign resource quotas
├── Apply VM Class and Storage Class to namespace
├── kubectl apply -f pod.yaml (standard K8s manifest)
└── Pod scheduled by Supervisor's scheduler → CRX created on ESXi host

Limitations:

├── No DRS-aware live migration (pod must be recreated on another host)
├── NSX networking is the documented baseline (DOCUMENTED, VCF 9.0 p.5212); the VCF 9.0 documentation conflicts on whether a VDS-networked Supervisor with a load balancer can run vSphere Pods (p.5311, p.5314), so confirm on your own build (see Consume & Automate, Obj 4.4)
├── Not supported on stretched clusters
└── Pod storage is ephemeral by default; use PVCs for persistent data

Certificate Management in VVF (Obj 4.2c)

VMCA (VMware Certificate Authority):

├── Embedded CA in vCenter: Issues certificates to ESXi hosts, vCenter services, Solution Users
├── Certificate hierarchy: VMCA Root CA → Machine SSL → Solution User certs
├── Default mode: VMCA is a self-signed root CA — 'a just-enough internal certificate authority' (VCF 9.0 docs, programming guide: 'Change the Machine SSL Certificate of vCenter'); optional modes: VMCA as a subordinate (intermediate) CA of the enterprise CA, or custom certificates on every endpoint
├── Custom CA mode: Replace VMCA root with enterprise CA-signed certificate
├── Certificate lifecycle: the VVF getting-started flow lists 'configure certificate management in VCF Operations' as a post-deployment task. For VVF the docs scope this to the VCF Operations component ('Managing Certificates in VMware vSphere Foundation'; Administration → Control Panel → Trusted Certificates); the Fleet Management > Certificates workflows (auto-renewal for VMCA, MSCA and OpenSSL CA, CA configuration, CSR generation, expiry notifications, p.457) are documented for VCF Instances
└── Certificate refresh (vCenter-local fallback): vCenter UI → Administration → Certificates → Certificate Management

Certificate Replacement Scenarios:

├── Replace Machine SSL cert: When hostname changes or cert expires
├── Replace VMCA Root: When transitioning to enterprise CA
├── Replace Solution User certs: Rarely needed; auto-generated by VMCA
├── ESXi host certificates: Auto-provisioned by VMCA when host joins vCenter
└── Thumbprint verification: For trust establishment between components

Certificate Store:

├── VECS (VMware Endpoint Certificate Store): Central cert repository on vCenter
├── Stores: MACHINE_SSL_CERT, TRUSTED_ROOTS, SMS, vpxd, vsphere-webclient
├── CLI: /usr/lib/vmware-vmafd/bin/vecs-cli store list
├── Backup: Include VECS in vCenter backup strategy
└── Troubleshooting: Certificate mismatch → services fail to start → check vecs-cli entry list

Identity Management & RBAC in VVF (Obj 4.2a)

Identity Sources:

├── Embedded SSO (vsphere.local): Default identity domain, always available
├── Integrated Windows Authentication: removed in vCenter 9.0 — migrate to Active Directory over LDAPS or to identity federation with MFA (VCF 9.0 End of Support Notes)
├── Active Directory over LDAP: Configure LDAP endpoint for AD queries
├── OpenLDAP: Third-party LDAP directory support
└── ADFS/Okta (Identity Federation): SAML 2.0 or OIDC identity providers

Role-Based Access Control (RBAC):

├── Privileges: Granular permissions (e.g., VirtualMachine.Interact.PowerOn)
├── Roles: Named collections of privileges (Administrator, ReadOnly, VM Power User, custom)
├── Principals: Users or groups from identity sources
├── Objects: vCenter inventory objects (datacenter, cluster, folder, VM, datastore)
├── Permissions: Principal + Role + Object + Propagation (inherit to children)
└── Global Permissions: Apply at root vCenter level, propagate everywhere

Built-in Roles:

├── Administrator: Full control (assign sparingly — principle of least privilege)
├── Read-Only: View inventory, no changes
├── No Access: Explicitly deny access to object subtree
├── VM Power User (custom example): PowerOn/Off, Console, Snapshot — no reconfigure
└── Network Administrator (custom): Port group management, no VM operations

Best Practices:

├── Use AD groups, not individual users, for permission assignments
├── Apply permissions at folder level, not individual VM level (scalability)
├── Audit permissions quarterly: vCenter → Administration → Access Control → Roles
├── Enable vCenter event logging for permission change tracking
└── Use Global Permissions only for cross-datacenter admin roles

Key Takeaways

  • VCF Operations policies include Alert, Capacity, Automation, and Compliance types — each automates operational decisions at scale.
  • Explore Logs provides interactive log search with regex/wildcard queries, field extraction, saved queries, and dashboard integration.
  • vSphere Pods run on CRX (Container Runtime for ESXi) — native containers without guest OS overhead, managed via kubectl.
  • VMCA is the embedded certificate authority in vCenter — manages machine SSL, solution user, and ESXi host certificates automatically.
  • RBAC uses Privileges → Roles → Permissions model. Always assign permissions to AD groups at folder level, not individual VMs.

VCF 9.x Operational Changes: Green Score, Storage DRS and vCLS#

GREEN SCORE (VCF Operations 9.0 / 9.1)

Green Score is a documented VCF Operations KPI — renamed from "Sustainability" in 9.0 — that measures energy efficiency in digital operations achieved through data-centre virtualization. It is comprised of multiple parameters and is configured at the ORGANIZATION level and for physical data centres.

Dashboards cover: Energy Efficiency with Virtualization (estimated carbon-footprint reduction versus physical), Energy Efficient Clusters / Infrastructure (compare clusters or data centres by estimated CO2 or power), Environmental Impact of Idle VMs (idle-VM identification), and aging compute/storage.

Important caveat Broadcom states explicitly: the calculators are INFORMATIONAL and are not intended for regulatory or compliance disclosure.

STORAGE DRS — WHAT CHANGED IN vSPHERE 9 / VCF 9.x
Storage DRS remains SUPPORTED, but only for a subset of what it used to do:

STILL SUPPORTED:

  • initial placement, space-utilization load balancing, anti-affinity rules
  • SDRS maintenance mode, automation levels, off-hours scheduling, SPBM limits

REMOVED in vCenter 9.0: the SDRS I/O Load Balancer, the SDRS I/O reservations-based load balancer, and Storage I/O Control (SIOC) entirely — including enabling SIOC on a datastore and setting Reservations/Shares through SPBM storage policies

The deprecation was pre-announced in vSphere 8.0 U3; 7.x and 8.x retain all three balancing modes for their lifecycle.

EXAM TRAP: "Storage DRS balances space AND I/O" is correct for 8.x and materially WRONG for 9.x. The 9.0 datastore-cluster documentation lists only space-utilization load balancing and anti-affinity rules, and the aggressiveness page sets thresholds for space used only.

vCLS IN vSPHERE 9 — DEPRECATED, NOT REPLACED

vSphere 9.0 DEPRECATES vCLS; it does not remove the agent VMs. Embedded vCLS VMs (vSphere-Pod-based, introduced in 8.0 U3, desired redundancy reduced from 3 to 2) still deploy by default and still appear in the vCLS folder.

What actually changed: vCLS is no longer REQUIRED. Verbatim from the docs — "Starting vSphere 9.0, vCLS can be disabled on a vSphere cluster without any impact to vSphere DRS or vSphere HA functionality" — and Broadcom recommends putting clusters into Retreat Mode to avoid the redundant resource usage. Full removal is deferred to a future vCenter release.

The enabling mechanism is DKVS, an etcd-based distributed key-value store run by clusterAgent on the ESX hosts, present in ESXi 8.x and 9.x and also used during vCenter restore-from-backup to provide more up-to-date recovery. Note the vCLS documentation pages do not themselves name DKVS — that link is inferential, so do not assert it as a documented vCLS replacement.

Key Takeaways

  • Green Score is real and documented (VCF Operations 9.0/9.1, renamed from Sustainability): energy efficiency of digital operations through virtualization, configured at organization and physical-data-centre level. Broadcom labels the figures informational, not for regulatory disclosure.
  • Storage DRS in vSphere 9/VCF 9.x: initial placement and SPACE balancing only. The I/O load balancer, the I/O reservations balancer and Storage I/O Control (SIOC) were all REMOVED in vCenter 9.0 — deprecation pre-announced in 8.0 U3.
  • vCLS in vSphere 9 is DEPRECATED, not replaced: embedded agent VMs still deploy, but DRS and HA no longer depend on them, so a cluster can run in Retreat Mode with no functional impact. Removal is deferred to a future release.
  • Exam trap: 'Storage DRS balances space and I/O' is right for 8.x, wrong for 9.x — the kind of version split exam questions exploit.

Exam Mapping: 2V0-16.25 — vSphere Foundation 9.0 Administrator

  • 2.1 Virtualization Fundamentals — principles, use cases, value proposition
  • 2.2 Compute Fundamentals — vCenter, ESX, clusters, VMs, Day 2 ops, Content Libraries, encryption
  • 2.3 Storage Fundamentals — vSphere storage, vSAN ESA/OSA, policies, resilience, space efficiency
  • 2.4 Network Fundamentals — differentiate VVF networking components
  • 4.1 Deploy & Configure — VVF components, deployment process, Supervisor configuration
  • 4.2 Manage — identity/RBAC, license mgmt, certificate mgmt, lifecycle mgmt
  • 4.3 Operate — VCF Operations (dashboards, alerts, views, reports, costing, policies, compliance, Service Discovery, vSAN Storage Ops, Ops for Logs)
  • 4.4 Consume & Automate — Supervisor Services, VM Service, VKS, vSphere Pods, VCF Operations Orchestrator

Labs in This Section

📝 Quiz — VVF 9.0 Administrator

0/60 correct

Section 1 — Architecture and Technologies

Q1
Which component is INCLUDED in VVF 9.0 but NOT part of VCF 9.0 differentiators?
  • VCF Automation
  • vCenter Standard + ESXi + VCF Operations (monitoring only)
  • NSX overlay networking
  • HCX
VVF 9.0 includes vCenter Standard, ESXi, and VCF Operations (monitoring only). NSX overlay networking, HCX, and VCF Automation are VCF-only differentiators not included in VVF.
Q2
In VVF 9.0, vSAN is offered as:
  • An optional add-on that must be purchased separately before use
  • Included as a full entitlement of 0.25 TiB per licensed core, pooled across the environment
  • Not available at all
  • Included with unlimited capacity
Each licensed VVF core includes a full vSAN entitlement of 0.25 TiB (250 GiB) of raw capacity, pooled across the whole VVF environment — unused capacity from compute-only clusters can be applied to vSAN-enabled clusters. It is an entitlement, not a trial and not an optional add-on; only capacity BEYOND 0.25 TiB/core is purchased as the vSAN add-on. Enabling vSAN is optional — VVF 9.0 also supports NFS and FC.
Q3
Which hypervisor type describes ESX 9.0?
  • Paravirtualized user-space hypervisor
  • Container runtime
  • Type 2 hosted hypervisor
  • Type 1 bare-metal hypervisor
ESXi is a Type 1 bare-metal hypervisor — it runs directly on hardware without a host OS. Type 2 runs on top of a host OS. Container runtime and paravirtualized hypervisor are different technologies.
Q4
What is the primary purpose of validating hardware against the VMware Hardware Compatibility List (HCL) for VVF?
  • To receive marketing discounts
  • To map to a specific vendor SKU
  • To ensure support, stability, and certified driver/firmware combinations for ESXi
  • To enable BIOS flashing
HCL validation ensures support, stability, and certified driver/firmware combinations. VMware only supports configurations on the HCL. Marketing discounts, BIOS flashing, and vendor SKU mapping are not HCL purposes.
Q5
VVF subscription licensing is based on which unit?
  • Per socket
  • Per physical core with a minimum per CPU
  • Per IP address
  • Per VM
VVF subscription licensing is per physical core with a minimum per CPU (typically 16 cores). Not per socket (legacy model), per VM, or per IP.

Section 2 — vSphere Configuration and Management

Section 3 — Storage Management

Section 4 — Networking

Section 5 — Operations and Troubleshooting

🃏 Flashcards — VVF 9.0 Administrator

61 cards
Card 1 of 61
VVF (vSphere Foundation)
VMware vSphere Foundation (VVF): a per-core subscription that includes vSphere with vCenter Standard, vSphere Supervisor with vSphere Kubernetes Service (VKS, formerly TKG Service), a vSAN capacity entitlement per core (more capacity is a per-TiB add-on), VCF Operations (formerly VMware Aria Operations) and VCF Operations for logs. VVF excludes NSX (full), HCX, VCF Automation, and fleet management. Targets customers who want modernized operations without full SDDC scope.
Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.