A virtual machine's disk was created to grow as the guest wrote data. The guest paused when the host datastore had no free space left. What filled the datastore?
Select an answer to reveal the explanation.
Short Explanation
You can trace the pause to the growing virtual disk: it expanded as the guest wrote data until the datastore ran out of space. Reducing guest memory, using a loopback plug, or rebuilding a RAID 0 stripe does not make that disk grow.
Full Explanation
The growing virtual disk is the cause: it was configured to expand as the guest wrote data, and that expansion consumed the host datastore’s available space until none remained. With no free datastore space, the guest paused. Reducing the guest’s memory changes the memory allocated to the guest; it does not fill the datastore. A loopback plug is used to test a host network port, not to store guest files, so it cannot account for the lost datastore capacity. A RAID 0 rebuild concerns the storage arrangement and is not the mechanism by which this virtual disk expands as the guest writes. Exam caveat: focus on the stated link between guest writes and disk growth; the pause alone does not identify what used the datastore, but the question explicitly says the disk was created to grow. Practical check: inspect the virtual disk’s size and the datastore’s free space, and confirm that the disk’s expansion accounts for the space consumed. After addressing the capacity, verify that the guest resumes and that the datastore retains free space.