VMware Technology and Product Fundamentals
What to know
VMware certification candidates must be fluent in the core product stack and how the pieces fit together. Start with the hypervisor: ESXi is a Type 1 bare-metal hypervisor that runs virtual machines and owns the host's physical resources. vCenter Server is the centralized management plane - it manages many ESXi hosts, enables clustering, and hosts features such as vSphere HA, DRS, and vMotion. A cluster is a group of hosts sharing resource and availability policies; a resource pool divides cluster CPU and memory among groups of VMs.
Around the core, know the purpose of vSAN (software-defined storage), NSX (software-defined networking and security), VMware Cloud Foundation (integrated SDDC stack), Aria (operations, automation, and cost management), and Tanzu (Kubernetes and container management). Understand virtual hardware: virtual CPU, memory, virtual disks (VMDK), snapshot delta disks, and the VM files (VMX configuration, NVRAM, log, VMSD).
Traps
Questions love the near-miss distinctions. A snapshot is not a backup - it captures a point-in-time delta and grows over time. vMotion moves a running VM's compute; Storage vMotion moves its disks; both can be combined. vSphere HA restarts VMs after host failure, while DRS balances load across hosts. Licensing and edition questions often hinge on which feature belongs to which edition, and product names have been rebranded (vRealize to Aria), so learn current names alongside legacy ones.
Rule of thumb
Ask "where is this configured?" If the setting is host-local (networking, local storage, host advanced settings), the answer is ESXi. If it is cluster-wide, policy-driven, or spans hosts, the answer is vCenter. Worked example: a requirement to move VMs between hosts with different CPU generations without downtime points to vMotion plus EVC (Enhanced vCPU Compatibility) masking, configured at the cluster level.