Configure and Manage vSphere Storage →mediumMultiple ChoiceObjective-mapped

VCP-DCV Configure and Manage vSphere Storage Practice Question

Exhibit

Refer to the exhibit.

Output from vmkfstools command:

vmkfstools -V /vmfs/volumes/datastore1/vm1/vm1.vmdk

Disk descriptor file: /vmfs/volumes/datastore1/vm1/vm1.vmdk
# Disk DescriptorFile
version=1
CID=12345678
parentCID=ffffffff
createType="vmfs"

# Extent description
RW 1048576000 VMFS "vm1-flat.vmdk"

# The Disk Data Base
#DDB


The VM is using a virtual mode RDM? (Based on the descriptor, is this a virtual RDM?)

Refer to the exhibit. What type of virtual disk is represented by this descriptor file?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Thick provisioned eager zeroed VMDK

The descriptor shows createType='vmfs' and a single extent with a 'flat.vmdk' file. This is characteristic of a thick provisioned virtual disk on VMFS. Specifically, thick provisioned eager zeroed VMDK files use the 'flat.vmdk' naming convention. Option A is incorrect because a thin provisioned VMDK would have createType='vmfsThin'. Option C is incorrect because a sparse disk with multiple extents would list multiple extents in the descriptor. Option D is incorrect because a physical mode RDM would have createType='vmfsRaw' or 'vmfsRawDeviceMap' and reference a raw device mapping.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Thin provisioned VMDK
Why it's wrong here
Incorrect. A thin provisioned VMDK would use createType='vmfsThin' and a different extent file naming (e.g., -flat.vmdk is not used for thin).
✓
Thick provisioned eager zeroed VMDK
Why this is correct
Correct. The createType='vmfs' with a single flat.vmdk extent indicates a thick provisioned eager zeroed VMDK (the default thick type on VMFS).
✗
Sparse disk with multiple extents
Why it's wrong here
Incorrect. A sparse disk with multiple extents would list multiple extent entries in the descriptor, not a single flat.vmdk.
✗
Physical mode RDM
Why it's wrong here
Incorrect. A physical mode RDM would have createType='vmfsRaw' or 'vmfsRawDeviceMap' and reference a disk device via a compatibility mode, not a .vmdk file.

Go deeper

VCP-DCV Configure and Manage vSphere Storage Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question