VCI Registration Part 1 flashcards
VCI Registration Part 1 · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- ESXi hypervisor
- A Type 1 bare-metal hypervisor from VMware that runs virtual machines directly on server hardware without an underlying general-purpose operating system, providing CPU and memory scheduling for all guest VMs.
- vCenter Server
- Central management platform for ESXi hosts and clusters. It supplies inventory, permissions, templates, cloning, and orchestration of vMotion plus cluster services such as HA and DRS.
- VMX file
- The plain-text configuration file of a virtual machine. It records hardware settings such as memory size, network adapter types, disk paths, and declared guest operating system.
- VMDK file
- The virtual disk file holding a VM's disk contents. It may be monolithic or split, and snapshot delta disks are also written as VMDK files alongside the base disk.
- Snapshot
- A point-in-time record of a VM's disk state plus optional memory state. Writes go to delta files, so snapshots grow continuously and are not a substitute for backup.
- vSphere HA
- Cluster feature that monitors hosts and restarts their virtual machines on surviving hosts after a failure. It protects availability rather than performance and needs shared or replicated storage.
- DRS
- Distributed Resource Scheduler balances CPU and memory load across a cluster by migrating running VMs with vMotion, following configured automation levels, affinity rules, and maintenance mode.
- vMotion
- Live migration of a powered-on VM's compute and memory state between hosts with minimal downtime. It requires shared storage, compatible CPU features, and sufficient network bandwidth.
- Standard vSwitch
- A virtual switch configured separately on each ESXi host. It is simple but must be recreated host by host, which makes consistent configuration across large clusters laborious.
- Type 1 hypervisor
- Virtualization layer installed directly on bare metal that runs VMs without a host operating system. ESXi is an example and typically delivers better performance and a smaller attack surface.
- Type 2 hypervisor
- Virtualization application installed on top of a conventional operating system, such as Workstation or Fusion. Guest I/O passes through the host OS, which adds latency and overhead.
- IaaS
- Cloud service model delivering compute, storage, and networking as provisioned resources. The customer manages operating systems, middleware, and applications while the provider manages the physical infrastructure.
- PaaS
- Cloud service model providing a managed runtime and development platform. The provider handles servers, operating systems, and scaling, while the customer deploys application code and manages its data.
- SaaS
- Cloud service model delivering a complete provider-managed application over a network, usually by subscription. The customer manages only users, data, and access settings rather than infrastructure.
- Five NIST cloud characteristics
- On-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service. A service must show these traits to qualify as cloud computing under the NIST definition.
- Recovery time objective
- The maximum acceptable duration of downtime after an outage before a service must be restored. It drives choices about clustering, high availability, and failover design.
- Recovery point objective
- The maximum acceptable amount of data loss, expressed as elapsed time. It determines how frequently backups or replication must occur to meet the business requirement.
- Scale up versus out
- Scaling up adds CPU, memory, or storage to one host; scaling out adds more hosts. Clusters scale out, and DRS with HA operates at that cluster scope.
- Andragogy
- Malcolm Knowles' model of adult learning: adults need relevance, self-direction, problem-centered content, and use of prior experience, in contrast to purely subject-centered pedagogy aimed at children.
- Bloom's revised taxonomy
- Six cognitive levels ordered remember, understand, apply, analyze, evaluate, create. Lab objectives should target apply or above so learners practice skills instead of reciting facts.
- Gagne's nine events
- Instructional sequence: gain attention, state objectives, recall prior learning, present content, guide learning, elicit performance, provide feedback, assess performance, enhance retention and transfer.
- ABCD objective format
- A way to write objectives with Audience, Behavior, Condition, and Degree. For example, given a vSphere Client, the learner creates a VM with specified settings in ten minutes.
- Working memory capacity
- Working memory handles roughly four to seven chunks at once. Limit simultaneous new concepts, cap slide bullets near six, and split long procedures into short steps.
- Tell-show-do-review
- Four-step demonstration cycle: explain the concept, demonstrate it, let the learner perform it, then debrief. It keeps hands-on practice central to skill acquisition.
- Wait time
- A pause of about three to five seconds after asking a question before calling on someone or prompting. It increases answer length and broadens participation.
- Lab baseline snapshot
- A known-good snapshot captured before learners begin. Reverting restores the environment quickly between cohorts instead of rebuilding, cutting reset time from hours to minutes.
- Pre-lab checklist
- Items verified before class: hosts powered, management services running, DNS and NTP correct, licensing applied, templates present, networks reachable, and baseline snapshots already taken.
- Lab IP addressing plan
- A documented map of subnets, VLAN IDs, and addresses for management, storage, vMotion, and VM traffic. It prevents overlaps and speeds learner self-checks during troubleshooting.
- Lab network isolation
- Placing student labs on dedicated VLANs and port groups so misconfigured DHCP, duplicate addresses, or routing loops cannot disrupt classroom systems or production infrastructure.
- Clone storm
- Performance collapse when many VMs are deployed or booted simultaneously, saturating storage IOPS and network links. Mitigate with staggered starts, linked clones, or content libraries.
- Lab triage order
- Troubleshooting sequence for lab faults: check power and physical connectivity, then IP reachability and DNS, then service status, then configuration changes the learner recently made.
- Time boxing a lab
- Allocating fixed blocks for environment build, learner tasks, and reset. Builds can take thirty to sixty minutes, so schedule them before learner time begins.