A host's datastore is filling up, and the growth is the snapshots kept for one virtual machine. Which requirement do those snapshots create?
Select an answer to reveal the explanation.
Short Explanation
Every snapshot is another copy of the guest's changes, and those copies are sitting on the host's shelf. You have to plan extra storage for them. A snapshot is not free, a port-test plug does not hold it, and a screen setting does not shrink it.
Full Explanation
A snapshot records the guest's disk state, and the changes after that point are stored on the host's datastore. Keeping snapshots is why this datastore is filling, so the requirement is extra host storage. A snapshot is not a free label. The growth in the stem is the space it uses. A loopback plug tests a network port. The hypervisor does not keep snapshots there. Refresh rate is a display timing. It does not shrink snapshot files. Exam caveat: deleting a snapshot consolidates it and can take time and still more temporary space. Do not delete them all at once on a datastore that is already full. Operational check: list the snapshots, remove the ones the test no longer needs, and confirm the datastore free space recovers. Remove snapshots the test no longer needs and watch free space return. Note the result on the ticket. Do not delete every snapshot at once on a datastore that is already full.