Troubleshooting practice questions

The virtual network standard switch lacks promiscuous mode enabled.

Why wrong: Promiscuous mode affects network packet inspection, not power-on compute allocation.

Enhanced vMotion Compatibility is set to an older baseline.

Why wrong: EVC settings prevent migration or power-on only if CPU instructions mismatch, not resource reservations.

The virtual machine has too many snapshots attached to its configuration file.

Why wrong: Snapshots impact storage and performance, not CPU reservation power-on placement checks.

vSphere HA admission control percentage limits.

Why wrong: HA admission control reserves failover capacity, not affinity placement constraints.

Enhanced vMotion Compatibility (EVC) baselines.

Why wrong: EVC ensures CPU instruction set compatibility, not workload placement rules.

Storage I/O Control share allocations.

Why wrong: SIOC governs storage queues, not DRS cluster placement rules.

The virtual machine must be powered off for any Storage vMotion operation to succeed.

Why wrong: Storage vMotion can be performed while the VM is powered on (online migration).

The physical switch port channel must be reconfigured to trunk the new datastore LUN IDs.

Why wrong: Physical switches do not trunk LUN IDs; LUNs are block storage entities accessed via FC or iSCSI/NVMe.

The guest operating system has experienced a hardware memory error on the physical DIMM.

Why wrong: Hardware errors trigger machine check exceptions, not ballooning.

The virtual machine has exceeded its configured memory reservation limit.

Why wrong: Reservations guarantee minimum allocation, not ballooning triggers.

The virtual machine has a memory limit set lower than its active working set.

Why wrong: A memory limit restricts maximum allocation, but ballooning is driven by host pressure.

esxcli storage san fabric status

Why wrong: ESXi does not track SAN fabric zoning status via this command.

esxcli fcadapter connection get

Why wrong: This command does not exist in the ESXi command namespace.

esxcli vmfs datastore extent list

Why wrong: This lists datastore extents, not multipathing path states.

VMware Tools has failed to start inside the guest operating system.

Why wrong: VMware Tools failure prevents ballooning and guest heartbeats, but swapping is a hypervisor-driven action triggered by absolute memory shortage.

The storage array is experiencing high hardware latency.

Why wrong: While swapping causes disk I/O, the root cause is memory exhaustion, not array latency.

The virtual machine has too much physical RAM allocated, causing memory corruption.

Why wrong: Oversized memory allocation causes memory pressure, but corruption is unrelated to swapping.

SWCUR (Current swap usage)

Why wrong: SWCUR is a memory swapping metric.

MCTLSZ (Ballooned memory size)

Why wrong: MCTLSZ is a memory metric, not a CPU metric.

DAVG (Device latency)

Why wrong: DAVG is a storage latency metric.

All virtual machines on the affected site immediately power off to prevent split-brain.

Why wrong: Powering off VMs requires a complete loss of datastore availability or HA response, not merely management connectivity loss on the witness.

The vSAN cluster automatically falls back to a standard single-site cluster layout.

Why wrong: Stretched cluster topologies cannot automatically reconfigure their fault domains without manual administrator intervention.

The vSAN datastore becomes entirely read-only across all sites.

Why wrong: As long as quorum is maintained via surviving data nodes and witness data paths, the datastore remains fully read-write.

esxcli storage vmfs extent list

Why wrong: This lists VMFS extents, which applies to traditional block storage datastores, not vSAN objects.

esxcli vsan cluster get

Why wrong: This checks general cluster membership and sub-cluster status, not individual disk component performance or health.

esxcli network ip route list

Why wrong: This displays the host routing table, which is irrelevant to vSAN storage component inspection.

The virtual machine has snapshot files older than 30 days.

Why wrong: Snapshots do not block vMotion; modern vSphere supports migrating VMs with snapshots.

The virtual machine is configured with a memory limit lower than its allocated RAM.

Why wrong: Memory limits do not block vMotion migrations.

esxcli vm kernel log list

Why wrong: This command does not exist in the ESXi command namespace.

esxcli system account list

Why wrong: This lists local user accounts on the ESXi host.

esxcli network firewall get

Why wrong: This checks firewall rule statuses, not syslog forwarding configurations.

It prioritizes voice and video packets using DSCP tagging.

Why wrong: QoS tagging handles packet marking, whereas traffic shaping enforces bandwidth limits.

It mirrors port traffic to a designated analyzer VM for packet capture.

Why wrong: Port mirroring (RSPAN/ERSPAN) handles traffic duplication for analysis.

It automatically load-balances traffic across physical uplinks using IP hash.

Why wrong: Uplink teaming policies control load balancing, not traffic shaping.

Restart the vCenter Server license service.

Why wrong: License services do not control file locks on datastores.

Format the datastore to release all file locks instantly.

Why wrong: Formatting datastores destroys all data.

Reboot the physical upstream network switch.

Why wrong: Network switches do not lock ESXi VMDK files.

Network Packet Drop Rate

Why wrong: Network Packet Drop Rate is a networking metric.

Memory Swapin Rate

Why wrong: Memory Swapin Rate tracks memory paging activity to disk, not storage array I/O latency.

CPU Ready Time

Why wrong: CPU Ready Time is a CPU scheduling metric, not a storage metric.

Because virtual machines do not use TCP/IP connections in vSphere Foundation 9.0.

Why wrong: Virtual machines use standard TCP/IP stacks within their guest operating systems.

Because esxcli commands are only permitted when vCenter Server is offline.

Why wrong: esxcli commands can be executed anytime regardless of vCenter state as long as SSH or local shell access is available.

Because the command only works for IPv6 addresses and drops IPv4 queries.

Why wrong: The command lists both IPv4 and IPv6 socket connections.

Press 'c' while running esxtop to display CPU scheduling statistics.

Why wrong: The 'c' key displays CPU metrics.

Press 'm' while running esxtop to display memory reclamation statistics.

Why wrong: The 'm' key displays memory statistics.

Press 'n' while running esxtop to display network interface statistics.

Why wrong: The 'n' key displays network statistics, not storage metrics.

Memory Compression, Swapping, Ballooning, and then TPS.

Why wrong: This order is incorrect and does not reflect ESXi memory management architecture.

Ballooning first, followed instantly by powering off idle virtual machines.

Why wrong: ESXi never automatically powers off VMs due to memory pressure unless HA admission control or explicit resource policies dictate placement.

Swapping immediately, followed by Ballooning, TPS, and Memory Compression.

Why wrong: Swapping impacts performance significantly and is always the last resort before out-of-memory errors.

vSphere Client -> vLCM -> Datastore Compliance View.

Why wrong: vLCM compliance view displays software and firmware status, not real-time disk I/O metrics.

Cloud Builder -> Monitoring -> Storage Inspector.

Why wrong: Cloud Builder is inactive post-deployment.

NSX Manager -> Diagnostics -> Datastore Latency Test.

Why wrong: NSX does not test or report datastore disk latency.

Run 'esxcli network cdp get' via the vCenter appliance shell.

Why wrong: CDP is managed on ESXi hosts, and the command syntax for CDP inspection in ESXi is executed on the host, not vCenter shell.

Check the virtual machine hardware summary tab.

Why wrong: VM hardware summary shows VM vNIC configurations, not physical switch CDP/LLDP data.

Open vCenter Administration -> Licensing -> Physical Switch Maps.

Why wrong: This menu path is invalid.

Enhanced Linked Mode is disabled between local vCenter servers

Why wrong: Enhanced Linked Mode affects management visibility, not cluster-level HA execution on individual nodes.

The ESXi hosts are configured with a standard switch instead of a distributed switch

Why wrong: vSphere HA functions correctly with both standard and distributed switches.