108 real Storage questions from the Virtualization bank, as asked in Indian campus drives and tech interviews. Every question has a verified answer and an AI-tutor explanation on placd — free to start.
1. What is snapshot?
Junior
A.mapping a physical LUN directly to a VM
B.ESXi's pluggable storage architecture that manages multiple physical paths to a LUN for redundancy and load balancing (Round Robin, Fixed, MRU)
C.a point-in-time delta state of a VM — not a backup
D.pre-allocating and zeroing a virtual disk upfront
A.snapshot — NVMe over Fabrics (RDMA, TCP, or FC) gives ESXi low-latency block storage with deeper queues than SCSI.
B.snapshot — a point-in-time delta state of a VM — not a backup
C.snapshot — Allocating more virtual disk capacity than physically exists, relying on actual usage staying below the total; requires monitoring to avoid datastore-full outages
D.snapshot — a clone sharing the base disk with its parent to save space
A.linked clone — a clone sharing the base disk with its parent to save space
B.linked clone — A datastore-wide feature that enforces fair IOPS distribution by share value when latency crosses a congestion threshold
C.linked clone — Balances VMs across a datastore cluster by space usage and I/O latency, with affinity and anti-affinity rules.
D.linked clone — Allocating more virtual disk capacity than physically exists, relying on actual usage staying below the total; requires monitoring to avoid datastore-full outages
A.thin provisioning — pre-allocating and zeroing a virtual disk upfront
B.thin provisioning — allocating disk space on demand rather than upfront
C.thin provisioning — A transport (over RDMA, TCP or Fibre Channel) that extends the low-latency NVMe protocol to networked storage, supported as a datastore type in vSphere 8
D.thin provisioning — vStorage APIs for Array Integration: offloads operations like full copy, block zeroing and hardware-assisted locking (ATS) to the storage array
A.Telling the array which blocks a thin disk no longer uses so freed space returns to the pool; automatic on VMFS-6 at a configurable rate
B.allocating disk space on demand rather than upfront
C.pre-allocating and zeroing a virtual disk upfront
D.A transport (over RDMA, TCP or Fibre Channel) that extends the low-latency NVMe protocol to networked storage, supported as a datastore type in vSphere 8
A.thick eager-zeroed — A framework where each virtual disk is a native array object managed via VASA, enabling per-VM array snapshots, replication and policy-based placement
B.thick eager-zeroed — Independent-persistent disks are unaffected by snapshots while independent-nonpersistent disks discard all writes at power-off
C.thick eager-zeroed — pre-allocating and zeroing a virtual disk upfront
D.thick eager-zeroed — an independent complete copy of a VM
A.VMware HCI software-defined storage pooling local disks
B.NVMe over Fabrics (RDMA, TCP, or FC) gives ESXi low-latency block storage with deeper queues than SCSI.
C.Allocating more virtual disk capacity than physically exists, relying on actual usage staying below the total; requires monitoring to avoid datastore-full outages
D.ESXi's pluggable storage architecture that manages multiple physical paths to a LUN for redundancy and load balancing (Round Robin, Fixed, MRU)
A.vSAN 8 ESA — Telling the array which blocks a thin disk no longer uses so freed space returns to the pool; automatic on VMFS-6 at a configurable rate
B.vSAN 8 ESA — ESXi's pluggable storage architecture that manages multiple physical paths to a LUN for redundancy and load balancing (Round Robin, Fixed, MRU)
C.vSAN 8 ESA — the architecture removing disk groups and a dedicated cache tier (all-NVMe)
D.vSAN 8 ESA — vStorage APIs for Array Integration: offloads operations like full copy, block zeroing and hardware-assisted locking (ATS) to the storage array
A.qcow2 — An improved virtual disk managed independently of any VM, with its own identity and snapshots, used by CNS for Kubernetes persistent volumes
B.qcow2 — The number of outstanding I/Os an HBA or device can handle; too low throttles throughput, too high inflates latency.
C.qcow2 — Allocating more virtual disk capacity than physically exists, relying on actual usage staying below the total; requires monitoring to avoid datastore-full outages
D.qcow2 — the KVM copy-on-write disk format supporting snapshots
Showing 30 of 108 Storage questions — the full set, with answers, explanations and an AI tutor on every question, is inside.
Free to start
Answers, AI explanations, and a scored voice mock interview
Sign up free to check your answers with explanations, ask the AI tutor anything on any question, and take one full AI mock interview — scored like a real panel.