Which three operations can cause VMFS metadata updates? (Choose three.)

The correct answer is C. Migrating a VM with vMotion. D. Powering a VM on or off. E. Expanding a VMFS datastore.. VMFS metadata tracks the filesystem structure, file locks, and allocation information on a datastore. Three operations that trigger metadata updates are: (C) Migrating a VM with vMotion - vMotion must update file lock ownership and VM registration data on the VMFS volume; (D) Pow

Section 3 – Configure and Administer vSphere 6.5 Storage

Question

Options

ARestarting a VM using the guest OS.
BLaunching a VM console.
CMigrating a VM with vMotion.
DPowering a VM on or off.
EExpanding a VMFS datastore.

How the community answered

(32 responses)

A
3% (1)
B
6% (2)
C
91% (29)

Explanation

VMFS metadata tracks the filesystem structure, file locks, and allocation information on a datastore. Three operations that trigger metadata updates are: (C) Migrating a VM with vMotion - vMotion must update file lock ownership and VM registration data on the VMFS volume; (D) Powering a VM on or off - these operations acquire or release file locks on VMDK and swap files, both of which require metadata changes; and (E) Expanding a VMFS datastore - physically resizing or adding extents to the datastore directly modifies the VMFS filesystem metadata. In contrast, (A) a guest OS restart keeps the VM running at the hypervisor level with no VMFS lock changes, and (B) launching a VM console is a purely administrative UI action with no filesystem impact.

Topics

#VMFS metadata#vMotion#datastore expansion#storage operations

Community Discussion

No community discussion yet for this question.

Full 2V0-622 Practice