CCNA Vmware Vsphere Foundation Fundamentals Questions

Expandable Reservation lets a child pool borrow beyond its own reservation, drawing on the parent's unreserved capacity. It takes effect only once the child's reservation is fully consumed and the parent still holds unreserved resources available for lending.

With four identical hosts and a one-host failure tolerance, the percentage policy must reserve enough capacity to absorb a single host's workload. Reserving 25 percent of cluster CPU and memory equals exactly one host's share (1 ÷ 4), satisfying the FTT = 1 constraint without over-reserving.

A VM-Host affinity rule binds the VM to a Host Group of the two designated hosts, enforcing placement and restricting it from the other four. This satisfies the strict licensing constraint requiring the VM to run only on those hosts.

DAVG measures the physical array's service time for read or write commands, excluding VMkernel queue latency, which is KAVG. This satisfies the stem's requirement to isolate array-side latency from queueing delays when analysing storage performance in esxtop's device view.

Deselecting the memory tickbox produces a crash-consistent snapshot containing only the VM's disk state and configuration. The .vmsn memory file is omitted, so no RAM contents are captured, reducing snapshot size and avoiding quiescing of running memory.

Co-stop arises because the hypervisor must co-schedule all 32 vCPUs simultaneously, yet only 16 physical cores exist. This strict co-scheduling forces vCPUs to wait for a complete set of free cores, inflating %RDY. The oversized vCPU-to-core ratio directly causes the scheduling delays observed in esxtop.

Snapshot privileges reside under the Virtual Machine, State category, covering create, revert, consolidate and delete operations. Selecting this category satisfies the stem's requirement to grant snapshot management, since permissions there control the VM's snapshot state rather than configuration or interaction.

HA Admission Control reserves cluster capacity before failover, guaranteeing sufficient resources exist to restart affected VMs on surviving hosts. It directly satisfies the stem's requirement that host failure leaves enough capacity, by blocking power-ons that would consume the reserved failover buffer.

Hot-add vCPU lets a running VM gain processors through the VMX device model, which signals the guest OS to bring the new vCPUs online dynamically. This satisfies the no-downtime constraint, provided the guest supports CPU hot-plug and the VM's configured socket/core limits permit the addition.

Directory groups centralise authorisation: permissions bind to the group object, so membership changes in Active Directory propagate automatically without editing vCenter roles per user. This satisfies the best-practise requirement for scalable, auditable privilege assignment across the integrated identity source.

A VMDK on VMFS or NFS is the native virtual disk format, provisioned through the datastore and attached directly to the VM's virtual SCSI or NVMe controller. This satisfies the requirement for storage natively provisioned and attached within vSphere.

Host Profiles captures a reference host's configuration as a profile, then continuously checks every attached host against it and remediates drift automatically. This directly satisfies the requirement for compliance checking plus automated remediation across all 20 hosts, preventing configuration drift without manual per-host auditing.

GRANT (28672 MB) exceeds ACTIVE (16384 MB), so roughly 12 GB is mapped to the VM's physical address space but not touched recently. The hypervisor has granted those pages, yet the guest is not actively referencing them, indicating reclaimable idle memory rather than a shortage.

Proactive HA consumes hardware provider events and, on a degraded redundant power supply, either recommends or automatically evacuates VMs depending on the cluster's automation level. This satisfies the stem's constraint that response behaviour follows the configured automation setting.

Storage capabilities are exposed through VASA provider data or user-defined datastore tags, which the policy then matches against. Automated tiering between SSD and HDD is advertised as such a capability, so the policy enforces placement on capable datastores.

A VM-Host anti-affinity rule with a must rule strictly prohibits the selected virtual machines from running on the selected host group. It does not force the virtual machine onto any specific host, so it meets the requirement of excluding the reserved hosts without pinning the workload elsewhere. This is the correct rule type for guaranteed exclusion.

Storage DRS continuously monitors datastore latency and I/O imbalance, then uses Storage vMotion to redistribute virtual disks across datastores in the datastore cluster once latency thresholds are breached, directly satisfying the requirement to automatically balance I/O load.

NIOC version 3 reserves bandwidth for system traffic types, including fault tolerance, under the distributed switch's System Traffic resource allocation. Applying shares and reservations there satisfies the requirement to guarantee FT bandwidth during high utilisation.

A vSphere Distributed Switch is configured once at the vCenter level and applies consistently to every member host, which is exactly the centralized configuration the scenario requires. It also supports advanced features such as port mirroring, NetFlow, and per-port policies needed by NSX-backed workloads, so it is a foundational component of this design.

Fully Automated DRS performs its own migration recommendations and executes them, so evacuating VMs off the host on entering Maintenance Mode happens without manual intervention. Partially Automated only generates recommendations requiring approval, which would leave VMs powered on and block the task.

A vSphere Distributed Switch spans multiple hosts, letting the administrator configure port groups, VLANs, and policies once and have them applied consistently across every member host. This centralised control plane is its primary function in a multi-host cluster, replacing per-host standard switch configuration.

Storage vMotion relocates virtual disks between datastores with different performance or capacity tiers while the VM remains running, enabling tiering and reclamation without downtime. This directly addresses the storage performance and capacity utilisation optimisation the stem requires.

A hard IOPS limit caps the batch VM's disk throughput, directly preventing it from consuming datastore queue depth and starving other workloads. This satisfies the constraint of stopping one VM overwhelming shared storage during peak hours, unlike shares or reservations which only guarantee minimums.

Memory ballooning uses a VMware Tools driver inside the guest to inflate a balloon, forcing the guest to page idle memory back to the hypervisor. This satisfies the stem's requirement for a hypervisor-level driver reclaiming idle guest memory.

Export OVF Template directly satisfies the requirement to export a virtual machine as an OVF template from the vSphere Client. Right-clicking the virtual machine exposes this action, which packages the VM's configuration and virtual disks into OVF format. No other right-click menu option performs OVF export, so this selection matches the stem's stated task exactly.

The 'Number of failures to tolerate' setting defines how many host, disk, or disk group failures the vSAN datastore can withstand while preserving data availability. Setting it to 1 ensures that if a single disk or disk group fails, the virtual machine's data remains accessible because vSAN maintains a mirror or erasure-coded copy. This directly meets the requirement of surviving a single disk or disk group failure.

A memory reservation guarantees the VM receives 4GB of physical RAM that the hypervisor cannot reclaim, even under host memory pressure. This directly ensures the critical production VM always has its required physical memory available.

Encrypted vMotion encrypts the VM's memory and state as it crosses the network during a live migration, using a one-time AES-256 key. This directly satisfies the stem's "data in transit" requirement, protecting regulated workloads from interception on the migration path between hosts.

VM Overrides apply per-VM DRS settings, letting the administrator raise the database VM's shares or set a custom automation level while leaving the cluster-wide automation level untouched. This resolves the CPU contention against batch VMs without altering cluster defaults, exactly as the stem requires.

vSphere Lifecycle Manager uses a desired-state image, combining ESXi base image, firmware add-ons and components into one cluster baseline. This satisfies the stem's requirement for a unified image-based baseline, enabling compliance checking and remediation across all 16 hosts.

An RDM presents a physical LUN directly to the VM as a mapped device, providing persistent raw disk access with metadata in a pointer file, which is exactly the provisioning type needed to attach a persistent raw disk device.

CPU Demand reflects the CPU the VM would consume absent contention or configured limits, so it can exceed allocation when the guest wants more than granted. This satisfies the stem's requirement to define the metric driving the flagged condition.

After the VASA provider is registered and the protocol endpoint is presented, the array advertises one or more storage containers. A rescan lets each ESXi host discover those containers, and mounting a container creates the vVols datastore in the vSphere Client. This is the required next step because vVols datastores are backed by storage containers rather than by traditional LUNs.

vSphere Configuration Profiles let administrators define a desired configuration for a cluster and compare each host against it, reporting drift and enabling remediation. It is the native, image-based approach in vSphere 9.0 for enforcing a standardized ESXi configuration across cluster hosts without deploying a separate host configuration management product.

vCenter Single Sign-On natively federates external directories through Identity Provider configurations, supporting Active Directory over LDAP/LDAPS, OpenID Connect, and generic LDAP. This satisfies the stem's requirement for authentication mechanisms built into vCenter Server itself, without third-party brokers or additional gateway components.

vSphere Virtual Machine Encryption encrypts VM files including vmdk and vmx at the hypervisor level, using keys from a KMIP-compliant key provider. This satisfies the stem's requirement to protect virtual machine files at rest without relying on in-guest encryption.

vSphere Lifecycle Manager enforces a declarative desired-state image per cluster, so firmware and drivers are remediated consistently across every host against that single specification. This directly satisfies the stem's consistency constraint, unlike per-host baselines that drift. It integrates firmware updates through hardware support managers, keeping the whole cluster aligned.

vSphere Distributed Services Engine offloads networking, storage, and security services to a DPU that contains its own ARM cores and runs a separate software stack. ESXi still runs on the x86 server as the hypervisor, but a portion of the infrastructure plane executes on the DPU, freeing host CPU cycles for tenant workloads.

Guest customization specifications are created under Policies and Profiles, then Guest Customization Specifications, in the vSphere Client. This satisfies the stem's requirement to modify IP address and hostname automatically, as the specification supplies the sysprep or cloud-init data applied at deployment.

The ABORT counter in esxtop increments when the ESXi storage stack or the array fails to complete an I/O within the timeout window, forcing the command to be aborted. A high value signals latency or path problems causing repeated timeouts.

Cross-vCenter vMotion migrates a powered-on VM between vCenter Server instances across sites, preserving its state with no downtime. It satisfies the stem's constraint of moving a running VM between different data centres, which standard vMotion within a single vCenter cannot achieve.

DRS honours configured VM-Host and VM-VM affinity or anti-affinity rules when generating placement and migration recommendations, so workloads stay pinned to or separated from specified hosts and peers. This rule compliance is one of the three evaluated factors, alongside resource utilisation and host compatibility constraints.

SPBM is the vSphere Foundation framework that lets administrators create storage policies describing capabilities such as replication, encryption, and performance. These policies are assigned to virtual machines and datastores, and SPBM enforces compliance regardless of the underlying block or file storage. It provides the centralized, policy-based abstraction required in this scenario.

Setting the port group VLAN ID to 20 makes the standard switch tag outbound frames from member virtual machines with VLAN 20 and strip the tag on inbound frames. The guest operating system remains unaware of VLANs and sends untagged traffic, which matches the requirement that virtual machines transmit untagged on VLAN 20 while the physical switch port carries tagged frames.

Running a VM on delta disks forces every write to traverse the snapshot chain before reaching the base VMDK, adding latency and reducing throughput. This satisfies the stem's performance constraint: sustained snapshot use degrades I/O, so snapshots suit short-term rollback points, not long-term operation.

A vSphere Distributed Switch's control plane resides in vCenter, so the switch configuration is defined once and pushed to every associated host, and it can be exported as a backup. This centralised model removes the per-host repetition inherent to standard vSwitches, satisfying the uniform, recoverable network configuration requirement.

Upgrading hardware compatibility is performed from the virtual machine's right-click menu in the vSphere Client, via Compatibility, then Upgrade VM Compatibility. This satisfies the stem's requirement to locate the operation, since the VM must be powered off first and the wizard then selects the target ESXi version.

vSphere DRS performs automated initial placement and ongoing balancing of virtual machines across hosts. When a host enters maintenance mode, DRS generates migration recommendations and, in fully automated mode, executes them automatically. This is exactly the behavior needed to evacuate workloads without manual intervention, so enabling DRS satisfies the design requirement for the new cluster.

vCenter Server provides the central management plane that orchestrates VM provisioning operations such as creation, deletion and cloning across managed ESXi hosts. ESXi alone manages only its local VMs, so it cannot deliver the cluster-wide life-cycle management the stem requires.

Storage vMotion relocates a virtual machine's VMDK and configuration to a different datastore while the VM remains powered on and its compute resource, host and cluster stay unchanged. This satisfies the scenario's requirement of changing only storage placement.

SDRS evaluates the 500 IOPS reservation as a placement constraint, verifying the destination datastore has enough unreserved IOPS capacity before migrating the VMDK. This satisfies the scenario's requirement that automated load balancing honours the configured Storage I/O Control reservation.

With the isolation response set to 'Power off and restart VMs', the isolated ESXi host powers off its running VMs locally once it loses heartbeat access to the primary HA node and cannot reach any isolation address. Surviving hosts then detect the failure and restart those VMs, satisfying the cluster's availability requirement during the partition.

A reservation is an absolute guaranteed minimum allocation, enforced even under full contention, and it is deducted from the parent pool's available capacity. This satisfies the rule that a pool always receives at least its reserved compute power.

Linux file system freezing via VMware Tools scripts flushes and freezes mounted file systems before the snapshot, producing application-consistent quiesced images. This satisfies the requirement to quiesce the guest OS during backup without disrupting running services.

A memory reservation guarantees that amount of physical host memory for the virtual machine. When the reservation equals the configured memory, the VMkernel cannot reclaim any of that memory through ballooning or swapping, because the full amount is protected. This directly satisfies the requirement that the virtual machine never lose physical memory to host pressure.

A memory Limit sets an absolute ceiling on the resource pool's consumption, capping it at 32 GB regardless of spare capacity in the parent. Reservations and shares only influence allocation priority, so they cannot enforce a hard maximum. The Limit directly satisfies the stated constraint.

A CPU reservation larger than any single host's unreserved capacity makes the VM unschedulable, since DRS cannot place it even in fully automated mode. This satisfies the stem's insufficient-CPU error despite DRS being enabled, as admission checks reject the reservation outright.

Setting the DRS migration threshold to Priority 1 restricts recommendations to only the most severe imbalance, directly reducing sensitivity to minor load fluctuations. Priority 5 triggers migrations for slight imbalances, so lowering it satisfies the stem's requirement to curb frequent, unnecessary vMotion activity across the cluster.

Virtual Machine Storage Policies let administrators assign per-VM policies defining performance (IOPS, throughput) and availability (FTT, RAID) requirements. This directly satisfies the stem's need to define storage performance and availability for specific virtual machines, rather than applying cluster-wide settings.

A VM-VM anti-affinity rule keeps the two database VMs on separate ESXi hosts, satisfying the requirement that they never share a physical host. Configured as a "must" rule, DRS enforces strict separation, so a host failure cannot take down both database instances simultaneously.

Properly configured DNS and static IP addresses underpin vSphere HA's host-to-host communication and isolation detection. HA agents exchange heartbeats over the management network, so unresolvable names or DHCP-assigned addresses break cluster membership and failover decisions. This satisfies the stem's requirement for critical HA cluster operation components.

Right-clicking the source virtual machine and selecting Clone launches the cloning wizard directly, satisfying the requirement to initiate cloning from the vSphere Client. The wizard then prompts for a name, folder, compute resource, storage and clone type, letting the administrator produce the golden image copy.

HCX provides Layer 2 network extension, stretching on-premises segments into VMware Cloud on AWS so VMs keep their existing IP addresses. This directly satisfies the no-re-IP requirement, unlike migration-only or disaster-recovery tooling that would force readdressing on cutover.

CPU load is a primary metric evaluated by DRS when placing or migrating virtual machines.

vSphere Performance Charts is built into the vCenter interface, providing native real-time and historical metrics for CPU, memory, storage and network across hosts and virtual machines. It satisfies the requirement for right-sizing analysis without external tooling.

Content Library stores VM templates and vApp templates centrally, then synchronises them across clusters, so every deployment uses identical configurations. It also supports versioning and lifecycle management of template content, matching the requirement for consistent deployment and ongoing template maintenance across the environment.

A reservation is an explicit, guaranteed allocation: the pool's configured CPU or memory reservation is set aside and cannot be consumed by sibling pools, ensuring that capacity is always available to it. This is the defining guarantee distinguishing reservations from shares, which only arbitrate contention.

Resizing to 8 vCPUs aligns the virtual machine with a single physical NUMA node of 8 cores, so all vCPU memory accesses remain local. This eliminates remote memory access latency across nodes, directly mitigating the contention and degradation described on the eight-socket host.

Clustering aggregates CPU and memory from member ESXi hosts into a single logical resource pool, so workloads draw on combined capacity rather than being siloed per host. This pooled capacity underpins DRS load balancing and admission control for the cluster.

vSphere DRS satisfies the maintenance-mode evacuation requirement by automatically generating migration recommendations and relocating powered-on VMs to remaining hosts in the cluster. Without DRS enabled, placing a host into Maintenance Mode cannot trigger automatic vMotion evacuations, so VMs would remain stranded until manually migrated.

DAVG measures the average latency the device reports for I/O it processes, isolating the physical storage array or LUN as the bottleneck source. It satisfies the stem's latency investigation by revealing time spent below the VMkernel, distinguishing array-side delay from guest or kernel overhead.

A snapshot including memory captures the running state of the virtual machine, written to a .vmsn file alongside the snapshot descriptor. This preserves in-guest processes and open sessions, allowing a revert to resume execution exactly where it paused.

A required VM-Host affinity rule that surviving hosts cannot satisfy blocks HA restart, because DRS placement constraints are enforced during failover. If the rule is mandatory and no remaining host matches the specified host group, vSphere HA cannot power the VM on, so restart fails.

vSphere HA applies distinct datastore response policies: PDL triggers immediate VM restart on surviving hosts, while APD waits and retries before responding, so these configured policies dictate HA's behaviour when heartbeat or metadata datastores become inaccessible.

An external KMS holds key material outside the vSphere environment and issues keys to ESXi hosts only after authentication. This separation means a compromised host cannot simply read keys from local storage; it must authenticate to the KMS, and access can be revoked or restricted. Using a standard key provider with an external KMS meets both the encryption-at-rest and host-compromise separation requirements.