VCI Registration Part 1 key terms

Software that runs directly on physical hardware or on an operating system and lets multiple virtual machines share the underlying CPU, memory, storage, and network resources. VMware ESXi is a type 1 hypervisor installed directly on the server.

A type 1 hypervisor from VMware that installs directly on server hardware and provides the virtualization layer for running virtual machines. It manages CPU, memory, storage, and networking for each guest and is configured through vCenter Server or its own host client.

The central management platform for VMware vSphere environments. It provides a single interface for configuring hosts, organizing them into clusters and data centers, deploying virtual machines, and enabling features such as vMotion, DRS, and High Availability.

A software-based computer that runs its own operating system and applications on virtualized hardware. Each one has virtual CPU, memory, disk, and network devices that the hypervisor maps to physical resources.

A file or set of files, typically with a .vmdk extension, that presents storage to a virtual machine as if it were a physical hard drive. It lives on a datastore and can be thin or thick provisioned.

A point-in-time record of a virtual machine's disk state and, optionally, its memory and power state. It allows quick rollback after a change or failed update, but it is not a substitute for a full backup.

A vSphere feature that moves a running virtual machine from one host to another with no downtime. It requires shared storage or a compatible storage configuration plus compatible CPU features and adequate network bandwidth.

A cluster-level feature that balances virtual machine workloads across hosts by monitoring resource use and either suggesting or automatically performing vMotion migrations according to configured rules and automation level.

A cluster feature that restarts virtual machines on surviving hosts when a host fails. It relies on heartbeats, admission control, and shared storage so that protected workloads can recover automatically.

A group of hosts managed together so their CPU, memory, and storage can be pooled. Clusters enable features such as vMotion, DRS, and High Availability, and they set the boundary for those capabilities.

A logical storage container that hosts virtual machine files. It can be backed by block storage such as Fibre Channel or iSCSI, by NFS, or by vSAN, and it is presented to hosts as a common unit.

A host-level virtual switch that connects virtual machine network adapters and VMkernel interfaces to physical uplinks. It is configured separately on each host and offers port groups, VLAN tagging, and traffic shaping.

A set of drivers and utilities installed inside a guest operating system that improves performance and enables features such as graceful shutdown, time synchronization, quiesced snapshots, and clipboard sharing.

A preconfigured master copy of a virtual machine that cannot be powered on. It is used to deploy new virtual machines quickly and consistently, often after customization such as hostname and network settings.

An architecture in which compute, storage, networking, and security are abstracted from hardware and managed through software policy. It enables automation, pooled resources, and consistent operations across private and public clouds.

The practice of combining workloads from many underused physical servers onto fewer, more fully utilized hosts through virtualization. It reduces hardware, power, cooling, and space costs while simplifying management and improving disaster recovery options.

The number of virtual machines supported per physical host, or the ratio of virtual to physical resources. It guides sizing decisions, and higher ratios increase efficiency but reduce headroom for spikes, failures, and maintenance.

The process of converting an existing physical server into a virtual machine, typically using a conversion tool that captures the disk contents and reconfigures drivers so the guest boots under the hypervisor.

The three standard delivery categories: Infrastructure as a Service provides compute, storage, and network; Platform as a Service adds runtime and development tooling; Software as a Service delivers finished applications. Each shifts a different amount of management to the provider.

A deployment model that connects private infrastructure with public cloud services so data and applications can move between them. It supports workload placement flexibility, burst capacity, and gradual migration while keeping some systems on premises.

The ability to move running or stopped workloads between hosts, clusters, data centers, or clouds without disrupting users. It depends on compatible virtual hardware, shared or replicated storage, and consistent networking.

The maximum acceptable time to restore a service after a disruption. It drives decisions about replication frequency, standby capacity, and automation, and is usually defined together with the recovery point objective.

Automated coordination of multiple tasks and systems so a complex process runs end to end without manual steps. In virtual and cloud environments it provisions resources, sequences configuration, and enforces policy across many components.

A specific, measurable statement describing what learners should be able to do by the end of a lesson or course. It guides content selection, activity design, and assessment, and it usually names an observable action.

The process of learning about participants before training, including their roles, experience, existing knowledge, and goals. Results inform pacing, examples, lab difficulty, and which prerequisites need to be reviewed or skipped.

A structured outline of what will be taught in a session, including objectives, sequence of topics, activities, timing, materials, and assessment. It keeps delivery on track and helps another instructor teach the same content consistently.

A live walkthrough in which the instructor performs a task while explaining decisions and expected results, often projected for the class. It models correct procedure before learners attempt the same task on their own.

Temporary support provided to learners as they practice a new skill, such as step-by-step guides, hints, or partially completed configurations. Support is gradually removed as competence grows so learners become independent.

Low-stakes checks during instruction that reveal whether learners are following the material, such as polls, quick labs, or targeted questions. Results let the instructor adjust pace or revisit content before the final assessment.

The amount of mental effort a task demands. Reducing extraneous load, for example by simplifying slides, chunking steps, and removing distractions, helps learners retain new technical material and complete hands-on tasks.

Guidelines for teaching adults, who typically need relevance, practical application, some control over their learning, and respect for prior experience. Applying them means explaining why a topic matters and letting learners practice real tasks.

A set of verification steps completed before class, such as confirming hosts are powered on, networks are reachable, credentials work, and lab exercises run end to end. It prevents avoidable delays once learners arrive.

A known-good, preconfigured baseline of a virtual machine or nested environment that is copied for each learner or lab instance. It ensures consistent starting conditions and can be rebuilt quickly if a lab is damaged.

The process of returning a lab environment to its documented starting state, usually by reverting to a baseline snapshot or redeploying from a template. It is used after practice, between cohorts, or when a learner breaks a configuration.

Explicit expectations set at the start of a session about participation, questions, breaks, device use, and respect among learners. They create a predictable environment and reduce disruptions during demonstrations and labs.

The documented route for getting help when a problem exceeds the instructor's ability to resolve it, naming who to contact, how, and when. It covers lab infrastructure failures, licensing issues, and content errors.