While configuring a test environment, a technician must choose a virtual hard drive format for each VM. The host laptop has only 100 GB of free space, so unused guest disk capacity should not be reserved on the physical SSD. Which virtual disk type should the technician select?
Raw device mapping to the physical SSD
Differencing disk created from a snapshot chain
Dynamically allocated (thin-provisioned) virtual disk
A dynamically allocated (thin-provisioned) virtual disk initially occupies only a few megabytes of physical storage and grows as data is written inside the guest, preserving host free space. Fixed-size (thick-provisioned) disks pre-allocate the full capacity up front, immediately consuming host storage. Raw-device mapping presents the entire physical drive directly to the VM and also ties up all available space. Differencing (snapshot) disks depend on an existing parent image and mainly capture changes, but the parent still requires space and the chain is not intended for primary storage allocation. Therefore, thin provisioning is the most space-efficient choice for the scenario described.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a dynamically allocated (thin-provisioned) virtual disk?
Open an interactive chat with Bash
How does a fixed-size (thick-provisioned) virtual disk differ from a dynamically allocated one?
Open an interactive chat with Bash
Why is thin provisioning preferred over other virtual disk types for limited host space?